shale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SHALE-487) Update Master POM's Plugin Management
Date Sat, 19 Apr 2008 00:00:05 GMT

    [ https://issues.apache.org/struts/browse/SHALE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43651#action_43651
] 

Rahul Akolkar commented on SHALE-487:
-------------------------------------

Generally, its best to specify these for all plugins in use (if we're not using any of these,
we can remove them). The most important benefit is better reproducibility of builds, lacking
this we will fall back to using whatever versions our individual m2 installs deem fit.


> Update Master POM's Plugin Management
> -------------------------------------
>
>                 Key: SHALE-487
>                 URL: https://issues.apache.org/struts/browse/SHALE-487
>             Project: Shale
>          Issue Type: Improvement
>    Affects Versions: 1.0.5-SNAPSHOT
>            Reporter: Greg Reddin
>            Assignee: Greg Reddin
>            Priority: Critical
>
> The Master POM needs to be configured to prevent site-deployment. This requires the following
three things.
> 1) Lock plugins in master pom's <pluginManagement>
> 2) For release plugin in (1) have this:
> <plugin>
>  <groupId>org.apache.maven.plugins</groupId>
>  <artifactId>maven-release-plugin</artifactId>
>  <version>2.0-beta-7</version>
>  <configuration>
>    <goals>deploy</goals>
>  </configuration>
> </plugin>
> 3) Override release plugin (to permit default configuration including
> site deploys) in parent pom's <pluginManagement>.

-- 
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