[ http://jira.codehaus.org/browse/MNG-759?page=all ]
Dan Tran updated MNG-759:
-------------------------
Attachment: pom.xml
Here are important info about the attached pom.xml
- packaging = dll , i have my own lifecycle defined in my
maven-native-plugin's components.xml
- I have a dependency of type "lib" another lifecycle
- in the linkerStartOption, i have to hardcode the .lib file inorder to link
<linkerStartOption>
..\common\target\modiiop-windows-x86-common-7.0-SNAPSHOT.lib
</linkerStartOption>
- I dont have ArtifactHandler for type dll, lib. M2 uses the lifecycle name
as extention
name when It is not able to find the artifact Handler
> Empty artifacts when not using maven-core's default lifecycles
> ---------------------------------------------------------------
>
> Key: MNG-759
> URL: http://jira.codehaus.org/browse/MNG-759
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Environment: xp
> Reporter: Dan Tran
> Priority: Blocker
> Fix For: 2.0-beta-1
> Attachments: pom.xml
>
>
> maven project that uses external build lifecycle out side maven-core do not
> see it artifact list.
> in my case of using maven-native-plugin, my dll project has a .lib
> dependency, therefore
> the link phase will fail since the artifacts is empty (
> project.getArtifacts() returns empty set)
> and the linker do not have the required lib file to link to
> This is a blocking bug.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
