Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Eclipse Web Tools Platform Project (WTP) » Project explorer J2EE content extensions duplicity - jst.j2ee vs jst.jee
Project explorer J2EE content extensions duplicity - jst.j2ee vs jst.jee [message #1798736] Fri, 23 November 2018 12:21 Go to next message
Jozef Tomek is currently offline Jozef TomekFriend
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


index.php/fa/34387/0/

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

Re: Project explorer J2EE content extensions duplicity - jst.j2ee vs jst.jee [message #1823119 is a reply to message #1798736] Thu, 19 March 2020 16:58 Go to previous message
Jozef Tomek is currently offline Jozef TomekFriend
Messages: 16
Registered: November 2018
Junior Member
Went on to try to check the source code of those plugins to understand the difference. After setting up dev environment for Eclipse plugins and fighting off all build errors, I realized I could have seen the difference for the whole time just by looking at plugin.xml of those plugins.

Long story short, org.eclipse.jst.j2ee.navigator.ui plugin ("J2EE Extensions to Common Navigator") handles old versions of J2EE technologies, whereas org.eclipse.jst.jee.ui plugin ("Eclipse Java EE Developer Tools") handles newer JavaEE technologies.

Mystery solved.
Topic closed
Previous Topic:Where can I get JSDT-core source code?
Next Topic:HTML editor auto-closing quotes
Goto Forum:
  


Current Time: Mon May 06 00:39:05 GMT 2024

Powered by FUDForum. Page generated in 0.03793 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top