The full log excerpt:

The full log excerpt:

Thanks for the taking the time to open a bugzilla!

Eric Rizzo wrote:

I actually think the problem in Peter's particular case is that the "Eclipse IDE for Java Developers" package specifies "-Dosgi.requiredJavaVersion=1.5" in its eclipse.ini
While I understand that Mylyn requires 1.5, I don't think anything else that is "crucial" to the Java dev tools does, so it seems to me that this is an unnnecessary restriction for that package (Mylyn is, IMO, still an optional piece of functionality that should not prevent the entire tool from loading).

I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=248976 about this.

Eric

If bug 174515 is all that happens when Eclipse tries to load in a JRE that's insufficient for its plugins, then it does seem like it might be worth making eclipse.ini less fussy - or telling users how to do themselves it in the documentation.

Anyway, here's my bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=249063

Thanks everyone for your help,
Peter

I actually think the problem in Peter's particular case is that the "Eclipse IDE for Java Developers" package specifies "-Dosgi.requiredJavaVersion=1.5" in its eclipse.ini
While I understand that Mylyn requires 1.5, I don't think anything else that is "crucial" to the Java dev tools does, so it seems to me that this is an unnnecessary restriction for that package (Mylyn is, IMO, still an optional piece of functionality that should not prevent the entire tool from loading).

I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=248976 about this.

Eric

https://bugs.eclipse.org/bugs/show_bug.cgi?id=249063

Thanks everyone for your help,
Peter

"Ed Merks"<Ed.Merks@xxxxxxxxx>  wrote in message
news:gbjb97$c93$1@xxxxxxxxxxxxxxxxxxxx

Peter,

That's a very good point.  It looks to me like Eclipse Classic is the only
download that doesn't require Java 5.0.  That makes the recommendation at
the top of the page awfully weak.  Please open a bugzilla asking to make
the statement more strongly.   In fact, there really ought to be a way to
find out the JRE level required for any particular package, and currently
it's guesswork; that's no good.   The other things ought to be fixed up as
well.  When you open a bugzilla, please append the bugzilla number to this
thread.

The issue is really kind of trickier than it seems on the surface.  See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=174515 for a related topic.

I do think that clearer documentation on the web site would help, and I
think we should simply be recommending that people use the newest JVM
version they can, and understand that if they're on a downlevel VM some
functionality may be missing.  The way I would put it is: "Most of the
Eclipse core is able to run on Java 1.4.2, but every version of Eclipse
contains some functionality that relies on Java 5 or even Java 6.  You may
not need this functionality, depending on what you're doing with Eclipse."

The problem is that describing exactly what functionality is and is not
available on a given VM quickly gets into way more detail than is
appropriate for a downloads page.  Someone planning on using Eclipse to edit
PHP scripts shouldn't have to read about the JSR199 API, for instance.

I really think it comes down to the question of how we show that some
functionality is unavailable, without intruding on the experience of people
who don't need that functionality.  Unfortunately, that is a very hard
challenge.

I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=248976 about this.

Eric

Building configured application...
Configuration files taken from <path>packagerConfiguration.
The application will be built in <path>.

Then it stops; no Packing installation site, Building, or Moving Files.

Now I get into "Building" when it dies:

Anyone know where I should start..
Steve

By the way, check out this blog entry about an online package builder:
<http://rapblog.innoopract.com/2008/09/new-eclipse-download-wizard-and-rap.html>

I may be becoming dangerous.  I stumbled on the the wiki page at
http://wiki.eclipse.org/EPP/How_to_build_a_package_locally and *thought*
that it described exactly what I want to do. I would like to create
something like "Eclipse IDE for Java Developers" or "Eclipse IDE for
C/C++ Developers" but with a custom selection of features. Then a new
user simply needs to unzip that custom package, just like you would with
the "standard" ones, and go. No updates, no fuss, no queues at my office.

Am I way off base, abusing a tool? If not, I have a problem. The build
finds all of the features, merrily installs them, then:

<SNIP>
Building configured application...
Configuration files taken from <path>\packagerConfiguration.
The application will be built in <path>.

Then it stops; no Packing installation site, Building, or Moving Files.

Thanks for everyone's help,
Steve

that's what I wanted to know!

Cheers,
Eugen