Hi Andy, it is the correct behavior, ${finalName} is used only on your local
${maven.build.dir} but when maven try to install/deploy to remote
remote, it uses the enforced naming. ${artifactid}-${version}.${ext}
There were similar discussions on war plugin in the last couple weeks.
-D
On 9/7/05, Andy Glick <[EMAIL PROTECTED]> wrote:
>
> Brett Porter wrote:
> > Sorry for the confusion - I was referring to the modello plugin
> > configuration:
> >
>
> Wanted to let you know that I just did an install build and the artifact
> does appear in the target directory with the final name as assigned in the
> profile "maven-model-2.0-beta-1-SNAPSHOT-all.jar" but the version name
> installed in maven.repo.local was different and was missing the all
> classifier "maven-model-2.0-beta-1-SNAPSHOT.jar". Each timestamp reflected
> the same minute, so they aren't from different runs.
>
> Should I report this in JIRA?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
