[jira] Commented: (PLUTO-552) Change Pluto 2.0 maven groupid to org.apache.portals.pluto

["Craig Doremus (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PLUTO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706437#action_12706437 ] 

Craig Doremus commented on PLUTO-552:
-------------------------------------

Documentation on the Pluto web site's Getting Started page (http://portals.apache.org/pluto/v11/getting-started.html) needs to be changed to reflect the new pluginGroup name. Since the 1.1.x branch still keeps the org.apache.pluto pluginGroup name, the old and the new pluginGroup group needs to exist in settings.xml in order to do trunk and branch builds.
Is there any reason to believe that having both the old and the new pluginGroup name in settings.xml will be a problem?

> Change Pluto 2.0 maven groupid to org.apache.portals.pluto
> ----------------------------------------------------------
>
>                 Key: PLUTO-552
>                 URL: https://issues.apache.org/jira/browse/PLUTO-552
>             Project: Pluto
>          Issue Type: Task
>          Components: build system, general
>    Affects Versions: 2.0.0
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.0.0
>
>
> Pluto currently (probably from historical reason, dating back from pre maven 1.0 times) uses a maven groupid org.apache.pluto.
> We've voted to change the Pluto 2.0.0 groupid to org.apache.portals.pluto, see:
>   http://mail-archives.apache.org/mod_mbox/portals-pluto-dev/200904.mbox/%3C49E461CE.60200@douma.nu%3E

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