Copies of third party open source projects that are used in the build of GlassFish, along with tools to build those projects. GlassFish depends on the versions of these projects that we build, not directly on binaries produced by the originating project.
-
Check the derby.version in the POM. Don't override it on command line, it must be same as the redeployed artifact version - or a snapshot. Copy the derby.version to the bash property, see the example.
-
Example:
version=1.10.15
git checkout -b release
cd ant
mvn release:prepare -DpushChanges=false -DdevelopmentVersion=1.10.16-SNAPSHOT -DreleaseVersion=${version} -Dtag=Ant-${version} -Dresume=false
git push eclipse Ant-${version}
- Visit Eclipse CI and run the deployment for Derby and the tag: https://ci.eclipse.org/glassfish/view/Release/job/repackaged-deploy
- Visit Maven Central Deployments: https://central.sonatype.com/publishing/deployments
- Manually check that everything is as expected for the last time and press Drop or Publish.
- Wait until the package is distributed to the Maven Central. Not that UI indexes are updated with large latency, but artifacts will be available sooner.
- Finally push the branch and create a PR to master
git push eclipse release
-
Check the derby.version in the POM. Don't override it on command line, it must be same as the redeployed artifact version - or a snapshot. Copy the derby.version to the bash property, see the example.
-
Example:
version=10.17.1.0
git checkout -b release
cd derby
mvn release:prepare -DpushChanges=false -DdevelopmentVersion=10.17.1.0-SNAPSHOT -DreleaseVersion=${version} -Dtag=Derby-${version} -Dresume=false
git push eclipse Derby-${version}
- Visit Eclipse CI and run the deployment for Derby and the tag: https://ci.eclipse.org/glassfish/view/Release/job/repackaged-deploy
- Visit Maven Central Deployments: https://central.sonatype.com/publishing/deployments
- Manually check that everything is as expected for the last time and press Drop or publish.
- Wait until the package is distributed to Maven Central. Not that UI indexes are updated with large latency, but artifacts will be available sooner.
- Finally push th branch and create a PR to master
git push eclipse release
Same can be applied to other subprojects.