[
http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142797#action_142797
]
Dennis Lundberg commented on MSITE-302:
---------------------------------------
Unfortunately pluginManagement doesn't work for reporting plugin, only for
build plugins. It's a bug and it is in JIRA somewhere.
The site plugin doesn't know, it simple asks the POM for the version. If there
is no version there, then it becomes more difficult and a bit different
depending on which version of Maven you use. But it is recommended to add
versions to all plugins in your POM.
> mvn install site-deploy does not follow the reactor build sequence
> ------------------------------------------------------------------
>
> Key: MSITE-302
> URL: http://jira.codehaus.org/browse/MSITE-302
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Reporter: Ramon Havermans
> Attachments: msite302-maven-logs.zip, msite302.zip,
> OvereenkomstService_site-OvereenkomstService_site.1006-build.log
>
>
> We have a multi pom project. We have one parent, one EJB and one Impl
> project. The EJB project uses the Impl. The reactor sequence is Parent, EJB,
> Impl. When first doing "mvn install" and then "mvn site-deploy" the build is
> succesful. When doing "mvn install site-deploy" (on clean repository) the
> build fails because it first builds the Ejb instead of the Impl. It won't
> build because it is missing the installed Impl jar.
--
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
