You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org> on 2009/07/04 03:28:47 UTC
[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration
[ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727173#action_12727173 ]
#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------
<gmcdonald> jira/confluence set up, all done
> 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 disabled.
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.