commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <ja...@carmanconsulting.com>
Subject Re: [DISCUSS] Changes to commons-parent pom.xml...
Date Sat, 23 Feb 2008 17:47:19 GMT
On 2/23/08, Dennis Lundberg <dennisl@apache.org> wrote:
> We've has discussions about this previously. I stand by my position that
>  changes like these should tried out in at least one component release,
>  before they are included in the parent pom. It's a way of verifying that
>  the changes actually works during a release.
>

Well, the current proxy release will be using these changes.  So,
we'll see what everything looks like with it.

>
>  James Carman wrote:
>  > All,
>  >
>  > I've been working on the release candidate for commons-proxy-1.0 (if
>  > you couldn't tell by the SVN traffic).  I have created my own "rc"
>  > profile in proxy's pom.xml file.  I think we should push those changes
>  > to commons-parent.  Here's what it looks like:
>  >
>  >         <profile>
>  >             <id>rc</id>
>  >             <distributionManagement>
>  >                 <site>
>  >                     <id>stagingSite</id>
>  >                     <name>Release Candidate Staging Site</name>
>  >                     <url>
>  > ${commons.deployment.protocol}://people.apache.org/home/${releaseManager}/public_html/${artifactId}-${version}
>  >                     </url>
>  >                 </site>
>  >             </distributionManagement>
>  >             <build>
>  >                 <plugins>
>  >                     <plugin>
>  >                         <artifactId>maven-assembly-plugin</artifactId>
>  >                         <executions>
>  >                             <execution>
>  >                                 <goals>
>  >                                     <goal>attached</goal>
>  >                                 </goals>
>  >                                 <phase>package</phase>
>  >                             </execution>
>  >                         </executions>
>  >                     </plugin>
>  >                     <plugin>
>  >                         <artifactId>maven-gpg-plugin</artifactId>
>  >                         <configuration>
>  >                             <passphrase>${gpg.passphrase}</passphrase>
>  >                         </configuration>
>  >                         <executions>
>  >                             <execution>
>  >                                 <id>sign-artifacts</id>
>  >                                 <phase>package</phase>
>  >                                 <goals>
>  >                                     <goal>sign</goal>
>  >                                 </goals>
>  >                             </execution>
>  >                         </executions>
>  >                     </plugin>
>  >                     <plugin>
>  >                         <artifactId>maven-install-plugin</artifactId>
>  >                         <configuration>
>  >                             <createChecksum>true</createChecksum>
>  >                         </configuration>
>  >                     </plugin>
>  >                     <plugin>
>  >                         <artifactId>maven-source-plugin</artifactId>
>  >                         <executions>
>  >                             <execution>
>  >                                 <id>create-source-jar</id>
>  >                                 <goals>
>  >                                     <goal>jar</goal>
>  >                                 </goals>
>  >                                 <phase>package</phase>
>  >                             </execution>
>  >                         </executions>
>  >                     </plugin>
>  >                     <plugin>
>  >                         <artifactId>maven-release-plugin</artifactId>
>  >                         <configuration>
>  >                             <!-- Pass these arguments to the deploy plugin.
-->
>  >                             <arguments>-Prc</arguments>
>  >                         </configuration>
>  >                     </plugin>
>  >                     <plugin>
>  >                         <artifactId>maven-javadoc-plugin</artifactId>
>  >                         <executions>
>  >                             <execution>
>  >                                 <id>create-javadoc-jar</id>
>  >                                 <goals>
>  >                                     <goal>jar</goal>
>  >                                 </goals>
>  >                                 <phase>package</phase>
>  >                                 <configuration>
>  >                                     <source>${maven.compile.source}</source>
>  >                                 </configuration>
>  >                             </execution>
>  >                         </executions>
>  >                     </plugin>
>  >                 </plugins>
>  >             </build>
>  >         </profile>
>  >
>  > Basically, all I did was change the staging site deployment directory
>  > to go to a directory in my account's public_html.  Also, I made sure
>  > that the signing occurs during the "package" phase and not "verify".
>  > There is also a property declaration for the "releaseManager" property
>  > which defaults to ${user.name}.  After I've done this, all I have to
>  > do to get my release candidate's site published is:
>  >
>  > mvn -Prc clean site:stage-deploy
>  >
>  > And, when I want to create the distribution files:
>  >
>  > mvn -Prc clean site package
>  >
>  > The site goal is required because we want the javadocs in the
>  > distribution files (from what I've been told).  Is there not a way to
>  > get maven to do the javadocs when you do "package" so that they will
>  > be included in the distribution files?
>  >
>  > So, how does this sound to you guys?  I didn't want to go changing the
>  > parent pom without consulting with you folks first.
>  >
>
> > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  > For additional commands, e-mail: dev-help@commons.apache.org
>  >
>  >
>
>
>
> --
>
> Dennis Lundberg
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message