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
