[orbit-dev] EJB and javax.xml.rcp packages export versions

[David M Williams <david_williams@xxxxxxxxxx>]

> Is there a reason why the package export is without a version?

No, no good reason. Seems like we (or, at least me) seldom do unless/until
there is a reason ... such as known cases of multiple versions.

But, I'm open to doing it, if you think it is important and the right thing
to do. As far as I know, it would not "break" anyone. I have opened bug
373209 to discuss exporting with version numbers.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=373209

I'm a little surprised it wouldn't work as is, though, since I thought "0"
was interpreted as "satisfies anything" but maybe that's only with
"require-bundle"?

Thanks,





From:	"Kirchev, Lazar" <l.kirchev@xxxxxxx>
To:	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>,
Date:	03/03/2012 02:49 PM
Subject:	Re: [orbit-dev] New bundles in Orbit
Sent by:	orbit-dev-bounces@xxxxxxxxxxx



Hi all,

I had a problem with the ejb 3.0 bundle. When I added it to the build, the
build failed because of unsatisfied import of the ejb bundle to package
javax.xml.rpc.handler. I found out that this package is exported by Orbit
bundle javax.xml.rpc, and yet the build does not find it. The ejb bundle
imports it with a version range, but javax.xml.rpc exports it without a
version. This is the reason why the import remains unsatisfied.

Is there a reason why the package export is without a version?

Lazar

From: orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx]
On Behalf Of Kirchev, Lazar
Sent: Friday, March 02, 2012 9:07 AM
To: orbit-dev@xxxxxxxxxxx
Subject: [orbit-dev] New bundles in Orbit

Hi all,

I’m going to add to Orbit Tomcat 7.0.21 bundles (CQ 6292 , ATO CQ5540) and
EJB 3.0 API (CQ6291,  ATO CQ3944).

Lazar_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev