Version 2.1
Description
This is a pre-release of new jazz development environment features. The main reason for including non-stable features is the release of 6.0.6.1, which has warranted the inclusion of a semi-automated workflow for creating a new runtime from an sdk zip file. The new database and sdk_files included in this pull request have been created using said feature. Dog fooding seems reasonable in this case.
This is the first release of files that have been created using this new technique.
The new features are currently unstable, but have proven to work for creating the new 6.0.6.1 files.
Summary
- You are safe to upgrade if you are using the jazz development environment for creating plugins
- If you want to be very safe, create a backup before you go ahead with the upgrade instructions
- There are new features that you are welcome to use at your own risk
Upgrading
This release includes a new upgrade command. It updates an existing jde
folder with the files required for using 6.0.6.1 and some of the new features without touching any files in the user
folder.
Please note that running the upgrade command multiple times can result in false-positive errors. You can ignore them unless you think files are being overwritten that are inside your user folder.
Fresh installation
If you are creating a fresh environment with this release, just follow the previous wiki instructions on how to create a working environment.
Upgrading an existing installation
Upgrading to a new release of the jde should be fairly simple. If you are going ahead with this, you are probably interested in using 6.0.6.1 for development.
Preparation
You have to download the new releases required for the jde to run.
- Server SDK
- Windows CCM or Linux CCM
- Copy the
RTC-SDK-Server-6.0.6.1.zip
to thejde/sdks
folder - Copy the
JTS-CCM-keys.zip
to thejde/servers
folder
Upgrade Procedure
Note that this is the first release including an upgrade procedure. If you encounter problems, please open an issue with as many details as you can!
- If you want to be on the safe side, consider doing a full backup
./gradlew backup --mode=full
. Note that this can take a considerable amount of time. - Get the newest changes:
git remote update && git pull
- Run the upgrade command:
./gradlew upgrade
You are now ready to create a 6.0.6.1 runtime
./gradlew setup
will create a runtime for 6.0.6.1
Features
Stable Features
- 6.0.6.1 support
Incubating Features
- Automated database and sdk file creation from a new RTC release
- Creation of P2 repositories from run times
- Automatic maven configuration of local p2 repositories
- Target Platform exploration in an automatically deployed eclipse IDE
Documentation of new features is incomplete, as they are not stable. Previous functionality should continue to work in the same way. As a general rule of thumb, all gradle tasks that are in the Jazz Development Environment
group are considered stable for general users. Reference the build.gradle file for all tasks.
All other tasks are either for hacking on the tool itself (jde development
group), or unstable if they are unclassified. You are welcome to test these features, but be aware that they are:
- Going to change in breaking ways
- Probably unstable in usage
Before working with them, I advise backing up your environment or creating an isolated environment for testing purposes. Be aware that the p2 repository features can break your maven configuration. A backup is created in the backup folder, but you will have to manually address breakage to your maven configuration!
Bug fixes
- Improved handling of release versions
- Improved logging
Notes
Once again, thank you @MartinBenninger for helping with testing of this new release.