| Key: |
MAVEN-1726
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Manfred Mayer
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
For the extend tag, we can support http protocol, or another syntax like this <extend>${repo}/aGroupId/poms/anArtifactId-version.pom</extend>. Personally, I prefer the second solution.
With this features, users can share default pom parameter between all their projects, and it prepare the introduction of pom V4.
|
|
Description
|
For the extend tag, we can support http protocol, or another syntax like this <extend>${repo}/aGroupId/poms/anArtifactId-version.pom</extend>. Personally, I prefer the second solution.
With this features, users can share default pom parameter between all their projects, and it prepare the introduction of pom V4. |
Show » |
Sort Order:
|
CLONE -Add the possibility to use parent pom present in repo
For the extend tag the extend of a pom should be possible like this <extend>${maven.repo.local}/aGroupId/poms/anArtifactId-version.pom</extend>.
I think this would be a nice feature extension for Maven 1.1.
I created a patch for the current 1.1-beta3-SNAPSHOT, which parses the string in <extend>${maven.repo.local}/aGroupId/poms/anArtifactId-version.pom</extend>
and tries to download "aGroupId/poms/anArtifactId-version.pom" with the common artifact-download-mechanism from the specified remote repositories to the local repository. It also supports the SNAPSHOT mechanism, and works fine.
IMHO this change is not very invasive, because it only becomes active, if the specified parent pom cannot be found.