| Incorrect JRE system libraries list [message #135671] |
Mon, 19 January 2004 12:42  |
Eclipse User |
|
|
|
Originally posted by: mpjohn.us.ibm.com
I've encountered a problem trying to change my Eclipse platform to use a 1.4
JRE versus the 1.3 JRE. My team has been using Eclipse with JRE 1.3 for
some time to develop an Eclipse feature. The feature is currently being
beta-tested. For various reasons, we would like to swap out the JRE we're
using to launch Eclipse and use a 1.4 JRE versus the 1.3. This plan would
allow both our plugins and the end users' (by virtue of the default JRE) to
take advantage of 1.4 functionality. But we ran into a problem.
The problem is that if you have a workspace that was created previously with
JRE1.3 as the default JRE and then you launch Eclipse with JRE1.4, the list
of JRE system libraries for the default JRE does not get updated correctly.
The list contains all of the JARs in jre/lib/ext, but none of the jre/lib
JARs -- most notably, jre/lib/core.jar is not included, so you get the
following compile failure:
This compilation unit indirectly references the missing type
java.lang.Object (typically some required class file is referencing a type
outside the classpath)
If you add the JRE definition manually from the "Installed Java Runtime
Environments" preference page, the correct list of libraries is generated.
However, we would prefer not to have our end users go through this extra
step if we end up going this route in our next release.
Is this a bug or am I missing something?
Thanks.
Maynard
|
|
|
| Re: Incorrect JRE system libraries list [message #135870 is a reply to message #135671] |
Tue, 20 January 2004 09:17  |
| Eclipse User |
|
|
|
Chaning the JRE that you run Eclipse with will not change the Installed JREs
in the workspace preferences. The preferences are simply initialized with
the JRE that Eclipse runs with, the first time a JRE is required, for
convenience.
Darin
"Maynard Johnson" <mpjohn@us.ibm.com> wrote in message
news:buh58f$76a$1@eclipse.org...
> I've encountered a problem trying to change my Eclipse platform to use a
1.4
> JRE versus the 1.3 JRE. My team has been using Eclipse with JRE 1.3 for
> some time to develop an Eclipse feature. The feature is currently being
> beta-tested. For various reasons, we would like to swap out the JRE we're
> using to launch Eclipse and use a 1.4 JRE versus the 1.3. This plan would
> allow both our plugins and the end users' (by virtue of the default JRE)
to
> take advantage of 1.4 functionality. But we ran into a problem.
>
> The problem is that if you have a workspace that was created previously
with
> JRE1.3 as the default JRE and then you launch Eclipse with JRE1.4, the
list
> of JRE system libraries for the default JRE does not get updated
correctly.
> The list contains all of the JARs in jre/lib/ext, but none of the jre/lib
> JARs -- most notably, jre/lib/core.jar is not included, so you get the
> following compile failure:
> This compilation unit indirectly references the missing type
> java.lang.Object (typically some required class file is referencing a type
> outside the classpath)
>
> If you add the JRE definition manually from the "Installed Java Runtime
> Environments" preference page, the correct list of libraries is generated.
> However, we would prefer not to have our end users go through this extra
> step if we end up going this route in our next release.
>
> Is this a bug or am I missing something?
>
> Thanks.
> Maynard
>
>
|
|
|
| Re: Incorrect JRE system libraries list [message #135883 is a reply to message #135870] |
Tue, 20 January 2004 11:09 |
| Eclipse User |
|
|
|
Originally posted by: mpjohn.us.ibm.com
Darin,
Bear with me as I rephrase the issue with more specifics.
We use WebSphere Studio Workbench as our Eclipse platform. The WSWB build
we get comes with a 1.3.1 JRE laid down in the eclipse/jre folder. When a
user initially launches our WSWB-based product with the standard 1.3.1, by
default, a JRE definition is added to the list of installed JREs with a
location of <installDir>/eclipse. Since initially this is the only JRE
definition, it is automatically selected as the "default" JRE. Our typical
user simply uses that default JRE.
As I mentioned earlier, we see some benefit (both for us and for our users)
to moving to the 1.4 JRE in the future. So an upgrade of our product (which
includes an embedded WSWB) would replace the 1.3.1 JRE under
<installDir>/eclipse/jre with a 1.4.1 JRE. But in testing out such an
upgrade scenario, we've found that the existing default JRE definition in
the workspace preferences gets only partially updated, as described in my
earlier post.
So, are you saying the initialization of the "default" JRE workspace
preference is something you can count on being done properly only when a
workspace is first being created/initialized?
Thanks in advance for your reply.
-Maynard
"Darin Wright" <Darin_Wright@ca.ibm.com> wrote in message
news:bujd70$n6c$1@eclipse.org...
> Chaning the JRE that you run Eclipse with will not change the Installed
JREs
> in the workspace preferences. The preferences are simply initialized with
> the JRE that Eclipse runs with, the first time a JRE is required, for
> convenience.
>
> Darin
>
> "Maynard Johnson" <mpjohn@us.ibm.com> wrote in message
> news:buh58f$76a$1@eclipse.org...
> > I've encountered a problem trying to change my Eclipse platform to use a
> 1.4
> > JRE versus the 1.3 JRE. My team has been using Eclipse with JRE 1.3 for
> > some time to develop an Eclipse feature. The feature is currently being
> > beta-tested. For various reasons, we would like to swap out the JRE
we're
> > using to launch Eclipse and use a 1.4 JRE versus the 1.3. This plan
would
> > allow both our plugins and the end users' (by virtue of the default JRE)
> to
> > take advantage of 1.4 functionality. But we ran into a problem.
> >
> > The problem is that if you have a workspace that was created previously
> with
> > JRE1.3 as the default JRE and then you launch Eclipse with JRE1.4, the
> list
> > of JRE system libraries for the default JRE does not get updated
> correctly.
> > The list contains all of the JARs in jre/lib/ext, but none of the
jre/lib
> > JARs -- most notably, jre/lib/core.jar is not included, so you get the
> > following compile failure:
> > This compilation unit indirectly references the missing type
> > java.lang.Object (typically some required class file is referencing a
type
> > outside the classpath)
> >
> > If you add the JRE definition manually from the "Installed Java Runtime
> > Environments" preference page, the correct list of libraries is
generated.
> > However, we would prefer not to have our end users go through this extra
> > step if we end up going this route in our next release.
> >
> > Is this a bug or am I missing something?
> >
> > Thanks.
> > Maynard
> >
> >
>
>
|
|
|
|
| Re: Incorrect JRE system libraries list [message #136587 is a reply to message #136075] |
Thu, 22 January 2004 16:36 |
| Eclipse User |
|
|
|
Originally posted by: mpjohn.us.ibm.com
Ok, I think I get it now. You don't want to reinitialize the "default JRE"
info since it's possible the user may have intentionally imported
preferences they would not want over-written.
Thanks.
Maynard
"Darin Wright" <Darin_Wright@ca.ibm.com> wrote in message
news:bum6s9$1m2$1@eclipse.org...
> > So, are you saying the initialization of the "default" JRE workspace
> > preference is something you can count on being done properly only when a
> > workspace is first being created/initialized?
>
> Yes.
>
> Also note, that over-writing an existing JRE install with a new JRE (i.e.
> same location in the file system) will not update the JRE definitions in
the
> workspace. The Java debugger ensures that JREs in the user preferencess
> still exist (when referenced), however, we do not look for JREs being
> changed underneath us.
>
> See related bug report:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=31586
>
> Darin
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04328 seconds
Home