Maven 2 & 3
  1. Maven 2 & 3
  2. MNG-139

server definitions should be reusable - review use of repository IDs

    Details

    • Number of attachments :
      0

      Description

      currently if multiple projects use the same server for deployment, we are relying on inheritence to share the definition, or it must be copied. This applies similarly to the SCM connection and the dist/site management settings.

      It would be a good idea to be able to declare these elements in a deployed artifact.

      It may still be reasonable to do this through inheritence, but there is a chance we'll hit the need for multiple inheritence (because multiple projects inherit things from different sources), so we should enumerate the use cases and verify it.

      eg.
      A B
      / \ / \
      C D E

      Where A and B declare two different things that D uses both of, but which C and E desire only to inherit one of.

      This essentially using composition for some elements instead of inheritence.

        Issue Links

          Activity

          Hide
          Brett Porter added a comment -

          consider or close this. we're butting up against some nastiness syncing id's at the moment.

          Show
          Brett Porter added a comment - consider or close this. we're butting up against some nastiness syncing id's at the moment.
          Hide
          Bob Allison added a comment -

          One place where problems can occur is using a mirror for codehaus while building m2. In the m2 top-level plugin, there is a repository named "snapshots" which points to "http://snapshots.maven.codehaus.org/maven2/" and a pluginRepository named "snapshots" which points to "http://snapshots.maven.codehaus.org/maven2/plugins". Creating a mirror of "snapshots" causes problems during the integration tests. The name used for the pluginRepository needs to be changed so it does not match the regular repository (that change allows the integration tests to succeed whether the pluginRepository is mirrored or not).

          Show
          Bob Allison added a comment - One place where problems can occur is using a mirror for codehaus while building m2. In the m2 top-level plugin, there is a repository named "snapshots" which points to "http://snapshots.maven.codehaus.org/maven2/" and a pluginRepository named "snapshots" which points to "http://snapshots.maven.codehaus.org/maven2/plugins". Creating a mirror of "snapshots" causes problems during the integration tests. The name used for the pluginRepository needs to be changed so it does not match the regular repository (that change allows the integration tests to succeed whether the pluginRepository is mirrored or not).
          Hide
          Brett Porter added a comment -

          scope is beyond what I was intending to implement - might push this back.

          One thing I'd like to do is eliminate the <id/> element in the repository definition, and instead store a unique key in the metadata at the root of the repository. That can be looked up once and retained, and used as the key for defining servers in settings.xml, ensuring consistency between environments, while still being portable across changing urls or different hostnames/redirects.

          Show
          Brett Porter added a comment - scope is beyond what I was intending to implement - might push this back. One thing I'd like to do is eliminate the <id/> element in the repository definition, and instead store a unique key in the metadata at the root of the repository. That can be looked up once and retained, and used as the key for defining servers in settings.xml, ensuring consistency between environments, while still being portable across changing urls or different hostnames/redirects.
          Hide
          Brett Porter added a comment -

          still wanted, will write proposal for 2.2

          Show
          Brett Porter added a comment - still wanted, will write proposal for 2.2
          Show
          Jason van Zyl added a comment - Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
          Hide
          Jason van Zyl added a comment -

          Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

          Show
          Jason van Zyl added a comment - Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

            People

            • Assignee:
              Unassigned
              Reporter:
              Brett Porter
            • Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: