[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ 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
[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142791#action_142791 ] Trevor L. Torrez commented on MSITE-302: Thanks :) Setting the version of the javadoc plugin to 2.4 in the parent pom reporting section (and deleting "false" from all poms) works, even without specifying the version of the site plugin. I could not however just specify the version in the pluginManagement section of the parent pom. Is this a bug or is it supposed to be that way? How does the site plugin know what version of the javadoc plugin to use? > 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
[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142507#action_142507 ] Dennis Lundberg commented on MSITE-302: --- Trevor, your problem comes from the Javadoc Plugin. Your log says that you are using version 2.3 of the Javadoc Plugin. When I tried your sample project, thanks for that by the way, it ran successfully for 'mvn install site-deploy' using Maven 2.0.9 and Javadoc Plugin 2.4. Then I hardcoded the Javadoc Plugin to version 2.3 and I got the same error that you did. My advise to all of you is to upgrade to Javadoc Plugin 2.4. > 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
[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142055#action_142055 ] Dennis Lundberg commented on MSITE-302: --- Trevor, can you try this with Site Plugin 2.0-beta-7? > 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.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
[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137832#action_137832 ] Ramon Havermans commented on MSITE-302: --- I will provide a sample, but it won't be soon because I don't have much time for it right now. > 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: > 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
[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137750#action_137750 ] Dennis Lundberg commented on MSITE-302: --- Can you provide a sample project for this? > 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: > 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
[jira] Commented: (MSITE-302) mvn install site-deploy does not follow the reactor build sequence
[ http://jira.codehaus.org/browse/MSITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124124 ] Ramon Havermans commented on MSITE-302: --- Correction the reactor sequence is Parent, Impl, Ejb. > 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 > > 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
