[
https://issues.apache.org/jira/browse/NPANDAY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027505#comment-14027505
]
Greg Domjan edited comment on NPANDAY-623 at 6/13/14 7:03 AM:
--------------------------------------------------------------
Ok, I see where this might not have been covered now.
When using custom-lifecycle-maven-plugin externally generated items are
identified at install/deploy if they have the right name, but are not
identified at 'compile' because there is no compile goal, instead they are
identified by custom-lifecycle:set-artifact
Requires adding this to work around the issue
{code:xml}
<executions>
<execution>
<id>CSharpObjGen</id>
<phase>compile</phase>
<goals>
<goal>set-artifact</goal>
</goals>
</execution>
</executions>
{code}
Then, this is working differently to the compile-lifecycle. As custom-lifecycle
uses final name which will by default include a version number, compared to
compile-lifecycle wich will build a dll without version in the name and attach
it.
{noformat}
[INFO] [custom-lifecycle:set-artifact {execution: default-set-artifact}]
[WARNING] NPANDAY-105-001: Could not set expected artifact to
'E:\example\bar\target\bar-8.1.0-0-SNAPSHOT.dll', because it does not exist
{noformat}
So also to configure
{code:xml} <finalName>${project.artifactId}</finalName>{code}
was (Author: gdomjan):
Ok, I see where this might not have been covered now.
When using custom-lifecycle-maven-plugin externally generated items are
identified at install/deploy if they have the right name, but are not
identified at 'compile' because there is no compile goal, instead they are
identified by custom-lifecycle:set-artifact
Requires adding this to work around the issue
<executions>
<execution>
<id>CSharpObjGen</id>
<phase>compile</phase>
<goals>
<goal>set-artifact</goal>
</goals>
</execution>
</executions>
Then, this is working differently to the compile-lifecycle. As custom-lifecycle
uses final name which will by default include a version number, compared to
compile-lifecycle wich will build a dll without version in the name and attach
it.
[INFO] [custom-lifecycle:set-artifact {execution: default-set-artifact}]
[WARNING] NPANDAY-105-001: Could not set expected artifact to
'E:\example\bar\target\bar-8.1.0-0-SNAPSHOT.dll', because it does not exist
So also to configure
<finalName>${project.artifactId}</finalName>
> 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)
