[
http://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120492
]
Chad Lyon commented on MJAR-68:
-------------------------------
right, but do you agree that in a multi-module project if you are skipping
tests (which includes skipping the build of the test JAR) then your modules
that rely on that test JAR to run their tests won't need the test JAR and
therefore should not fail with a "Missing dependency" (namely that test JAR)?
The reason they should not fail is because they aren't running tests!!! I'm
saying that the problem here is that in a sub-module POM if I specify:
<scope>test</scope>
for a dependency and then I skip tests then that dep should not even be checked
for.
> multi module release fails because of test-jar
> ----------------------------------------------
>
> Key: MJAR-68
> URL: http://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.
-
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
