Project explorer J2EE content extensions duplicity - jst.j2ee vs jst.jee [message #1798736] |
Fri, 23 November 2018 12:21 |
Jozef Tomek Messages: 16 Registered: November 2018 |
Junior Member |
|
|
Hello
Latest Eclipse 2018-12 M2 (Eclipse IDE for Java EE Developers) user here.
The other day I was playing with enabling & disabling Java EE related extensions in 'Project explorer' / 'Filters and Customization' / 'Content', and came to conclusion that extensions:
- J2EE Application Deployment Descriptors
- J2EE Application Client Deployment Descriptors
- J2EE Connector Deployment Descriptors
- J2EE EJB Deployment Descriptors
- J2EE Web Deployment Descriptors
provided by org.eclipse.jst.j2ee.navigator.ui plugin are just not working at all.
On the other hand, those provided by org.eclipse.jst.jee.ui do work:
- Java EE Navigator Content EJB
- Java EE Navigator Content WEB
- Java EE Navigator Content EAR
- Java EE Navigator Content Application Client
- Java EE Navigator Content Connector
To be fair, I verified the behavior only for those for EJB, EAR and WAR, but I expect the other 2 behave the same.
I've seen same behavior since 1st Photon release.
My versions:
org.eclipse.jst.jee.ui_1.0.901.v201802201739 ("Eclipse Java EE Developer Tools")
org.eclipse.jst.j2ee.navigator.ui_1.1.700.v201802082131 ("J2EE Extensions to Common Navigator")
Is there any reason for this half-broken (at least for me) duplicity ?
[Updated on: Fri, 30 November 2018 06:00] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.02067 seconds