You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2011/02/05 19:49:30 UTC

[jira] Resolved: (COMMONSSITE-37) Gump profile

     [ https://issues.apache.org/jira/browse/COMMONSSITE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved COMMONSSITE-37.
-----------------------------

    Resolution: Not A Problem

The wildcard jar Gump feature seems to be sufficient, so no need for this.

> Gump profile
> ------------
>
>                 Key: COMMONSSITE-37
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-37
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Emmanuel Bourg
>
> I'd like to suggest the addition of a Gump profile in the parent POM. Gump needs to specify the name of the jar produced by the build, this was possible with Maven 1 by adding a maven.final.name system property, but it doesn't seem to be possible with Maven 2.
> The same effect can be obtained with the following profile in the POM:
> {code:xml}
> <profile>
>   <id>gump</id>
>   <activation>
>     <property>
>       <name>maven.final.name</name>
>     </property>
>   </activation>
>   <build>
>     <plugins>
>       <plugin>
>         <artifactId>maven-jar-plugin</artifactId>
>         <configuration>
>           <finalName>${maven.final.name}</finalName>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>
> </profile>
> {code}
> This profile has been tested on the Commons CLI 1.x POM

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira