[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [jdt-dev] Problems on MacOSx

Is that a regression since 3.4?
 

> -----Original Message-----
> From: jdt-dev-bounces@xxxxxxxxxxx 
> [mailto:jdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Hallgren
> Sent: Thursday, February 19, 2009 8:56 AM
> To: Eclipse JDT general developers list.
> Cc: Oisin Hurley; Henrik Lindberg
> Subject: Re: [jdt-dev] Problems on MacOSx
> 
> Hi,
> As it turns out, our headless configuration did not include 
> the org.eclipse.jdt.launching.macosx bundle. But when we 
> attempted to include it, we discovered a problem that is a 
> blocker for us. This fragment introduces new dependencies to 
> org.eclipse.ui and org.eclipse.jdt.ui. This effectively 
> impedes all headless builds on MacOS X unless a major part of 
> the IDE is included in the tool.
> 
> Any chance that this can be revised so that this fragment is 
> split in two in Eclipse 3.5? The fragment has two packages, 
> one of them apparently has no dependencies to the UI and I 
> have a strong feeling that's the part that is needed to do the build.
> 
> Regards,
> Thomas Hallgren
> 
> 
> Darin Wright wrote:
> > It sounds like your installation may be missing the 
> > "org.eclipse.jdt.launching.macosx" bundle. This message 
> indicates that 
> > installed JREs were being restored, but the VM type extension 
> > associated with the JREs was not present. This bundle 
> contains the VM 
> > type extension for Mac JREs.
> >
> > Darin Wright
> >
> >
> >
> >
> > Thomas Hallgren <thomas@xxxxxxx>
> > Sent by: jdt-dev-bounces@xxxxxxxxxxx
> > 02/18/2009 07:29 AM
> > Please respond to
> > "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
> >
> >
> > To
> > jdt-dev@xxxxxxxxxxx
> > cc
> > Oisin Hurley <ohurley@xxxxxxxx>, Henrik Lindberg 
> > <henrik.lindberg@xxxxxxxxxxxxxx> Subject [jdt-dev] Problems 
> on MacOSx
> >
> >
> >
> >
> >
> >
> > A user of Buckminster has problems with headless builds on MacOS X. 
> > The Eclipse builder encounters a problem and prints the message:
> >
> > The project was not built since its build path is 
> incomplete. Cannot 
> > find the class file for java.lang.Object.
> >
> >
> > After an unsuccessful build, these lines can be found in the log:
> >
> >      [java] INFO:  Installed JRE 'JVM 1.4' removed due to 
> missing VM 
> > type extension.
> >      [java] INFO:  Installed JRE 'JVM 1.4.1' removed due to 
> missing VM 
> > type extension.
> >      [java] INFO:  Installed JRE 'JVM 1.4.2' removed due to 
> missing VM 
> > type extension.
> >      [java] INFO:  Installed JRE 'JVM 1.5' removed due to 
> missing VM 
> > type extension.
> >      [java] INFO:  Installed JRE 'JVM 1.5.0 (MacOS X 
> Default)' removed 
> > due to missing VM type extension.
> >
> > I would like some help interpreting what this means. I 
> think the last 
> > log line is relevant since the build is intended to use the 
> default JVM.
> > What component is it that causes the problem? Is it the JVM 
> that lacks 
> > something? Who is supposed to declare the missing VM type extension?
> >
> > The Buckminster bugzilla for this problem can be found here: 
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=258587. Any 
> insight that 
> > might be helpful is greatly appreciated.
> >
> > Regards,
> > Thomas Hallgren
> > _______________________________________________
> > jdt-dev mailing list
> > jdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/jdt-dev
> >
> >
> > _______________________________________________
> > jdt-dev mailing list
> > jdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/jdt-dev
> >   
> _______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jdt-dev
>