[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273424#comment-273424 ] Paul Gier commented on MNG-4112: Added the new properties in [r1147597|http://svn.apache.org/viewvc?view=revisionrevision=1147597]. Added integration test in [r1147598|http://svn.apache.org/viewvc?view=revisionrevision=1147598]. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273312#comment-273312 ] Benjamin Bentmann commented on MNG-4112: 3.0.3 (r1075438; 2011-02-28 11:31:09-0600) is another possibility. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273313#comment-273313 ] Martin Todorov commented on MNG-4112: - I think it would make more sense to a developer to have it in the form of x.y.z (for example 3.1.0). Perhaps there should be two properties. One for the Maven version (in the format I just mentioned) and one that contains the full version info, along with the revision and etc). Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273319#comment-273319 ] Anders Hammar commented on MNG-4112: I second Martin's suggestion. It would be good with a x.y.z property for profile activation or similar (not that I like profiles that much though) and the full string for other purposes. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273341#comment-273341 ] Paul Gier commented on MNG-4112: Ok, I agree two properties might be best. Anyone currently using the build-helper-maven-plugin to get the version will expect that maven.version contains just the simple version, so how about this? maven.version = 3.0.3 maven.build.version = Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600) Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273304#comment-273304 ] Paul Gier commented on MNG-4112: I'm not sure whether to use just the version number or the full version string for this. For example, 3.0.3 vs Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600). I'm leaning toward the full version info since this is similar to the version string available in the Ant property ant.version. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[
http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233535#action_233535
]
Paul Benedict commented on MNG-4112:
Adding ${maven.version} sounds like a good idea to me. However, a user should
NEVER be able to override it with -D/properties. I would make that an
outright error.
Set property containing the currently executing maven version.
--
Key: MNG-4112
URL: http://jira.codehaus.org/browse/MNG-4112
Project: Maven 2 3
Issue Type: Improvement
Reporter: Paul Gier
Fix For: 3.1
Attachments: MNG-4112-maven-embedder.patch
It would be helpful to have an easy way to access the current version of
maven. This might be accomplished by setting a property like maven.version
during startup that would be available to the pom and/or to plugins. This
could be used to record what version of maven was used during the build to
facilitate build reproducibility.
--
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
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233316#action_233316 ] Baptiste MATHUS commented on MNG-4112: -- I think this enhancement should really be added, also because of maven3 arriving. It would help knowing the used maven version used to build in the future. For instance, I'm currently trying to debug a maven3/maven2 build problem because of a badly built plugin (plugin.xml badly encoded, seems like a bug for maven 2.2.1). And I've a hard time dichotomizing things to correctly file the corresponding issue. Cheers Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172183#action_172183 ] Jason van Zyl commented on MNG-4112: I'll take a look later this week. There are two branches with lots of changes including the embedder, but this is not hard to add but the embedder is not the right place. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier Fix For: 2.1.1, 3.0-alpha-3 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171763#action_171763 ] Brett Porter commented on MNG-4112: --- yep, that looks exactly right - however, ISTR having that as a system property caused some grief. It would be better to inject it into the properties in the request after it is created - they are still available for interpolation. Combine that with an IT and I'd say commit away :) Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171630#action_171630 ] Brett Porter commented on MNG-4112: --- from the thread on the ML, it sounded like it was acceptable usage to grab the RuntimeInformation component (but add an integration test to Maven to make sure it survives any future refactoring). Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171654#action_171654 ] Jason van Zyl commented on MNG-4112: Just test the property is present, don't bind it to the RuntimeInformation because it will be different in Maven 3.x. The property being available is cool, specifically getting it from the RuntimeInformation component is not. Shouldn't be source dependent. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171658#action_171658 ] Paul Gier commented on MNG-4112: I looked into it a bit, and I should be able to get the version the same way that it's retrieved when you run mvn -version from the command line. It gets the information from the maven core jar, so it wouldn't be dependent on the RuntimeInformation. I wasn't sure if it should be a system property, or should the scope of the property be more localized? The RuntimeInformation could be used in a goal in a plugin (maybe the buildnumber plugin?) to allow the version to be accessed in maven pre 3.0. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171660#action_171660 ] Brett Porter commented on MNG-4112: --- that's exactly what the runtimeinformation does. I misunderstood what Jason meant on the list by making it work. If you're happy to settle for making a change to Maven, then putting maven.version into the context for interpolation and anything else that is going to grab it from the session is probably the right way to go. I had the feeling 3.x already has this, but 2.1 doesn't - would need to check though. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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
