Right. At the very least we should establish a consistency setup
where the team members have J2SE 1.4 installed (I did not). Having 1.4 first
on the BREE is more community/developer friendly because it will “work” without
having to install another JRE and get an XML parser/API from somewhere (e.g.,
eRCP). However, as we saw recently, it is easy for other references to creep
in (including refs to XML stuff without a corresponding import and refs to
classes/methods not in 1.4 or Foundation 1.1)
We should also be consistent about it. Some bundles in p2 have Foundation
1.1 first. Others have J2SE1.4 first.
In any event, this discussion is why I posted here. We should
come to an agreement on the approach and move forward based on that.
Jeff
From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Watson
Sent: Tuesday, February 19, 2008 10:02 AM
To: Equinox development mailing list
Subject: Re: [equinox-dev] [prov] use of Foundation 1.1
The org.eclipse.equinox.registry also has J2SE
1.4 listed before Foundation 1.1. If I remember correctly, this is because we
do not have a bundle at pde-build time that provides the XML api to bundles
with BREE < J2SE 1.4. I think if you simply reorder the BREEs we will get a
build failure for bundles needing XML stuff to compile. We would need an XML
bundle to be available at build time also.
Tom
"Jeff McAffer" ---02/19/2008 07:57:02
AM---There are several projects in p2 currently that list J2SE 1.4 and
Foundation 1.1 in the BREE for the bundle. This is good but t

From:
|

"Jeff McAffer"
<jeff@xxxxxxxxx>
|

To:
|

"'Equinox development mailing list'"
<equinox-dev@xxxxxxxxxxx>
|

Date:
|

02/19/2008 07:57 AM
|

Subject:
|

[equinox-dev] [prov] use of Foundation 1.1
|
There are several projects in p2 currently that list J2SE 1.4 and Foundation
1.1 in the BREE for the bundle. This is good but they list them in that order.
The net result is that J2SE 1.4 is used to compile the code. What happens in
some cases people don’t have 1.4 so PDE uses the next best thing which ends up
being 1.5 or 1.6. In the end we get references to things we ought not. In
particular, I just had a setup in which there were no XML api in my workspace
or target yet everything was compiling ok. Took quite some time to figure out
how this could be so.
If everyone agrees, I will go through the projects and update them accordingly.
Jeff_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev