[ http://jira.codehaus.org/browse/MNG-2222?page=all ]
John Casey updated MNG-2222:
----------------------------
Fix Version: 2.2
Currently, multimodule builds which container interdependencies require at
least the 'package' phase to be run, in order for module artifacts to be
available as dependencies for other modules.
We should maybe look at pushing this back to the 'compile' phase if possible...
> dependency to dependency without source code fails
> --------------------------------------------------
>
> Key: MNG-2222
> URL: http://jira.codehaus.org/browse/MNG-2222
> Project: Maven 2
> Type: Bug
> Components: Dependencies
> Versions: 2.0.4
> Environment: Linux apple 2.6.12-1.1381_FC3smp #1 SMP Fri Oct 21 04:03:26 EDT
> 2005 i686 i686 i386 GNU/Linux
> java version "1.5.0_06"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)
> Reporter: Michael Mosmann
> Fix For: 2.2
>
>
> - project1
> - project2 (dep project1)
> - project3 (dep project2)
> - parent pom (module project1,project2,project3)
> mvn compile
> build project1
> build project2
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> build project3
> [INFO] Failed to resolve artifact.
> in project2 no target created
> -------------------------------
> Workaround
> put Noop.java into source so it will build some sources
--
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
