[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307121#comment-307121 ] Andreas Pieber commented on MSITE-614: -- fair enough; still the question persists: is it a regression then or something we need to change in our configuration? site plugin failure when forking a lifecycle Key: MSITE-614 URL: https://jira.codehaus.org/browse/MSITE-614 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0 Reporter: Andreas Pieber Attachments: 5ebbfe13_maven-test.tar.gz If you execute mvn site in the attached test project it fails because of the forked cycles. The test project could therefore not be resolved in the maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306683#comment-306683 ] Dennis Lundberg commented on MSITE-614: --- There were some fairly large changes made to Site Plugin 3.0, so I'm not surprised that a project might work with Site Plugin 2.x but not with 3.x. site plugin failure when forking a lifecycle Key: MSITE-614 URL: https://jira.codehaus.org/browse/MSITE-614 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0 Reporter: Andreas Pieber Attachments: 5ebbfe13_maven-test.tar.gz If you execute mvn site in the attached test project it fails because of the forked cycles. The test project could therefore not be resolved in the maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306614#comment-306614 ] Andreas Pieber commented on MSITE-614: -- well, I know that commenting out features-maven-plugin works, but why does it work using version 2.3 of site? site plugin failure when forking a lifecycle Key: MSITE-614 URL: https://jira.codehaus.org/browse/MSITE-614 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0 Reporter: Andreas Pieber Attachments: 5ebbfe13_maven-test.tar.gz If you execute mvn site in the attached test project it fails because of the forked cycles. The test project could therefore not be resolved in the maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306493#comment-306493 ] Dennis Lundberg commented on MSITE-614: --- If I comment out org.apache.karaf.tooling:features-maven-plugin from test-assembly/pom.xml the build succeeds fine. My conclusion from that is that features-maven-plugin doesn't work correctly. site plugin failure when forking a lifecycle Key: MSITE-614 URL: https://jira.codehaus.org/browse/MSITE-614 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0 Reporter: Andreas Pieber Attachments: 5ebbfe13_maven-test.tar.gz If you execute mvn site in the attached test project it fails because of the forked cycles. The test project could therefore not be resolved in the maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290875#comment-290875 ] Florian Probst commented on MSITE-614: -- I'm getting an similar message in my project. It seems that the site Plugin can't execute the javadoc plugin for an submodule: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-cli) on project DE_Project: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.2:exploded (default) on project DE_IndustrialWiki_Web: Failed to copy file for artifact [-041:DE_Project_Ext:jar:1.0.0-SNAPSHOT:compile]: D:\FP\Projekte\\-041\Java\DE_Project\DE_Project_Ext\target\classes (Zugriff verweigert) - [Help 1] Dennis, what do you mean if you say the plugin is not correctly configured? As Andreas said, the same project works well with version 2.3 of the site plugin, while version 3.0 fails... site plugin failure when forking a lifecycle Key: MSITE-614 URL: https://jira.codehaus.org/browse/MSITE-614 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0 Reporter: Andreas Pieber Attachments: 5ebbfe13_maven-test.tar.gz If you execute mvn site in the attached test project it fails because of the forked cycles. The test project could therefore not be resolved in the maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
