[ http://jira.codehaus.org/browse/MNG-692?page=all ]
Kenney Westerhof resolved MNG-692:
----------------------------------
Assign To: Kenney Westerhof
Resolution: Fixed
As it turns out, the artifacts _are_ pointing to the jars (in the target
directory),
but the maven-ejb-plugin didn't update the Artifact file for the project.
Personally, I think it's a bad idea to give the packaging plugins that
responsibility,
or even to allow them to modify that setting (breaks abstraction layers).
The lifecycle executor should verify if the artifact (if any) exists after the
'package' lifecycle,
and update the project Artifact with the correct file.
> Project.getArtifacts() returns artifacts with getFile() pointing to
> target/classes when that project is in the reactor
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-692
> URL: http://jira.codehaus.org/browse/MNG-692
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Kenney Westerhof
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> MNG-249 solves the reactor-awareness by setting the File of an Artifact to
> the Build.outputDirectory if the
> project is in the reactor (more or less).
> This leads to problems when plugins want to copy those artifacts: they're now
> pointing to directories
> (try the ear plugin for instance).
--
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]
