[jira] Commented: (MNG-2979) Cross module dependencies for multi-module site

["Mat Gessel (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95353 ] 

Mat Gessel commented on MNG-2979:
---------------------------------

I'm running into this issue in 2.0.6 as well. 

I'm going to attach several files: 
gwttk-m2.zip: a skeleton project demonstrating the issue (site goal fails on "sandbox" module)
package.txt: the successful result of running "mvn package" in the root module directory
site.txt: the failed result of running "mvn site" in the root module directory

(Note: I also noticed that you cannot compile/package the child module independently unless its dependencies are checked into the repository )


Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
----------
1) net.asquare:gwttk:jar:0.2.3-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
      mvn install:install-file -DgroupId=net.asquare -DartifactId=gwttk \
          -Dversion=0.2.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency: 
  	1) net.asquare:gwttk-sandbox:jar:0.2.3-SNAPSHOT
  	2) net.asquare:gwttk:jar:0.2.3-SNAPSHOT

----------
1 required artifact is missing.

for artifact: 
  net.asquare:gwttk-sandbox:jar:0.2.3-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

	at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
	at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
	at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
	... 16 more

> Cross module dependencies for multi-module site
> -----------------------------------------------
>
>                 Key: MNG-2979
>                 URL: http://jira.codehaus.org/browse/MNG-2979
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Artifacts, Dependencies, Documentation:  General, Sites & Reporting
>    Affects Versions: 2.0.5
>         Environment: Linux 2.6.18-gentoo-r6 #2 SMP PREEMPT Wed Feb 28 10:25:50 CET 2007 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
>            Reporter: Wally Wallou
>            Priority: Minor
>
> Considering a multi-module project A which declares two sub-projects (modules) B and C. Having module C indicating in its POM a dependency against module B. Compilation and packaging work great without having to install module B in maven local repository, it locate module B for module C using declared aggregation at top level project A.
> But for site goals it does not work, that is to say when maven try to generate site for module C it tells that module B artifact cannot be found. So we have to install module B to be able to generate module C site, whereas it is not necessary for compile or package goals.
> I think it would be great if site goals behaves like compile and package with aggregation. It would be more coherent, and avoid to have to run install just for site goals.

-- 
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