Jerome Dochez wrote:
> Ludovic Champenois wrote:
>> Jerome Dochez wrote:
>>> Ludovic Champenois wrote:
>>>> Sahoo wrote:
>>>>> We are going to remove javax.javaee-${version}.jar from web
>>>>> bundle. This is needed to fix [1] and [2]. We have not yet decided
>>>>> whether to make it part of glassfish bundle (a.k.a. full bundle)
>>>>> or not. The runtime does not need it.
>>> the only thing I can think of would be to make it available for
>>> developers, so that you could do
>>>
>>> javac -cp ~/glassfish/.../javaee.jar
>>>
>>> would that be useful for netbeans/eclipse in that regards ?
>> for a javac CLI user, yes,
>> but for NetBeans *and* Eclipse: no, as those IDEs do not use the
>> classpath from manifest to detect jar dependencies...
>> I guess it is the same with IntelliJ
> I can smell trouble coming...
>
> so you are planning to ship an empty shell javaee.jar with your plugins ?
> how will that work when dealing with the newly installed EJB 3.1
> container APIs ?
>
For long time, I have been of the opinion that we should distribute a
skinny javaee.jar (I think you are referring to with a different name)
in lib dir to not break existing build scripts. Next comes what will be
part of that skinny jar? Would such a jar contain only APIs currently
supported by the installation or all Java EE APIs known at a particular
point of time. My preference would be for the latter one. Such a jar can
then be used by javac, jspc, and IDEs. Are we allowed to do it?
Thanks,
Sahoo