www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-1937) JSecurity to Shiro project migration
Date Fri, 26 Jun 2009 14:27:07 GMT

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

Les Hazlewood commented on INFRA-1937:

Also, we'll need a new JIRA space set up:


Should this be a different ticket as well?  I'd be happy to do that rather than aggregate
these requests under this single ticket if that makes things easier...

> JSecurity to Shiro project migration
> ------------------------------------
>                 Key: INFRA-1937
>                 URL: https://issues.apache.org/jira/browse/INFRA-1937
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Confluence, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Gavin
> Per this mail thread:  http://markmail.org/thread/ihtntmuy2ey5ur7x
> - The JSecurity project has voted to change its name to Shiro.  Please set up a new subversion
repository with the name shiro instead of JSecurity and then migrate the existing codebase
over (should be a simple SVN copy).
> - We will also need new Incubator mailing lists for the project:
> shiro-dev@incubator.apache.org
> shiro-user@incubator.apache.org
> shiro-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Shiro and the old JSecurity one
> Thanks!

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

View raw message