Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Critical
Fix Version/s: 4.0.0.Alpha1
Affects Version/s: 4.0.0.Alpha1
Component/s: maven
Labels:
- new_and_noteworthy

Release Note Text:

Hide
All the JBoss Maven tooling related to Java EE features now depends on m2e-wtp from Eclipse.org, which conflicts with m2eclipse-wtp (from github) .

It's recommended to install JBoss Tools over a clean Eclipse installation or, uninstall m2eclipse-wtp completely if you have it installed already

Show
All the JBoss Maven tooling related to Java EE features now depends on m2e-wtp from Eclipse.org, which conflicts with m2eclipse-wtp (from github) . It's recommended to install JBoss Tools over a clean Eclipse installation or, uninstall m2eclipse-wtp completely if you have it installed already
Release Note Status:
Not Required

Since m2e-wtp is moving to eclipse.org, we need to make sure our Maven plugins are compatible with it. Github's m2eclipse-wtp should not be used anymore.

During a transition period (i.e. spanning a few milestone releases), we can try to make our Maven plugins compatible with both m2e-wtp versions but this is NOT guaranteed.

This ticket depends on ~~JBIDE-12292~~

is blocked by

JBIDE-12292 Use m2e-wtp dev builds in composite sites and aggregate builds (rather than in Juno target platform)

Closed

Assignee:: Fred Bricon

Reporter:: Fred Bricon

Writer:: Isaac Rooskov (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2012/07/06 9:28 AM

Updated:: 2020/09/14 5:28 AM

Resolved:: 2012/12/02 9:16 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates