You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "?rjan Austvold (JIRA)" <ji...@codehaus.org> on 2005/10/31 06:43:33 UTC
[jira] Created: (MPRELEASE-13) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
Release plugin fails to update SNAPSHOTS in the dependencyManagement section
----------------------------------------------------------------------------
Key: MPRELEASE-13
URL: http://jira.codehaus.org/browse/MPRELEASE-13
Project: maven-release-plugin
Type: Bug
Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
Reporter: Ørjan Austvold
In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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: (MNG-1374) Release plugin fails to update
SNAPSHOTS in the dependencyManagement section
Posted by "mike perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1374?page=comments#action_53118 ]
mike perham commented on MNG-1374:
----------------------------------
I disagree, Emmanuel. See the last part of my comment on Dec-02-05.
> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
> Key: MNG-1374
> URL: http://jira.codehaus.org/browse/MNG-1374
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Versions: 2.0
> Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
> Reporter: Ørjan Austvold
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: prep.txt
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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: (MNG-1374) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
Posted by "mike perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1374?page=comments#action_52666 ]
mike perham commented on MNG-1374:
----------------------------------
I'm attempting to fix this issue but I'm finding that POM updating might require two passes. The issue is that the parent POM holds the depMgmt dep versions but it is updated FIRST and then the versions of the children are updated. So the parent 's depMgmt dependency version stays at 1.0.0-SNAPSHOT but the child project's actual released version is incremented to 1.0.0.
I think the release transform algorithm will need to change to something like this:
for each project
inc version
update dependencies
end
for each project
update depMgmt versions
writePom
end
My only question is whether the development transform should do the same? I would think that it would be a bad idea for all dependency versions to be blanket incremented without a real need. Instead I would think that we should NOT do the same for the release transform and instead force the developer to increment the depMgmt version when his project ACTUALLY requires an updated version.
> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
> Key: MNG-1374
> URL: http://jira.codehaus.org/browse/MNG-1374
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Versions: 2.0
> Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
> Reporter: Ørjan Austvold
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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: (MNG-1374) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1374?page=all ]
Lukas Theussl updated MNG-1374:
-------------------------------
Version: 2.0
Component: maven-release-plugin
> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
> Key: MNG-1374
> URL: http://jira.codehaus.org/browse/MNG-1374
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Versions: 2.0
> Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
> Reporter: Ørjan Austvold
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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] Closed: (MNG-1374) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1374?page=all ]
John Casey closed MNG-1374:
---------------------------
Resolution: Fixed
Fix Version: 2.0.1
applied. thanks, mike
> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
> Key: MNG-1374
> URL: http://jira.codehaus.org/browse/MNG-1374
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Versions: 2.0
> Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
> Reporter: Ørjan Austvold
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: prep.txt
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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: (MNG-1374) Release plugin fails to update SNAPSHOTS in the dependencyManagement section
Posted by "mike perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1374?page=all ]
mike perham updated MNG-1374:
-----------------------------
Attachment: prep.txt
Patch which appears to exhibit the correct (per my writeup) versioning behavior. Apoligies for the "noise" in the patch but I used Eclipse's code format to format per the maven spec and it reformatted a lot of the file.
> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
> Key: MNG-1374
> URL: http://jira.codehaus.org/browse/MNG-1374
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Versions: 2.0
> Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
> Reporter: Ørjan Austvold
> Attachments: prep.txt
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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] Closed: (MNG-1374) Release plugin fails to update SNAPSHOTS
in the dependencyManagement section
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1374?page=all ]
Emmanuel Venisse closed MNG-1374:
---------------------------------
Resolution: Fixed
ok Mike, you're right
> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
> Key: MNG-1374
> URL: http://jira.codehaus.org/browse/MNG-1374
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Versions: 2.0
> Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
> Reporter: Ørjan Austvold
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: prep.txt
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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] Reopened: (MNG-1374) Release plugin fails to update
SNAPSHOTS in the dependencyManagement section
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1374?page=all ]
Emmanuel Venisse reopened MNG-1374:
-----------------------------------
We need to update dependency versions in dependencyManagement to new version after tagging process
> Release plugin fails to update SNAPSHOTS in the dependencyManagement section
> ----------------------------------------------------------------------------
>
> Key: MNG-1374
> URL: http://jira.codehaus.org/browse/MNG-1374
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Versions: 2.0
> Environment: Maven 2.0 (release-plugin version: 2.0-beta3)
> Reporter: Ørjan Austvold
> Assignee: John Casey
> Fix For: 2.0.1
> Attachments: prep.txt
>
>
> In a multi project the parent-pom can specify "standard" versions for dependencies within the project group. I have found it convenient to also list group-members with versions in this section so that all child artifact within the group simply specifies inter-group artifact dependencies without versions.
> The release plugin fails to alter SNAPSHOT dependencies within the dependencyMangement section. The tagged version of child poms gets instead the correct version explicitly stated in their dependency section.
> It seems a bit strange that dependencies on artifacts within a group must have dependencies on other artifacts within the group listed with version numbers.
--
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