You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Archimedes Trajano (JIRA)" <ji...@codehaus.org> on 2011/09/30 03:24:17 UTC
[jira] Issue Comment Edited: (MJAR-68) multi module release fails
because of test-jar
[ https://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280317#comment-280317 ]
Archimedes Trajano edited comment on MJAR-68 at 9/29/11 8:23 PM:
-----------------------------------------------------------------
This works well on 3.0.3
was (Author: trajano):
This also affects 3.0.3
> multi module release fails because of test-jar
> ----------------------------------------------
>
> Key: MJAR-68
> URL: https://jira.codehaus.org/browse/MJAR-68
> Project: Maven 2.x JAR Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: maven 2.0.5
> Reporter: Yuri Schimke
>
> The release plugin is failing in the prepare task
> mvn release:prepare
> seemingly because it can't find the test-jar that has just been built by the previous module i.e. built within.
> Are there some examples in the wild of using the test-jar on a multi module project that does releases?
> The (nasty) workaround I have for now, is to wait for the build to fail and then
> mvn install
> So the test-jar (and other artifacts) are in my local repository and then continue
> mvn release:prepare
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira