Changelog for Maven Tools 4 Eclipse
These major features were implemented in this version:
- Orbit renaming
Orbit renaming means that all bundles which come from the Orbit project are moved to the group org.eclipse.orbit and the artifacts are renamed to orbit.*. This means org.apache.commons.lang is moved to org.eclipse.orbit:orbit.org.apache.commons.lang
The main reason for this is to prevent mixing bundles from Orbit and Maven Central.
- Class deletion
Class deletion is a new feature to delete classes from Eclipse bundles during the conversion. This is necessary to fix problems with org.apache.batik.pdf
- Suppressing of warnings in reports
Reports can contain an overwhelming number of warnings that you don't really care about or, worse, that you can't fix. The analyze command now accepts a file with warnings to ignore.
- The command p2ls can be used to examine the content of a remote or local P2 repository. The Swing UI allows to download individual bundles with and without source and/or dependencies
- The command show does the same for a local M2 repository
- The command download can download bundles by URL (using the Eclipse mirror infrastructure plus a local cache). See the script orbitSourceDownload.sh for an example.
- Because of bugs in the Maven Eclipse Plugin, MT4E now contains its own code to create POMs from Eclipse bundles. This also allows to handle nested JARs and source bundles.
- Many patches accept glob-style patterns.
- Optional dependencies no longer cause an entry in the "Missing Dependencies" section of the report
- Error and warning messages contain links to explanations in this wiki (overview)
- The command fails with an exit code != 0 in case of an error. That allows to use it in scripts.
The versions 0.12 and 0.11 were not released.
This is a maintenance release to fix the most pressing issues.