On Thu, Feb 21, 2013 at 10:47 PM, Roberto Sanchez Herrera/Mexico/IBM
<rsanchez@xxxxxxxxxxx> wrote:
Fred, is there a way to see the differences between 1.3.0 and 1.3.1?
Hi
m2e 1.3(.1) is available from the m2e release repository.
See [1] for the usual installation instructions.
m2e 1.3 focuses on bringing new APIs to be consumed by
3rd party adopters :
* New APIs to better control the project conversion to
Maven experience
- Added new <conversionParticipantConfiguration>
extension point to explicitely request ProjectConversionParticipant invocation
per packaging type (For Jan and Tobias ;-))
- Added a new ConversionEnabler, providing the
ability to preselect the packaging type during project conversion
- exclude project conversion participants for certain
projects
- Added new attributes to order project conversion
participants execution
* Added new API for Runtime classpath resolution of dependencies
referenced with classifiers (fixes some ejb-client resolution issues in
m2e-wtp)
* Introduced a new ResolverConfiguration#lifecycleMappingId
attribute, if specified, the corresponding ILifecycleMapping will be used
regardless of any other lifecycle mapping metadata
* Introduced a new flavor of AbstractProjectConfigurator#addNature
that accepts updateFlags parameter that allows finer control over new nature
creation.
* Added new AbstractJavaProjectConfigurator#getOutputLocation
method to provide better extensibility
The following behaviors changed in m2e 1.3
* The behavior for <execute/> mapping of maven plugins
has been changed to runOnIncremental=false by default, to prevent random
build loops
* The JDT conversion participant is now restricted to
the “jar” packaging by default. 3rd party adopters need to explicitely
request the maven-compiler-plugin to be configured, via an extension point
Regular m2e users will probably appreciate :
* some slight improvements made on the archetype selection
page
* import wizard now allows the (de)selection of individual
projects
See the changelog for everything fixed in the 1.3 version[2].
Since a number of new APIs were introduced in m2e 1.3,
we decided to use a separate discovery catalog, to prevent users from installing
incompatible m2e extensions in previous 1.1 & 1.2 versions. Unfortunately,
some build issues prevented us from getting that catalog ready before the
Juno SR2 aggregator build picked m2e 1.3.0 up. For that reason the
Juno SR2 distributions and canonical juno p2 repository embed version 1.3.0.
m2e 1.3.0 points at the "old" 1.1 discovery catalog.
The m2e 1.3.1 version that is available today points at
a new 1.3 discovery catalog.
The discovery catalog used in m2e can be manually changed
by editing your eclipse.ini and adding the -Dm2e.discovery.url parameter
-vmargs
...
...
-Dm2e.discovery.url="">http://download.eclipse.org/technology/m2e/discovery/directory-1.3.xml
You'll probably notice the new 1.3 catalog contains significantly
less entries than the previous version. m2e extensions owner need to make
sure their plugins are compatible with m2e 1.3 and request a catalog update
in BZ. This time I should be able to take some time to work on the catalog
requests backlog.
As usual please report any bugs to bugzilla[3]
Finally I'd like to give some kudos to Marcos and Roberto
from IBM who contributed a number of patches for this release, keep it
up guys ;-)
Fred
[1] http://www.eclipse.org/m2e/download/
[2] https://bugs.eclipse.org/bugs/buglist.cgi?list_id=4327661&query_format=advanced&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&product=m2e&target_milestone=Kepler%20M4&target_milestone=Kepler%20M5
[3] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E
"Have you tried turning it off and on again" - The IT Crowd _______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
