Re: maven assembly plugin problem.

> Did you try the outputFileNameMapping in the dependencySet descriptor for
> assembly?
> <outputFileNameMapping>${artifact.artifactId}-${artifact.baseVersion}${dashC
> lassifier?}.${artifact.extension}</outputFileNameMapping>
>
> Notice the version it is ${artifact.baseVersion} and *not*
> ${artifact.version}
>
> Thanks,
> mohan kr
>
> -----Original Message-----
> From: Alexander Vaysberg [mailto:work@...]
> Sent: Wednesday, July 01, 2009 2:42 AM
> To: Maven Users List
> Subject: maven assembly plugin problem.
>
> Hi,
>
> I have a problem with assembly plugin. I have a standalone application
> and I make  for this app a jar with manifest. In manifest set  I a
> Main-Class and all dependencies for this app with jar plugin. That work
> fine. Than, I create with assembly the zip and get the all dependencies
> in lib. But I have a problem with SNAPSHOT jars. I have 5 SNAPSHOT jars.
> 3-Jars copy the assembly as so:- db-1.0.0-SNAPSHOT.jar, but for 2 -jars
> so same as: - firm-db-data-0.0.122-20090623.122812-2.jar. That is a date
> and time. For Deploying use I the Archiva.
>
>  The jar plugin write in Manifest firm-db-data-0.0.122-SNAPSHOT. But the
> assembly put the dependency as firm-db-data-0.0.122-20090623.122812-2. I
> need the solution for this problem.
>
> Alexander Vaysberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>