maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Moved: (MEAR-66) finalName taken into account for full build but not for ear build
Date Tue, 22 May 2007 13:51:59 GMT


Stephane Nicoll moved MNG-3002 to MEAR-66:

    Affects Version/s:     (was: 2.0.6)
          Component/s:     (was: Dependencies)
           Complexity:   (was: Intermediate)
                  Key: MEAR-66  (was: MNG-3002)
              Project: Maven 2.x Ear Plugin  (was: Maven 2)

> finalName taken into account for full build but not for ear build
> -----------------------------------------------------------------
>                 Key: MEAR-66
>                 URL:
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: Windows XP; JDK1.5
>            Reporter: Mark Jeffery
> If I force a build of all projects via a parent pom (which build 2 EARS), then the finalName
attribute of the jar plugin is taken into account for the dependencies when they are built.
> If I quickly build one EAR only, via its pom, it retrieves the dependencies from the
repository, the finalName in the dependency pom is not taken into account and the version
number is added to the jar name.
> This breaks the manifest entries for the jars that were built with the forced build as
they still reference the specified name but the jars included in the EAR have the version
on the name.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message