Pluto
  1. Pluto
  2. PLUTO-560

Change Pluto 2.0 maven pluto plugin prefix from pluto to pluto2 to prevent lookup clashes with the Pluto 1.x plugin

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: maven pluto plugin
    • Labels:
      None

      Description

      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>

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Ate Douma
              Reporter:
              Ate Douma
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development