[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] Created: (WAGON-341) SCP Auth failed with local account as comment in pub key
SCP Auth failed with local account as comment in pub key Key: WAGON-341 URL: https://jira.codehaus.org/browse/WAGON-341 Project: Maven Wagon Issue Type: Bug Components: wagon-ssh Affects Versions: 1.0-beta-7 Environment: Ubuntu Natty Sun Java 6 build 25 Reporter: Emmanuel Hugonnet Auth failed with RSA or DSA private/public key authentication whith wagon while using the same key pair all is working fine from the cli using the 'classic' ssh and scp tools. My key pair RSA or DSA was geneated 'locally' so I have ehugonnet@my-laptop in the comment part. Using a key pair generated for my email address ehugon...@my-gmail.com the authentication is working fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-550) site:site attributes parameter does not work
[
https://jira.codehaus.org/browse/MSITE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273326#comment-273326
]
Lukas Theussl commented on MSITE-550:
-
The problem was the expression=${attributes} parameter annotation, apparently
that clashed with something else.
site:site attributes parameter does not work
--
Key: MSITE-550
URL: https://jira.codehaus.org/browse/MSITE-550
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: SebbASF
Attachments: MSITE-550.zip
The site:site goal has an optional attributes parameter:
{quote}
attributes:
The template properties for rendering the site.
* Type: java.util.Map
* Required: No
* Expression: ${attributes}
{quote}
However this does not work - no parameters are created for the template.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-550) site:site attributes parameter does not work
[
https://jira.codehaus.org/browse/MSITE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MSITE-550.
---
Resolution: Fixed
Fix Version/s: 3.0
2.4
Assignee: Lukas Theussl
Fixed in [r1147048|http://svn.apache.org/viewvc?rev=1147048view=rev] and
[r1147051|http://svn.apache.org/viewvc?rev=1147051view=rev]
site:site attributes parameter does not work
--
Key: MSITE-550
URL: https://jira.codehaus.org/browse/MSITE-550
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: SebbASF
Assignee: Lukas Theussl
Fix For: 2.4, 3.0
Attachments: MSITE-550.zip
The site:site goal has an optional attributes parameter:
{quote}
attributes:
The template properties for rendering the site.
* Type: java.util.Map
* Required: No
* Expression: ${attributes}
{quote}
However this does not work - no parameters are created for the template.
--
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] Created: (SUREFIRE-756) Allow ability to capture executed random runOrder for re-play purposes
Allow ability to capture executed random runOrder for re-play purposes -- Key: SUREFIRE-756 URL: https://jira.codehaus.org/browse/SUREFIRE-756 Project: Maven Surefire Issue Type: New Feature Components: Maven Failsafe Plugin, Maven Surefire Plugin Affects Versions: 2.9 Reporter: Joshua Spiewak Priority: Minor As a user of the runOrder=random feature, I would like to be able to capture a given ordering of tests and re-play that order, so that if a particular ordering exposes hidden dependencies between tests I can reproduce in my development environment, fix the problem, and then runs the tests again to confirm the fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (JXR-86) add standard skip configuration option
[ https://jira.codehaus.org/browse/JXR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed JXR-86. --- Resolution: Fixed Fix Version/s: 2.3 add standard skip configuration option -- Key: JXR-86 URL: https://jira.codehaus.org/browse/JXR-86 Project: Maven JXR Issue Type: Improvement Reporter: jieryn Assignee: Benson Margulies Priority: Trivial Fix For: 2.3 Please add the standard skip configuration option to skip execution of the plugin. Thanks! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (JXR-86) add standard skip configuration option
[ https://jira.codehaus.org/browse/JXR-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273357#comment-273357 ] Benson Margulies commented on JXR-86: - r1147229 | bimargulies | 2011-07-15 12:44:42 -0400 (Fri, 15 Jul 2011) | 2 lines [JXR-86] add standard skip configuration option add standard skip configuration option -- Key: JXR-86 URL: https://jira.codehaus.org/browse/JXR-86 Project: Maven JXR Issue Type: Improvement Reporter: jieryn Assignee: Benson Margulies Priority: Trivial Fix For: 2.3 Please add the standard skip configuration option to skip execution of the plugin. Thanks! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
