Making an update to JRE features, locally hosted

This is a quick draft, will be expanded when the p2 site arrives at their "real" hosting site. The scripts are all quite safe to run and work well. You will need bash and mvn installed.

Clone

• best is to clone it next to JCT/core which should be linked from or have the name core. Alternatively, to make version bumping work, export JCT_CORE_HOME=... to your environment.

git clone https://github.com/simlei/org.jcryptool.thirdparty --depth=1
cd org.jcryptool.thirdparty

Make changes

• Version changes should be done through the dedicated script bin/bump/jre-version-allplatforms which takes no arguments, queries for the version interactively.
• The JRE features are defined in: https://github.com/simlei/org.jcryptool.thirdparty/tree/master/projects/org.jcryptool.thirdparty.jre
• The p2 touchpoints (product setup key=value syntax files) are for each platform in the file p2.inf
• p2.inf can do scripting: https://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instructions_35#Actions

Scripts

The scripts are pretty self-explanatory. E.g. bin/build-jre-and-p2 is just two mvn -pl <project-list> -am clean package [install] calls. To use a localhost-ed site, you have to change {JCT-core}/o.j.target/o.j.target.target accordingly (look for a "jre" url and change to http://localhost:8080/site . )

# builds JRE features in /projects and their 
# respective p2 site in /releng

bin/build-jre-and-p2          

# hosts the JRE p2 site on locahost:8080/site 
# (alternatively, add -Djetty.port={port})

bin/publish-p2local-jre       

# guides you through a version bump for the JRE 
#  .. in o.j.thirdparty and ../core (by default). 
# Only targets specific files, no depth dearch mess. 
# It does 'sed -i {}' however, so use common sense.

bin/bump/jre-version-allplatforms

Troubleshooting

• One could temporarily mv ~/.m2 ~/.m2-stash but it is not required.