Change Pluto 2.0 maven pluto plugin prefix from pluto to pluto2 to prevent
lookup clashes with the Pluto 1.x plugin
-------------------------------------------------------------------------------------------------------------------
Key: PLUTO-560
URL: https://issues.apache.org/jira/browse/PLUTO-560
Project: Pluto
Issue Type: Task
Components: maven pluto plugin
Affects Versions: 2.0.0
Reporter: Ate Douma
Assignee: Ate Douma
Fix For: 2.0.0
As was brought up by Craig Doremus, the new Pluto 2.0 groupId,
org.apache.portals.pluto, can cause a lookup problem of the maven pluto plugin
if both the old groupId, org.apache.pluto, and the new groupId
are used/needed as maven settings.xml <pluginGroup> definition because they
currently use the same plugin prefix, pluto.
Solution is simple: change the plugin prefix for Pluto 2.0 to pluto2.
As result, the Pluto 2.0 plugin then needs to be invoked using:
$mvn pluto2:install -DinstallDir=<your appserver location>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
