I think this is because it uses a repo layout.
Are you defining the packaging in a plugin? If so, you could also
define an artifact handler that gives it the extension you want in the
repo.
- Brett
On 15/06/2008, at 12:02 AM, Raphaël Piéroni wrote:
Hi folks,
Using the appassembler plugin, i managed to get a proper dependency
directory.
But ther is something strange in my result, the project's artifact is
renamed from
foo.jar to foo.<packaging type>
My project uses it own kind of packaging type, and also, the
assemble goal
is call from inside a forked lifecycle.
I digged a little the code to search where could be the problem, and
i ended on
the appassemble plugin calling artifactInstaller.install/3
Then i searched the dependency and found that interface is defined in
maven-artifact. But it is also there i lost the trace. Which specific
implementation
is really used?
Also, the assemble goal is called just after the jar:jar goal which
created the correct
artifact type.
Thanks in advance for any diagnostic so i can create a jira in the
proper project.
I assume this problemmmmm is not for the appassemble plugin, but
dunno to which
it belongs.
Regards,
Raphaël
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
