[
https://issues.apache.org/jira/browse/NPANDAY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028953#comment-14028953
]
Lars Corneliussen commented on NPANDAY-623:
-------------------------------------------
Hi, you are right! Doesn*t like, that compile doesn't use final name - i think
it should.
But in the .NET-area there are some expectations to dll-names when
automatically resolving assemblies - so no easy choice.
Just changing final-name in the pom-model if it isn't yet custom-changed could
be another option.
> 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
> Environment: Maven 2.2.1
> Reporter: Greg Domjan
> Attachments: example.zip
>
>
> 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
(v6.2#6252)
