You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Manfred Mayer (JIRA)" <ji...@codehaus.org> on 2005/11/17 13:57:06 UTC
[jira] Created: (MAVEN-1726) CLONE -Add the possibility to use parent pom present in repo
CLONE -Add the possibility to use parent pom present in repo
------------------------------------------------------------
Key: MAVEN-1726
URL: http://jira.codehaus.org/browse/MAVEN-1726
Project: Maven
Type: New Feature
Reporter: Manfred Mayer
Fix For: 1.0.1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1726) CLONE -Add the possibility to use parent pom present in repo
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1726?page=all ]
Brett Porter updated MAVEN-1726:
--------------------------------
Priority: Blocker
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.
was:
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.
Fix Version: 1.1-beta-3
Environment:
> CLONE -Add the possibility to use parent pom present in repo
> ------------------------------------------------------------
>
> Key: MAVEN-1726
> URL: http://jira.codehaus.org/browse/MAVEN-1726
> Project: Maven
> Type: New Feature
> Reporter: Manfred Mayer
> Priority: Blocker
> Fix For: 1.1-beta-3, 1.0.1
> Attachments: MAVEN-1726.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1726) CLONE -Add the possibility to use parent pom present in repo
Posted by "Manfred Mayer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1726?page=comments#action_51220 ]
Manfred Mayer commented on MAVEN-1726:
--------------------------------------
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.
> CLONE -Add the possibility to use parent pom present in repo
> ------------------------------------------------------------
>
> Key: MAVEN-1726
> URL: http://jira.codehaus.org/browse/MAVEN-1726
> Project: Maven
> Type: New Feature
> Reporter: Manfred Mayer
> Fix For: 1.0.1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1726) CLONE -Add the possibility to use parent pom present in repo
Posted by "Manfred Mayer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1726?page=all ]
Manfred Mayer updated MAVEN-1726:
---------------------------------
Attachment: MAVEN-1726.txt
patch to the last comment (for downloading parent poms)
> CLONE -Add the possibility to use parent pom present in repo
> ------------------------------------------------------------
>
> Key: MAVEN-1726
> URL: http://jira.codehaus.org/browse/MAVEN-1726
> Project: Maven
> Type: New Feature
> Reporter: Manfred Mayer
> Fix For: 1.0.1
> Attachments: MAVEN-1726.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1726) CLONE -Add the possibility to use parent pom present in repo
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1726?page=all ]
Arnaud Heritier updated MAVEN-1726:
-----------------------------------
Version: 1.1-beta-3
1.0.2
1.1-beta-1
1.1-beta-2
Will not be fixed in maven 1.0.X
I'm not sure that it will not create side-effects. You can share the pom but what about properties (used in the parent pom for example ...) ???
> CLONE -Add the possibility to use parent pom present in repo
> ------------------------------------------------------------
>
> Key: MAVEN-1726
> URL: http://jira.codehaus.org/browse/MAVEN-1726
> Project: Maven
> Type: New Feature
> Versions: 1.1-beta-3, 1.0.2, 1.1-beta-1, 1.1-beta-2
> Reporter: Manfred Mayer
> Priority: Blocker
> Fix For: 1.1-beta-3, 1.0.1
> Attachments: MAVEN-1726.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org