You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Miguel Almeida (JIRA)" <ji...@codehaus.org> on 2011/09/27 19:41:17 UTC
[jira] Commented: (MSITE-613) Regression in 3.0 - site:stage "Could
not resolve dependencies for project" on multi-module project
[ https://jira.codehaus.org/browse/MSITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280084#comment-280084 ]
Miguel Almeida commented on MSITE-613:
--------------------------------------
The 2nd issue is, on the same test case:
After 4 (site:stage with 3.0-beta3):
EXPECTED: The aggregate result of cobertura in parentA (ie, cobertura report with the aggregate reports of module1 and module2)
ACTUAL:
No report and the staging link points to file:///home/user/workspaces/impo/parentA/target/staging/localhost/home/user/mysite/cobertura/index.html
You can compare this the result of running the mvn cobertura:cobertura goal on parentA: you get a site/cobertura directory in the target with the correct report.
Is this an incompatibility of versions? Feel free to move this 2nd issue to a separate bug.
> Regression in 3.0 - site:stage "Could not resolve dependencies for project" on multi-module project
> ---------------------------------------------------------------------------------------------------
>
> Key: MSITE-613
> URL: https://jira.codehaus.org/browse/MSITE-613
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: multi module
> Affects Versions: 3.0
> Reporter: Miguel Almeida
> Attachments: parentA.zip
>
>
> Running the attached testcase, which has:
> parentA:|
> |module1
> |module2
> 1) Run: mvn site:site
> 2) Run mvn site:stage
> 2) fails with [ERROR] Failed to execute goal on project module2: Could not resolve dependencies for project org.example:module2:jar:1.0.0-SNAPSHOT: Failure to find org.example:module1:jar:1.0.0-SNAPSHOT in http://192.178.1.120:8082/archiva/repository/my-internal/ was cached in the local repository, resolution will not be reattempted until the update interval of my-internal has elapsed or updates are forced
> 3) Change plugin version to 3.0-beta-3
> 4) Repeat 1 and 2
> site:stage will run successfully
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira