You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by James Carman <ja...@carmanconsulting.com> on 2008/02/23 15:58:23 UTC
[DISCUSS] Changes to commons-parent pom.xml...
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
Re: [DISCUSS] Changes to commons-parent pom.xml...
Posted by Niall Pemberton <ni...@gmail.com>.
On Sat, Feb 23, 2008 at 2:58 PM, James Carman
<ja...@carmanconsulting.com> 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.
How about attaching a patch to COMMONSSITE-23 - then its much easier
to see the changes you're proposing
http://issues.apache.org/jira/browse/COMMONSSITE-23
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Changes to commons-parent pom.xml...
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/23/08, Jochen Wiedmann <jo...@gmail.com> wrote:
> It would help me, if you'd describe the changes relative to the
> previous version rather than displaying the complete profile.
Well, basically I just changed where the generated site will go. The
directory where it will go is now calculated based on a property
${releaseManager} which defaults to ${user.name}. Here's the
directory where it will put it:
/home/${releaseManager}/public_html/${artifactId}-${version}/site
So, now all you have to do is:
mvn -Prc site:deploy
and it will upload the generated site to that directory.
>
> > Also, I made sure
> > that the signing occurs during the "package" phase and not "verify".
>
>
> What's the difference?
For me (and maybe I was doing it wrong), I had to include "verify" as
one of my goals to get it to sign, even when I was using the "rc"
profile.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Changes to commons-parent pom.xml...
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Sat, Feb 23, 2008 at 3:58 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> 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:
It would help me, if you'd describe the changes relative to the
previous version rather than displaying the complete profile.
> Basically, all I did was change the staging site deployment directory
> to go to a directory in my account's public_html.
That's surely something I would appreciate too.
> Also, I made sure
> that the signing occurs during the "package" phase and not "verify".
What's the difference?
> There is also a property declaration for the "releaseManager" property
> which defaults to ${user.name}.
Jochen
--
Look, that's why there's rules, understand? So that you think before
you break 'em.
-- (Terry Pratchett, Thief of Time)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Changes to commons-parent pom.xml...
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/23/08, Dennis Lundberg <de...@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
Re: [DISCUSS] Changes to commons-parent pom.xml...
Posted by Dennis Lundberg <de...@apache.org>.
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.
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
Re: [DISCUSS] Changes to commons-parent pom.xml...
Posted by James Carman <ja...@carmanconsulting.com>.
Okay, here's what I've done to proxy's pom.xml file. I've added my
own "rc" profile which basically does the same thing as the parent's
profile (I copied it). Only, it defines a different site deployment
url. The url is calculated based on a couple of properties. The
first is ${releaseManager} which is supposed to be the user id of the
person doing the release. The second is ${rcNumber} which corresponds
to the release candidate number. Based on that, the site will go in
(on people.apache.org):
/home/${releaseManager}/public_html/${artifactId}-${version}-rc${rcNumber}/site
or, in proxy's case for release candidate 4:
/home/jcarman/public_html/commons-proxy-1.0-rc4/site
So, to deploy the site, you do:
mvn -Prc site site:deploy -DrcNumber=4
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org