commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COMMONSSITE-37) Gump profile
Date Sat, 10 Jul 2010 13:49:49 GMT

    [ https://issues.apache.org/jira/browse/COMMONSSITE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887032#action_12887032
] 

Sebb commented on COMMONSSITE-37:
---------------------------------

This may no longer be necessary, as Gump now allows wildcard jar names

> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message