www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2946) OpenEJB tck testing repo
Date Fri, 10 Sep 2010 13:57:33 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908021#action_12908021

Gavin commented on INFRA-2946:

Your last comment is confusing. Sounds like you want some parts of the same group to have
read perms whilst other parts of  the same group get write also - not possible.

Perhaps, after looking at other setups you want :

jcp-j2ee-nda = rw

jcp-j2ee-nda-ro = r

Does that sound right? 

(If not please check the asf-authorisation-template file for a few examples.)

> OpenEJB tck testing repo
> ------------------------
>                 Key: INFRA-2946
>                 URL: https://issues.apache.org/jira/browse/INFRA-2946
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: David Blevins
>            Assignee: Gavin
> Would be great if we could get a repo next to the Geronimo repo for setting up an OpenEJB
test harness.
> SVN: 
> https://svn.apache.org/repos/tck/openejb-tck/ 
> Mailing list (private): 
> tck@openejb.apache.org 
> Anyone in the jcp-j2ee-nda group should have read access (think that comes for free),
committers in that group should have write access.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message