You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Les Hazlewood (JIRA)" <ji...@apache.org> on 2009/03/12 14:42:50 UTC

[jira] Created: (INFRA-1937) JSecurity to Ki project migration

JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
            Reporter: Les Hazlewood


Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr

- The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
ki-dev@incubator.apache.org
ki-user@incubator.apache.org
ki-commits@incubator.apache.org

- Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718547#action_12718547 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

Sounds good - I'll notify the dev list about SVN - please go ahead in 2 hours.  And since there won't be any impact on list subscribers, please go ahead and rename them as well.  Thanks!

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688756#action_12688756 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

How do I go about getting a Hudson account?  My usual apache username/password isn't working...

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Assigned: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Cabrera reassigned INFRA-1937:
-----------------------------------

    Assignee:     (was: Alan Cabrera)

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696746#action_12696746 ] 

Alan Cabrera commented on INFRA-1937:
-------------------------------------

I'll hold on to this so we don't accidentally prematurely convert.

> JSecurity to Ki 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Alan Cabrera
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681316#action_12681316 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

Almost forgot - we'll need a Confluence space as well.

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718543#action_12718543 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

Please go ahead and do the SVN move as soon as possible - but please tell us when that time would be so we know when to expect it.

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688209#action_12688209 ] 

Nigel Daley commented on INFRA-1937:
------------------------------------

Or just rename it in the configure screen.

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718489#action_12718489 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<brettporter> I can help rename the lists. Did you want this to go ahead immediately? The SVN move is probably best done at a scheduled time to minimise interference with dev


> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Assigned: (INFRA-1937) JSecurity to Ki project migration

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Cabrera reassigned INFRA-1937:
-----------------------------------

    Assignee: Alan Cabrera  (was: Brett Porter)

> JSecurity to Ki 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Alan Cabrera
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Updated: (INFRA-1937) JSecurity to Ki project migration

Posted by "Justin Mason (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Mason updated INFRA-1937:
--------------------------------

    Component/s:     (was: Hudson)

removing Hudson from the components list, I think you're sorted on that count without our help.

> JSecurity to Ki 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718530#action_12718530 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

What impact, if any, will the list rename have on any existing subscribers?

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Updated: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Cabrera updated INFRA-1937:
--------------------------------

    Description: 
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!

  was:
Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr

- The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
ki-dev@incubator.apache.org
ki-user@incubator.apache.org
ki-commits@incubator.apache.org

- Finally, we'll need a new Hudson space under the name Ki and the old JSecurity one disabled.

Thanks!

        Summary: JSecurity to Shiro project migration  (was: JSecurity to Ki project migration)

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Alan Cabrera
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718842#action_12718842 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

Yep, they sure are.  It was weird though.  I sent out some messages to the list and a previous subscriber said he never saw them.   Perhaps it was a mail configuration or filter on his side.  Thanks!

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Updated: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot updated INFRA-1937:
-------------------------------------

    Assignee: Gavin

> 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: 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Justin Mason (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688110#action_12688110 ] 

Justin Mason commented on INFRA-1937:
-------------------------------------

regarding the Hudson space -- if you have a Hudson account, you should be able to do this; simply create a new Hudson "job", using the existing JSecurity one as its basis via "Copy an existing job", and change its names appropriately.

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689455#action_12689455 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<gmcdonald> Ki Space created http://cwiki.apache.org/confluence/display/KI/Index


> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ 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:

http://issues.apache.org/jira/browse/SHIRO

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 disabled.
> Thanks!

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


[jira] Assigned: (INFRA-1937) JSecurity to Ki project migration

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter reassigned INFRA-1937:
-----------------------------------

    Assignee: Brett Porter

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689460#action_12689460 ] 

Brett Porter commented on INFRA-1937:
-------------------------------------

Les, can you confirm whether you are going ahead? I got told this was on hold.

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718834#action_12718834 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

When I post to shiro-user and shiro-dev, the people that were previously subscribed to jsecurity-* don't seem to be receiving those messages.  Do they need to re-subscribe to the new lists?  I thought that would be transparent to them...

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696406#action_12696406 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<brettporter> I noticed you seem to be moving forward with the migration to Ki as the name. Would you like to schedule the mailing list changes now?


> JSecurity to Ki 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689467#action_12689467 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

We're still on hold pending some further investigation.  I'm hoping we'll get some resolution after Apache Con is over (people seem to be busy off-list).

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Closed: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot closed INFRA-1937.
------------------------------------

    Resolution: Fixed

> 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718588#action_12718588 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<joes4> svn moved.


> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696516#action_12696516 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

I'll clarify with the team today.  I think this should be OK unless anyone else feels otherwise.  I'll repost here again if/when it should be done.  Thanks for the reminder ;)

> JSecurity to Ki 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718483#action_12718483 ] 

Alan Cabrera commented on INFRA-1937:
-------------------------------------

JSecurity's final name is Shiro.

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696753#action_12696753 ] 

Brett Porter commented on INFRA-1937:
-------------------------------------

well I'm pretty sure I've seen other resources (in JIRA) already renamed. Admittedly, they are easier to change if so. You might want to keep an eye on that and just do it once :)

> JSecurity to Ki 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Alan Cabrera
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718839#action_12718839 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<brettporter> no, they don't need to subscribe. There are ~50 subs to each list. Are your posts appearing on http://mail-archives.apache.org/mod_mbox/incubator-shiro-user/200906.mbox/thread?


> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Updated: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated INFRA-1937:
--------------------------------

    Component/s: Confluence

> 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718587#action_12718587 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<joes4> mailing lists moved.


> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718545#action_12718545 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<joes4> the list rename won't impact subscribers at all.


> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718546#action_12718546 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<joes4> how about moving svn in 2 hours?


> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "Justin Mason (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688765#action_12688765 ] 

Justin Mason commented on INFRA-1937:
-------------------------------------

oops, thought you already had one!  details are here:

http://wiki.apache.org/general/Hudson

> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721018#action_12721018 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

Can someone also please set up a Confluence wiki space so we can migrate http://incubator.apache.org/ki/ ?

> 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: Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>
> 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.


[jira] Updated: (INFRA-1937) JSecurity to Shiro project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot updated INFRA-1937:
-------------------------------------

    Assignee:     (was: Gavin)

> 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
>
> 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.


[jira] Commented: (INFRA-1937) JSecurity to Shiro project migration

Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724559#action_12724559 ] 

Les Hazlewood commented on INFRA-1937:
--------------------------------------

Confluence http://incubator.apache.org/shiro is not yet set up.  Do I need to open a different ticket for this?

> 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.


[jira] Commented: (INFRA-1937) JSecurity to Ki project migration

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689456#action_12689456 ] 

#asfinfra IRC Bot commented on INFRA-1937:
------------------------------------------

<gmcdonald> You'll need to transfer/copy your pages from your current JSEC wiki, let me know when done so I can remove the JSEC space


> JSecurity to Ki 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: Hudson, Mailing Lists, Subversion
>            Reporter: Les Hazlewood
>            Assignee: Brett Porter
>
> Per this mail thread:  http://markmail.org/message/xxztclh7z2mqsmwr
> - The JSecurity project has voted to change its name to Ki.  Please set up a new subversion repository with the name ki 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:
> ki-dev@incubator.apache.org
> ki-user@incubator.apache.org
> ki-commits@incubator.apache.org
> - Finally, we'll need a new Hudson space under the name Ki 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.