[
https://jira.codehaus.org/browse/MSITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280132#comment-280132
]
Lukas Theussl commented on MSITE-613:
-------------------------------------
Problem 1 is something I would expect, see MSITE-171. What is surprising is
that it works with 3.0-beta-3, need to investigate.
Problem 2 is also the expected behaviour if I understand your description
correctly. Running site will put the aggregated report into
target/site/cobertura/, running site:stage will put it into
target/staging/localhost/home/user/mysite/cobertura/, so that cross links from
within the staged site work correctly.
> 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
