[jira] (MRELEASE-431) Configuration of policy for calculating next (release) version

[ https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated MRELEASE-431: - Attachment: MRELEASE-431-v3.patch > Configuration of policy for calculating next (releas

[jira] (MRELEASE-431) Configuration of policy for calculating next (release) version

[ https://jira.codehaus.org/browse/MRELEASE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332905#comment-332905 ] Robert Munteanu commented on MRELEASE-431: -- [~rfscholte] - I've attached [^MRELEASE-431-

[jira] (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Foegen updated MRELEASE-594: --- Attachment: allowUnusedSnapshotsInDependencyManagement.patch Hi, please have a look at the patc

[jira] (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332916#comment-332916 ] Hans Aikema commented on MRELEASE-594: -- I agree with previous commenters that DISallowing sn

[jira] (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332916#comment-332916 ] Hans Aikema edited comment on MRELEASE-594 at 9/17/13 9:23 AM: --- I a

Maven parsing pom.xml incorrectly

I'm using Thrift in my Maven project, compiling my .thrift code to .java as part of the generate-sources step. To do this, I use the maven antrun plugin in my pom.xml, which executes a command line call to the thrift executable, and sends it the appropriate argument flags, such as "-out" and "--gen

[jira] (MJARSIGNER-13) signing in multi-module project fails on windows

[ https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332937#comment-332937 ] Chris Feldhacker commented on MJARSIGNER-13: Possibly related tidbit to consider: We

[jira] (MSITE-665) Site plugin version 3.2 seems to modify a project's classpath.

[ https://jira.codehaus.org/browse/MSITE-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332939#comment-332939 ] Christian Schulte commented on MSITE-665: - Could someone please perform a release of the sit

bug in parsing file ... comments

We ran into a parsing bug that prevents commenting out an option with a command line for maven. We tried commenting out (for testing purposes) the following plugin, which contains the "thrift --gen" command. The "--gen" caused a parse error in the file (looks like it thinks it needs to have --> bec