Out of curiosity, why is there a
difference between Package Explorer and Project Explorer on this? Is it that
the JDT extensions to Project Explorer don’t optimize away empty containers
like the Package Explorer does? If so, has there been a bug entered for this? I
know that the guys that maintains these extensions want to achieve feature
parity with Package Explorer so I imagine they would want to know about this…
Behalf Of Carl Anderson
Sent: Wednesday, March 18, 2009
To: General discussion of
project-wide or architectural issues.
Subject: Re: [wtp-dev] utility
Yes, in the Java EE perspective, it is expected behavior for any Java EE module
to display an EAR Libraries container. (Note that it does not show up in the
Java perspective.) This has been true since WTP 2.0 was shipped in June, 2007,
so it is not recent. The functionality added back then was quite a concept-
before that, every jar had to be placed on all of the various classpaths of all
of the modules within an EAR, and synchronization was a nightmare... now it is
simply the following entry in the .classpath file:
- Carl Anderson
Karen Moore <karen.moore@xxxxxxxxxx>
03/18/2009 11:06 AM
Please respond to
"General discussion of project-wide or architectural issues."
discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
just tried it again with the candidate M6 build S-3.1M6-20090318020101.
Max Rydahl Andersen wrote:
> On 17-03-2009 16:30, Karen Moore wrote:
>> If I create a new Faceted project and
just add the 'Utility Module'
>> facet, an empty user library named EAR
Libraries is added to the
>> project. I'm not sure when this
functionality came about, but it
>> seems fairly new to me. Is this
expected behavior? Dali is
>> currently using the Utility Module facet
in conjuction with the JPA
>> facet to create a JPA project, we do not
need the EAR Libraries.
> sounds very much like a bug - this happens to
you on 3.5 ?
> wtp-dev mailing list
wtp-dev mailing list