Maven 2 & 3

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

depends upon

New Feature - A new feature of the product, which has yet to be developed. MNG-401 Add meta-data to root of Maven repository.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Brett Porter made changes -
Field Original Value New Value
Component/s design [ 11341 ]
Hide
Permalink
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.
Brett Porter made changes -
Fix Version/s 2.0-beta-1 [ 11040 ]
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. 		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.
Environment
Vincent Massol made changes -
Workflow jira [ 30918 ] Maven [ 37411 ]
Brett Porter made changes -
Priority Major [ 3 ] Critical [ 2 ]
Brett Porter made changes -
Remaining Estimate 4 hours [ 14400 ]
Original Estimate 4 hours [ 14400 ]
Assignee Brett Porter [ brettporter ]
Hide
Permalink
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
Permalink
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.
Brett Porter made changes -
Original Estimate 4 hours [ 14400 ]
Remaining Estimate 4 hours [ 14400 ]
Fix Version/s 2.0-beta-1 [ 11040 ]
Fix Version/s 2.0-beta-2 [ 11861 ]
Brett Porter made changes -
Fix Version/s 2.0-beta-2 [ 11861 ]
Fix Version/s 2.0-beta-3 [ 12015 ]
Brett Porter made changes -
Link This issue depends upon MNG-401 [ MNG-401 ]
Brett Porter made changes -
Fix Version/s 2.0-beta-3 [ 12015 ]
Fix Version/s 2.1 [ 11704 ]
Brett Porter made changes -
Assignee Brett Porter [ brettporter ]
Jason van Zyl made changes -
Priority Critical [ 2 ] Trivial [ 5 ]
Vincent Massol made changes -
Workflow Maven [ 37411 ] Maven New [ 47569 ]
Jason van Zyl made changes -
Fix Version/s 2.1 [ 11704 ]
Fix Version/s 2.1.x [ 13142 ]
Hide
Permalink
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
Brett Porter made changes -
Fix Version/s 2.x [ 13145 ]
Fix Version/s 2.1 [ 13142 ]
Summary server definitions should be reusable server definitions should be reusable - review use of repository IDs
Brett Porter made changes -
Priority Trivial [ 5 ] Major [ 3 ]

People

  • Assignee:
    Unassigned
    Reporter:
    Brett Porter
Vote (3)
Watch (3)

Dates

  • Created:
    Updated: