[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Convention for replacing potentially limited JRE packages

The main convention is not to interfere with what is already distributed by Eclipse :)
And, there is this version in the about to be released Indigo:
javax.transaction_1.1.1.v201105210645.jar

You might see if that existing one, from Orbit project, suffices?

http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/

HTH
 




From:        Ben Cox <ben_cox_21@xxxxxxxxxxx>
To:        <equinox-dev@xxxxxxxxxxx>
Date:        06/07/2011 07:14 PM
Subject:        [equinox-dev] Convention for replacing potentially limited JRE        packages
Sent by:        equinox-dev-bounces@xxxxxxxxxxx




Hi All,

There are a number of packages that are exported by the system bundle that are limited in comparison with their J2EE counterparts - I'm specifically thinking of javax.transaction and javax.transaction.xa at this point in time.

If I supply the full J2EE versions of these packages in a bundle of my own, is there any convention for a version of those packages?

Thanks,
Ben_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev