Browse Source

Minor 1.9.7 to 1.9.8 version bumps in docs and Ant script

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
tags/V1_9_8_RC3
Alexander Kriegisch 2 years ago
parent
commit
99f1df6dc8
2 changed files with 11 additions and 12 deletions
  1. 3
    4
      build/build.xml
  2. 8
    8
      docs/developer/RELEASE.md

+ 3
- 4
build/build.xml View File

<property name="maven.central.repository" value="https://repo.spring.io/libs-snapshot-local/org/aspectj/aspectjweaver"/> <property name="maven.central.repository" value="https://repo.spring.io/libs-snapshot-local/org/aspectj/aspectjweaver"/>
--> -->


<!-- aspectjtools/target/aspectjtools-1.9.7-SNAPSHOT.jar -->
<!-- aspectjtools/target/aspectjtools-1.9.8-SNAPSHOT.jar -->


<property name="bin.jars.folder" value="${build.root}/dist/tools/lib"/> <property name="bin.jars.folder" value="${build.root}/dist/tools/lib"/>
<property name="src.jars.folder" value="${build.root}/src"/> <property name="src.jars.folder" value="${build.root}/src"/>
<property name="suffix" value="1.9.7-SNAPSHOT"/>
<property name="suffix" value="1.9.8-SNAPSHOT"/>


<!-- ASPECTJRT --> <!-- ASPECTJRT -->
<maven:deploy file="${build.root}/aspectjrt/target/aspectjrt-${suffix}.jar"> <maven:deploy file="${build.root}/aspectjrt/target/aspectjrt-${suffix}.jar">


<target name="publishtomaven_milestone" depends="maven.init"> <target name="publishtomaven_milestone" depends="maven.init">
<property name="build.root" value="/Users/aclement/gits/org.aspectj"/> <property name="build.root" value="/Users/aclement/gits/org.aspectj"/>
<property name="suffix" value="1.9.7.M1"/>
<property name="suffix" value="1.9.8.M1"/>


<property name="adjusted.release.type" value="milestone"/> <property name="adjusted.release.type" value="milestone"/>
<property name="maven.central.repository" value="s3://maven.springframework.org/${adjusted.release.type}"/> <property name="maven.central.repository" value="s3://maven.springframework.org/${adjusted.release.type}"/>




</project> </project>


+ 8
- 8
docs/developer/RELEASE.md View File

</settings> </settings>
``` ```


Assuming that you are currently working on version 1.9.7-SNAPSHOT, you simply call:
Assuming that you are currently working on version 1.9.8-SNAPSHOT, you simply call:


```shell ```shell
mvn clean deploy mvn clean deploy
git status git status


# Set release version in all POMs # Set release version in all POMs
mvn versions:set -DnewVersion=1.9.7.M2
mvn versions:set -DnewVersion=1.9.8.M2


# Verify if the POM changes are OK, then remove the POM backup files # Verify if the POM changes are OK, then remove the POM backup files
mvn versions:commit mvn versions:commit
```shell ```shell
# Commit the release POMs to Git (better do this from your IDE, verifying the # Commit the release POMs to Git (better do this from your IDE, verifying the
# changes before staging them for Git commit) # changes before staging them for Git commit)
git commit -am "Set version to 1.9.7.M2"
git commit -am "Set version to 1.9.8.M2"


# Tag release # Tag release
git tag V1_9_7_M2 git tag V1_9_7_M2


# Set new snapshot version, increasing the version number after a final release # Set new snapshot version, increasing the version number after a final release
mvn versions:set -DnewVersion=1.9.7-SNAPSHOT
mvn versions:set -DnewVersion=1.9.8-SNAPSHOT


# Verify if the POM changes are OK, then remove the POM backup files # Verify if the POM changes are OK, then remove the POM backup files
mvn versions:commit mvn versions:commit


# Commit the snapshot POMs to Git # Commit the snapshot POMs to Git
git commit -am "Set version to 1.9.7-SNAPSHOT"
git commit -am "Set version to 1.9.8-SNAPSHOT"


# Push the previous commits to GitHub # Push the previous commits to GitHub
git push origin git push origin
# repositories there are. # repositories there are.
mvn nexus-staging:rc-list mvn nexus-staging:rc-list
# [INFO] ID State Description # [INFO] ID State Description
# [INFO] orgaspectj-1106 CLOSED org.aspectj:aspectjrt:1.9.7.M2
# [INFO] orgaspectj-1106 CLOSED org.aspectj:aspectjrt:1.9.8.M2


# Use the ID of the corresponding CLOSED staging repository for releasing to # Use the ID of the corresponding CLOSED staging repository for releasing to
# Maven Central # Maven Central
``` ```


Tadaa! We have performed an AspectJ release. In a few minutes, the artifacts should appear on Maven Central somewhere Tadaa! We have performed an AspectJ release. In a few minutes, the artifacts should appear on Maven Central somewhere
under https://repo1.maven.org/maven2/org/aspectj/, e.g. AspectJ Tools 1.9.7.M2 would appear under
https://repo1.maven.org/maven2/org/aspectj/aspectjtools/1.9.7.M2/. As soon as you see the artifacts there instead of
under https://repo1.maven.org/maven2/org/aspectj/, e.g. AspectJ Tools 1.9.8.M2 would appear under
https://repo1.maven.org/maven2/org/aspectj/aspectjtools/1.9.8.M2/. As soon as you see the artifacts there instead of
"404 not found", you can announce release availability on the AspectJ mailing list and wherever else appropriate. "404 not found", you can announce release availability on the AspectJ mailing list and wherever else appropriate.


Finally, you probably want to publish the AspectJ installer (`installer/target/aspectj-[VERSION].jar`), e.g. by creating a Finally, you probably want to publish the AspectJ installer (`installer/target/aspectj-[VERSION].jar`), e.g. by creating a

Loading…
Cancel
Save