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 Fri, 18 Apr 2008 20:22:05 GMT

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

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

I've added some commonly used plugins to the master pom's <pluginManagement>. Related
to that change, we should:

(a) Try out the builds, verify these are the versions we want
(b) Update to the latest versions if possible, where numbers listed are not the latest
(c) Reconcile the parent pom with this change


> 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