Greg Domjan commented on NPANDAY-623:

It may be a Maven2 specific issue?

Bumped version numbers so that there where no stored artifacts.
Ran ```mvn clean compile -pl foo -am``` on a solution (
     foo (depends on bar, baz)

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] NPANDAY-901-003: Could not satisfy required dependencies for scope test

Embedded error: NPANDAY-148-001: Could not resolve project dependencies

1) com.somegroup:bar:dotnet-library:8.1.0-1-SNAPSHOT
2) com.somegroup:baz:dotnet-library:8.1.0-1-SNAPSHOT

As I've only requested building to the compile phase it shouldn't be trying to 
resolve dependencies for the test phase.
This can be hidden if you have run to install previously, and it can lead to 
issue of linking against previous objects outside the reactor.

> Support reactor reference to other modules at compile phase 
> ------------------------------------------------------------
>                 Key: NPANDAY-623
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-623
>             Project: NPanday
>          Issue Type: Bug
>          Components: Maven Plugins
>    Affects Versions: 1.4-incubating, 1.5.0-incubating
>            Reporter: Greg Domjan
> When building multiple artifacts with dependencies in the reactor it appears 
> to be currently required that you build to the "install" phase.  
> This can actually be a bug - see 
> http://developer-blog.cloudbees.com/2012/12/maven-and-hack.html
> Even if not a bug, this goes against some common practices such as used in 
> the release-plugin which attempts to test the build by running all projects 
> to compile stage only.
> In comparison the maven reactor allows for dependency resolution in Java JAR 
> dependencies as soon as the compile phase is run. It does this by pointing 
> the artifact file to the local class folder.
> NPanday could take similar action and point the file to the local target file 
> as soon as compile.

This message was sent by Atlassian JIRA

Reply via email to