You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Martin Desruisseaux <ma...@geomatys.fr> on 2013/07/08 18:04:41 UTC
Release experiment
I'm not very familiar with the "mvn release" plugins, but maybe it is
designed for a context slightly different than our current one? (unless
I missed some configuration parameters). I though that we could create
the 0.3 branch before to release, since some material are removed on
that branch compared to the trunk. But the plugins replaced the
0.3-SNAPSHOT version numbers by 0.4-SNAPSHOT on the branch, leaving
trunk unchanged. Strangely, it created a 0.3 tags which still have the
0.3-SNAPSHOT version number instead than a plain 0.3. Maybe we have done
something wrong?
I wonder, given that there is some additional steps to do (e.g. replace
the "0.3-SNAPSHOT" string in some Java constants too), we may have to
customize the release process anyway. Does anyone have some experience
about customizing the Maven release process? Or what about exploring the
opportunity of creating a Ant task?
My understanding is that "mvn release" just performs version number
change and commit a tag on the SVN. Signing the JAR files is done by the
Maven "package" phase, which would still be executed. Is that right?
Martin
Re: Release experiment
Posted by Adam Estrada <es...@gmail.com>.
Very much appreciated, Chris!
On Fri, Jul 12, 2013 at 4:32 PM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> I will have some time to get back to the 0.3 RC this weekend.
>
> Will keep you guys up to date on progress.
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
> -----Original Message-----
> From: Martin Desruisseaux <ma...@geomatys.fr>
> Organization: Geomatys
> Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
> Date: Tuesday, July 9, 2013 9:10 AM
> To: "dev@sis.apache.org" <de...@sis.apache.org>
> Subject: Re: Release experiment
>
> >Le 09/07/13 15:27, Martin Desruisseaux a écrit :
> >> Correction: after more trials, a better Maven command seems to be:
> >>
> >> mvn clean site deploy -Papache-release
> >
> >Correction again: needs to run "install" in a separated build command
> >before "site" (skipping tests is okay):
> >
> > mvn clean install -DskipTests
> > mvn site deploy -Papache-release
> >
> >
> > Martin
> >
>
>
Re: Release experiment
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 12/07/13 22:32, Mattmann, Chris A (398J) a écrit :
> I will have some time to get back to the 0.3 RC this weekend.
>
> Will keep you guys up to date on progress.
Thanks a lot! Please let me known if you have any issue, maybe I could
make proposal for some of them.
Martin
Re: Release experiment
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
I will have some time to get back to the 0.3 RC this weekend.
Will keep you guys up to date on progress.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.fr>
Organization: Geomatys
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Tuesday, July 9, 2013 9:10 AM
To: "dev@sis.apache.org" <de...@sis.apache.org>
Subject: Re: Release experiment
>Le 09/07/13 15:27, Martin Desruisseaux a écrit :
>> Correction: after more trials, a better Maven command seems to be:
>>
>> mvn clean site deploy -Papache-release
>
>Correction again: needs to run "install" in a separated build command
>before "site" (skipping tests is okay):
>
> mvn clean install -DskipTests
> mvn site deploy -Papache-release
>
>
> Martin
>
Re: Release experiment
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 09/07/13 15:27, Martin Desruisseaux a écrit :
> Correction: after more trials, a better Maven command seems to be:
>
> mvn clean site deploy -Papache-release
Correction again: needs to run "install" in a separated build command
before "site" (skipping tests is okay):
mvn clean install -DskipTests
mvn site deploy -Papache-release
Martin
Re: Release experiment
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 09/07/13 12:06, Martin Desruisseaux a écrit :
> So if I'm understanding right, performing the following command should
> do the same thing than "mvn release:perform"?
>
> svn checkout https://svn.apache.org/repos/asf/sis/tags/0.3
> cd 0.3
> mvn deploy
Correction: after more trials, a better Maven command seems to be:
mvn clean site deploy -Papache-release
The reason for the "site" part is that the default "javadoc:jar" doesn't
seem to use the configuration declared in the pom.xml (links, groups,
taglets, etc.). Note that the above command does not deploy the site, so
the extra generated files should not hurt.
Martin
Re: Release experiment
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Hello Chris
I have deleted the "tags/0.3" directory and created a new one with the
recent changes in the <groupId> values. I have also set the version
number to "0.3" manually. I think that for this first release, it was
better to do the changes manually because the version number in pom.xml
were not the only things to edit. Other things to do for the release are:
* Remove the <pluginRepositories> section in the root pom.xml, because
it references http://repository.apache.org/snapshots and release are
not allowed to use snapshots. This section should not be needed
anymore for release anyway, since the sis-build-helper plugin should
become reachable like other modules.
* Edit static final constants containing the version number in two
Java classes:
o core/sis-build-helper/src/main/java/org/apache/sis/internal/taglet/Module.java
o core/sis-utility/src/main/java/org/apache/sis/util/Version.java
* Edit documentation in index.apt and download.apt.
So if I'm understanding right, performing the following command should
do the same thing than "mvn release:perform"?
svn checkout https://svn.apache.org/repos/asf/sis/tags/0.3
cd 0.3
mvn deploy
Do we have a release manager we can volunteer for trying the above? If
it works, I will try to automatize the process.
Thanks,
Martin
Le 08/07/13 18:38, Mattmann, Chris A (398J) a écrit :
> Yep I'm seeing the same behavior Martin, which is different in Maven 2.2.1
> which properly using the mvn release:prepare and mvn release:perform steps:
>
> 1. Replaced version #s in the trunk with Version N+1-SNAPSHOT
> 2. Created the tag with the un-SNAPSHOT versioned elements (e.g., 0.3)
>
> I'm also seeing the same behavior now in Apache OODT as I try and release
> version 0.6. So, there is something up in the new Maven 3 version that I
> am for the first time using in both of these instances to perform the
> release. I was going to go ahead and blow away the 0.3 tag in SIS, after
> performing some more experiments. I'm wondering if some properties in
> the <scm> section of our poms are incorrect (also in OODT) that Maven 2.2.1
> would happily ignore, but that Maven 3 is not happy about especially during
> the mvn release stages.
>
> So if you can shed some light into the above, thanks and great. Otherwise,
> I'm also investigating it.
>
> Cheers,
> Chris
Re: Release experiment
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
Yep I'm seeing the same behavior Martin, which is different in Maven 2.2.1
which properly using the mvn release:prepare and mvn release:perform steps:
1. Replaced version #s in the trunk with Version N+1-SNAPSHOT
2. Created the tag with the un-SNAPSHOT versioned elements (e.g., 0.3)
I'm also seeing the same behavior now in Apache OODT as I try and release
version 0.6. So, there is something up in the new Maven 3 version that I
am for the first time using in both of these instances to perform the
release. I was going to go ahead and blow away the 0.3 tag in SIS, after
performing some more experiments. I'm wondering if some properties in
the <scm> section of our poms are incorrect (also in OODT) that Maven 2.2.1
would happily ignore, but that Maven 3 is not happy about especially during
the mvn release stages.
So if you can shed some light into the above, thanks and great. Otherwise,
I'm also investigating it.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.fr>
Organization: Geomatys
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Monday, July 8, 2013 9:04 AM
To: Apache SIS <de...@sis.apache.org>
Subject: Release experiment
>I'm not very familiar with the "mvn release" plugins, but maybe it is
>designed for a context slightly different than our current one? (unless
>I missed some configuration parameters). I though that we could create
>the 0.3 branch before to release, since some material are removed on
>that branch compared to the trunk. But the plugins replaced the
>0.3-SNAPSHOT version numbers by 0.4-SNAPSHOT on the branch, leaving
>trunk unchanged. Strangely, it created a 0.3 tags which still have the
>0.3-SNAPSHOT version number instead than a plain 0.3. Maybe we have done
>something wrong?
>
>I wonder, given that there is some additional steps to do (e.g. replace
>the "0.3-SNAPSHOT" string in some Java constants too), we may have to
>customize the release process anyway. Does anyone have some experience
>about customizing the Maven release process? Or what about exploring the
>opportunity of creating a Ant task?
>
>My understanding is that "mvn release" just performs version number
>change and commit a tag on the SVN. Signing the JAR files is done by the
>Maven "package" phase, which would still be executed. Is that right?
>
> Martin
>