http://permalink.gmane.org/gmane.comp.apache.maven.issues hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.apache.maven.issues/38136 <pre> [ https://jira.codehaus.org/browse/MNG-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5477. ------------------------------ Resolution: Fixed Fix Version/s: (was: 3.1.0) 3.1.0-alpha-1 Assignee: Herve Boutemy done in [4db66fd0|http://git-wip-us.apache.org/repos/asf/maven/commit/4db66fd0] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Herve Boutemy (JIRA 2013-05-20T22:18:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38135 <pre> [ https://jira.codehaus.org/browse/MNG-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325314#comment-325314 ] Herve Boutemy commented on MNG-5477: ------------------------------------ unit test added in [ed1501ec|http://git-wip-us.apache.org/repos/asf/maven/commit/ed1501ec] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Herve Boutemy (JIRA 2013-05-20T21:23:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38134 <pre> [ https://jira.codehaus.org/browse/MRELEASE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325312#comment-325312 ] Lewis Henderson commented on MRELEASE-567: ------------------------------------------ I think that this is either a similar or the same problem that I have... I am trying to do a release:prepare (clean verify) and get errors with missing dependencies that are in the current build. I had the problem with the maven-dependency-plugin where I was using the 'copy' goal when I should have been using the 'copy-dependencies' goal. The copy-dependencies goal first looks in the current reactor, then the local repository and then remote. This is the same requirement for other 'bundling' type plugins. The 'jarResource's should be looked up in the same way. This is a show stopper for the release plugin when using the webstart (or other) bundling plugins. -- This message is automatically generated by JIRA. If you think it was sent incorrect</pre> Lewis Henderson (JIRA 2013-05-20T20:49:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38133 <pre> [ https://jira.codehaus.org/browse/MNG-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5481. ------------------------------ Resolution: Fixed Assignee: Herve Boutemy moved to https://issues.apache.org/jira/browse/MPOM-43 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Herve Boutemy (JIRA 2013-05-20T20:23:53 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38132 <pre>Hervé Boutemy created MPOM-43: --------------------------------- Summary: Prevent dependency with too recent bytecode from creeping in unnoticed Key: MPOM-43 URL: https://issues.apache.org/jira/browse/MPOM-43 Project: Maven POMs Issue Type: Improvement Components: maven Affects Versions: MAVEN-23 Reporter: Hervé Boutemy As a followup to http://www.mail-archive.com/dev-3+t1Dttqs2kyzMRdD/IqWQ&lt; at &gt;public.gmane.org/msg96659.html here's a patch that configures an additional enforcer rule to prevent using dependencies that were compiled with a compiler more recent than the maximum allowed. see https://jira.codehaus.org/browse/MNG-5481 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Hervé Boutemy (JIRA 2013-05-20T20:21:17 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38131 <pre> [ https://jira.codehaus.org/browse/MRELEASE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DK closed MRELEASE-838. ----------------------- Resolution: Not A Bug Fix Version/s: 2.4.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> DK (JIRA 2013-05-20T19:06:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38130 <pre> [ https://jira.codehaus.org/browse/MRELEASE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325306#comment-325306 ] DK commented on MRELEASE-838: ----------------------------- Sorry you can ignore the second command i tried -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> DK (JIRA 2013-05-20T16:09:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38129 <pre>DK created MRELEASE-838: --------------------------- Summary: Creating a branch from a tag does not work Key: MRELEASE-838 URL: https://jira.codehaus.org/browse/MRELEASE-838 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.4.1 Reporter: DK Priority: Blocker I'm trying to use the following command to create a branch from an SVN tag: mvn release:branch -DupdateBranchVersions=true -DupdateVersionsToSnapshot=false -DupdateWorkingCopyVersions=false -DbranchName=MyBranch However, it makes commits to the tag which it shouldn't and also updates the version and dependencies in the branch pom to the latest SNAPSHOT. I also tried: mvn release:branch -DupdateBranchVersions=true -DupdateVersionsToSnapshot=false -DupdateDependencies=false -DupdateWorkingCopyVersions=false -DsuppressCommitBeforeBranch=true -DbranchName=MyBranch And this fails with: [ERROR] Error resol</pre> DK (JIRA 2013-05-20T16:03:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38128 <pre> [ https://jira.codehaus.org/browse/MRELEASE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325307#comment-325307 ] DK commented on MRELEASE-838: ----------------------------- The following command: mvn release:branch -DupdateBranchVersions=true -DupdateVersionsToSnapshot=false -DupdateDependencies=false -DupdateWorkingCopyVersions=false -DsuppressCommitBeforeBranch=true -DbranchName=MyBranch Results in: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.1:branch (default-cli) on project myproject: Cannot perform a remote tag or branch without committing the working copy first. -&gt; [Help 1] [ERROR] But I cannot/should not commit to the tag -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> DK (JIRA 2013-05-20T16:17:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38127 <pre> [ https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325305#comment-325305 ] Michael Osipov edited comment on MSKINS-72 at 5/20/13 9:28 AM: --------------------------------------------------------------- I am not able to apply the patch myself: 403 Forbidden. Please apply patch until ACL has been clarified. was (Author: michael-o): I am not able to apply the patch myself: 403 Forbidden. Please apply patch unless ACL has been clarified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Michael Osipov (JIRA 2013-05-20T14:29:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38126 <pre> [ https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-72: --------------------------------- Assignee: Olivier Lamy (was: Michael Osipov) Remaining Estimate: 0 minutes Original Estimate: 0 minutes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Michael Osipov (JIRA 2013-05-20T14:27:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38125 <pre> [ https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-72: --------------------------------- Attachment: MSKINS-72.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Michael Osipov (JIRA 2013-05-20T14:25:53 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38124 <pre> [ https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-72: --------------------------------- Attachment: mylyn-context.zip -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Michael Osipov (JIRA 2013-05-20T14:25:53 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38123 <pre> [ https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325305#comment-325305 ] Michael Osipov commented on MSKINS-72: -------------------------------------- I am not able to apply the patch myself: 403 Forbidden. Please apply patch unless ACL has been clarified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Michael Osipov (JIRA 2013-05-20T14:25:53 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38122 <pre> [ https://jira.codehaus.org/browse/MSKINS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSKINS-72: ------------------------------------ Assignee: Michael Osipov (was: Olivier Lamy) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Michael Osipov (JIRA 2013-05-20T14:16:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38121 <pre> [ https://jira.codehaus.org/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325297#comment-325297 ] Thorsten Gawantka edited comment on MCOMPILER-203 at 5/20/13 7:03 AM: ---------------------------------------------------------------------- An example for this more than suboptimal behavior is the annotation processor for the static static metamodel generator of eclipselink. This processor will add the complete eclipselink dependencies to the compile-classpath which is IMHO MORE than suboptimal. Also the version 3.1 of maven-compiler-plugin is affected ;-) was (Author: thgaw): An example for this more than suboptimal behavior is the annotation processor for the static static metamodel generator of eclipselink. This processor will add the complete eclipselink dependencies to the compile-classpath which is IMHO MORE than suboptimal. Oh also the version 3.1 of maven-compiler-plugin is affected ;-) </pre> Thorsten Gawantka (JIRA 2013-05-20T12:04:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38120 <pre> [ https://jira.codehaus.org/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325297#comment-325297 ] Thorsten Gawantka edited comment on MCOMPILER-203 at 5/20/13 7:02 AM: ---------------------------------------------------------------------- An example for this more than suboptimal behavior is the annotation processor for the static static metamodel generator of eclipselink. This processor will add the complete eclipselink dependencies to the compile-classpath which is IMHO MORE than suboptimal. Oh also the version 3.1 of maven-compiler-plugin is affected ;-) was (Author: thgaw): An example for this more than suboptimal behavior is the annotation processor for the static static metamodel generator of eclipselink. This processor will add the complete eclipselink dependencies to the compile-classpath which is IMHO MORE than suboptimal. -- This message is automatically generated by JIRA. If you thi</pre> Thorsten Gawantka (JIRA 2013-05-20T12:02:54 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38119 <pre> [ https://jira.codehaus.org/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325297#comment-325297 ] Thorsten Gawantka commented on MCOMPILER-203: --------------------------------------------- An example for this more than suboptimal behavior is the annotation processor for the static static metamodel generator of eclipselink. This processor will add the complete eclipselink dependencies to the compile-classpath which is IMHO MORE than suboptimal. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Thorsten Gawantka (JIRA 2013-05-20T12:02:54 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38118 <pre> [ https://jira.codehaus.org/browse/MASSEMBLY-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=325296#comment-325296 ] Arnaud Heritier commented on MASSEMBLY-554: ------------------------------------------- I met also this inconsistent behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Arnaud Heritier (JIRA 2013-05-20T11:58:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38117 <pre> [ https://jira.codehaus.org/browse/SUREFIRE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hobson updated SUREFIRE-997: --------------------------------- Description: The TestNG {{suiteXmlFiles}} configuration parameter is of type {{File}} and as such only supports suite XML files relative to the current project. It would be handy to be able to reference suite XML files in other test dependencies by using classpath resources. This would provide an explicit method of executing tests from dependencies rather than the scanning mechanism added in SUREFIRE-569. was: The TestNG {{suiteXmlFiles}} configuration parameter is of type {{File}} and as such only supports suite XML files relative to the current project. It would be handy to be able to reference suite XML files in other test dependencies by using classpath resources. This would provide an explicit method of executing tests from dependencies rather than the scanning mechanism added in SUREFIRE-569. </pre> Mark Hobson (JIRA 2013-05-20T11:36:52 http://permalink.gmane.org/gmane.comp.apache.maven.issues/38116 <pre> [ https://jira.codehaus.org/browse/SUREFIRE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hobson updated SUREFIRE-997: --------------------------------- Description: The TestNG {{suiteXmlFiles}} configuration parameter is of type {{File}} and as such only supports suite XML files relative to the current project. It would be handy to be able to reference suite XML files in other test dependencies by using classpath resources. This would provide an explicit method of executing tests from dependencies rather than the scanning mechanism added in SUREFIRE-569. was: The TestNG {{suiteXmlFiles}} configuration parameter is of type {{File}} and as such only supports suite XML files relative to the current project. It would be handy to be able to reference suite XML files in other test dependencies by using classpath resources. This would provide an explicit method of executing tests from dependencies rather than the scanning mechanism added in SUREFIRE-569. </pre> Mark Hobson (JIRA 2013-05-20T11:36:52 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.maven.issues