[
http://jira.codehaus.org/browse/MRELEASE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191784#action_191784
]
Kai Hackemesser commented on MRELEASE-271:
------------------------------------------
I have a similar problem using Maven 2.0.10 and release plugin 2.0-beta-9. I
have here a project with 27 modules, from which 3 or so have sub modules. I'm
now using this preparationGoals trick above, but it doesn't solve the problem.
One of the sub modules fails to compile because it can't find the symbols
(classes) of the module that is installed as one of the first in the reactor
order. The library is definitely there, but somehow the compile process hasn't
it in its compile class path. I am not talking about test jars or the sources
from the test folder. What could that be?
I will attach the output of the release:prepare. the project that contains the
missing classes is utils-date. The module that fails at the end is "JEM v3.0
Connect", a sub module of "JEM v3.0". It has the module in question as a
transient compile dependency.
> perform goal sometimes fails with multi-module projects
> -------------------------------------------------------
>
> Key: MRELEASE-271
> URL: http://jira.codehaus.org/browse/MRELEASE-271
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-4, 2.0-beta-6
> Environment: XP
> Reporter: David Hoffer
> Attachments: MavenReleaseFailure.zip, release.zip,
> SuccessfulReleaseBuild.txt
>
>
> We have a multi-module maven project that has recently started failing in the
> release:perform goal.
> We have just added a couple more modules but do not know if that is the cause
> of the failure. It seems that the release:perform fails to compile the
> source after the SCM tag and checkout. The failure says that it cannot find
> a dependent jar but it is that jar that it is supposed to be building and
> releasing! I updated to use the latest 2.0-beta-6 release plugin version but
> this did not help.
> Upon receiving feedback in the maven users group that others have seen this
> behavior I followed their advise and added <configuration>
> <preparationGoals>clean install</preparationGoals></configuration> to my
> parent pom which did fix the problem.
> Why is the release goal failing now? When do I and when do I not need these
> changes to my pom? I will attach pom and build logs in hopes this can be
> fixed soon, let me know if you need additional information.
> -Dave
--
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
