[jira] Commented: (MNG-878) pom no longer correctly populated
[ http://jira.codehaus.org/browse/MNG-878?page=comments#action_46839 ] John Casey commented on MNG-878: This is sort of stream-of-consciousness, sorry about that... I was only thinking that anything which might have mutated the project files in order to arrive at that release should be included in the release-pom.xml, including command-line mojo invocations and command-line specified system properties. If these are left out, and I invoke: m2 clean:clean modello:xpp3-writer release:prepare ...oh, I guess that stuff won't make it into the actual release, though, will it? That means that only the plugins/configuration in the POM itself will actually be released, which makes your statement correct. Sorry for the confusion. > pom no longer correctly populated > - > > Key: MNG-878 > URL: http://jira.codehaus.org/browse/MNG-878 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2.0-beta-2 > > Original Estimate: 3 hours >Time Spent: 7 hours > Remaining: 0 minutes > > problems with the release pom generated by the release plugin: > - RELEASE is the populated version for a plugin, instead of being resolved > - plugins used in the build process but not explicitly listed in the pom are > not populated > - parent is not merge in -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-878) pom no longer correctly populated
[ http://jira.codehaus.org/browse/MNG-878?page=comments#action_46812 ] Brett Porter commented on MNG-878: -- its not the snapshot version that's the issue - that's not a big deal (there's no reason to pick a different version for the release plugin, we would just special case it if that was all it was - and besides, we should be using a released version :) The reason for excluding it was that that configuration shouldn't have been in there, at least in my opinion. Do you have an example of where it might be needed? > pom no longer correctly populated > - > > Key: MNG-878 > URL: http://jira.codehaus.org/browse/MNG-878 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 2.0-beta-2 > > Original Estimate: 3 hours >Time Spent: 7 hours > Remaining: 0 minutes > > problems with the release pom generated by the release plugin: > - RELEASE is the populated version for a plugin, instead of being resolved > - plugins used in the build process but not explicitly listed in the pom are > not populated > - parent is not merge in -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-878) pom no longer correctly populated
[ http://jira.codehaus.org/browse/MNG-878?page=comments#action_46668 ] John Casey commented on MNG-878: IMO, in order to support injection of command-line plugins, we'll have to have an audit trail in the MavenProject instance to record the plugins used and they're configurations - configuration from the command line also being a delta that we're not capturing here. I'm going to close this issue, because those would be new features, not bug fixes. > pom no longer correctly populated > - > > Key: MNG-878 > URL: http://jira.codehaus.org/browse/MNG-878 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Reporter: Brett Porter > Assignee: John Casey > Fix For: 2.0-beta-2 > > Original Estimate: 3 hours >Time Spent: 6 hours > Remaining: 2 hours > > problems with the release pom generated by the release plugin: > - RELEASE is the populated version for a plugin, instead of being resolved > - plugins used in the build process but not explicitly listed in the pom are > not populated > - parent is not merge in -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-878) pom no longer correctly populated
[ http://jira.codehaus.org/browse/MNG-878?page=comments#action_4 ] John Casey commented on MNG-878: not sure how to tackle the second item on this list...did you have something specific in mind? > pom no longer correctly populated > - > > Key: MNG-878 > URL: http://jira.codehaus.org/browse/MNG-878 > Project: Maven 2 > Type: Bug > Components: maven-release-plugin > Reporter: Brett Porter > Assignee: John Casey > Fix For: 2.0-beta-2 > > Original Estimate: 3 hours > Remaining: 3 hours > > problems with the release pom generated by the release plugin: > - RELEASE is the populated version for a plugin, instead of being resolved > - plugins used in the build process but not explicitly listed in the pom are > not populated > - parent is not merge in -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
