[
https://issues.apache.org/jira/browse/PLUTO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706565#action_12706565
]
Ate Douma commented on PLUTO-552:
---------------------------------
Hi Graig,
I think it would be better if we split the documentation for Pluto 1.x and 2.x
instead of this mixture within one site, similar to what we're in the process
of doing for Jetspeed 2.1.x and 2.2.x
Furthermore, as I have proposed elsewhere, I think we should consider moving
the documentation outside of the main release related trunk and keep it
separately like under /portals/site/pluto/pluto-1 and
/portals/site/pluto/pluto-2.
Anyway, besides that point, I think you're raising a valid technical concern
here.
It will indeed be a problem to have both the old and new pluginGroup defined
with the current plugin prefix which is the same for both.
The only way to solve that is changing the maven plugin prefix to like pluto2
for Pluto 2.0.
Good catch, this late in the game (we're planning to start the release process
for Pluto any time now) :)
I'll create a new JIRA issue for this and fix it which only requires a simple
configuration change in the plugin definition.
> 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/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
