Pluto
  1. Pluto
  2. PLUTO-552

Change Pluto 2.0 maven groupid to org.apache.portals.pluto

    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: build system, general
    • Labels:
      None

      Description

      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

        Issue Links

          Activity

          Hide
          Ate Douma added a comment -

          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.

          Show
          Ate Douma added a comment - 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.
          Hide
          Craig Doremus added a comment -

          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?

          Show
          Craig Doremus added a comment - 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?
          Hide
          Ate Douma added a comment -

          Update of pluto groupId to org.apache.portals.pluto completed and committed for both Pluto and Jetspeed-2

          As result of this change, every developer using the pluto-maven-plugin
          please add a new:

          <pluginGroup>org.apache.portals.pluto</pluginGroup>

          entry to the <pluginGroups> section within your mvn settings.xml

          Show
          Ate Douma added a comment - Update of pluto groupId to org.apache.portals.pluto completed and committed for both Pluto and Jetspeed-2 As result of this change, every developer using the pluto-maven-plugin please add a new: <pluginGroup>org.apache.portals.pluto</pluginGroup> entry to the <pluginGroups> section within your mvn settings.xml

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development