|
|
| Re: Open source JDK project [message #42494 is a reply to message #42460] |
Tue, 14 November 2006 22:58   |
Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Alex Blewitt wrote:
> You can already ship an RCP with an embedded JRE, by placing the
> runtime in a subdirectory called 'jre'. It shouldn't be too hard to
> modify e.g. customTargets.xml to perform the copying for you if you
> wanted to, and had a suitable JRE to hand.
Eclipse supports it, but re-distributing a JRE is not just a matter of
shipping it with your product. IANAL, but the last time I looked into
re-distribution there were some hairy license terms that prohibited it.
That may have changed in the past couple of years, but I'd be surprised.
I think this thread was thinking of the possibility of Eclipse building
and shipping its own JVM implementation, instead of having to rely on
the (bloated) Sun implementation.
Interesting idea, but I'm not sure that falls within the charter of the
foundation.
Eric
|
|
|
| Re: Open source JDK project [message #42516 is a reply to message #42460] |
Tue, 14 November 2006 23:22 |
 Marco Maccaferri
Messages: 147
Registered: July 2009 |
Senior Member |
|
|
On 14/11/2006 23:14 Alex Blewitt ha scritto:
> You can already ship an RCP with an embedded JRE, by placing the
> runtime in a subdirectory called 'jre'. It shouldn't be too hard to
> modify e.g. customTargets.xml to perform the copying for you if you
> wanted to, and had a suitable JRE to hand.
Yes, I know that, however this has several problems. One is that the
JVMs are shipped as installable executable that must be run on the
target environment to have the files to package with the program, so you
need one win32 machine, one win64 (when available), one linux x86, one
linux x86_64, one Mac PPC, one Mac x86, one Solaris, etc. Another
problem is that the JVMs are not consistent across OSes so you are not
sure that the evironment is exactly what you expect.
I also believe that there are restrictions on the redistributable
license for the JVMs (at least Sun's JVMs). This maybe has changed with
the release of the source code, but you always have to deal with the OS
installations.
What I would like to see is a 'JVM pack' like the RCP delta pack that
can be used to automatically package the JVM compiled for the selected
target OSes, so that you can build the application from whatever OS you
are developing on and you are sure that the JVM is consistent to your
expectations because compiled from the same source.
Additionally maybe it is possible to remove all unnecessary code from
such VMs. For example an RCP application don't need the java plugin or
webstart systems, and I also believe that it would be possible to remove
Swing and AWT since we are using SWT (of course if you don't need the
SWT_AWT bridge). In other words, build a JVM that is specifically
optimized to be used with Eclipse and RCP applications.
Bye
|
|
|
| Re: Open source JDK project [message #42547 is a reply to message #42494] |
Wed, 15 November 2006 00:40 |
| Eclipse User |
|
|
|
Originally posted by: alex_blewitt.yahoo.com
I agree that it's not within the remit of the Eclipse foundation, but remember that 'distributing a JRE' is not the same as 'redistributing the Sun JRE'. There are JREs that you can use to run Eclipse at the moment, though perhaps not taking advantage of everything (and certainly not Java (TM) compatible).
However, the existence of a version of a JRE that you don't have license to redistribute does not preclude there being any JRE that you can redistribute.
Alex.
|
|
|
| Re: Open source JDK project [message #42608 is a reply to message #42516] |
Wed, 15 November 2006 02:52 |
| Eclipse User |
|
|
|
Originally posted by: jeff_mcaffer.REMOVE.ca.ibm.com
Sounds like a fine community opportunity...
Jeff
Marco Maccaferri wrote:
>
> On 14/11/2006 23:14 Alex Blewitt ha scritto:
>
>> You can already ship an RCP with an embedded JRE, by placing the
> > runtime in a subdirectory called 'jre'. It shouldn't be too hard to
> > modify e.g. customTargets.xml to perform the copying for you if you
> > wanted to, and had a suitable JRE to hand.
>
> Yes, I know that, however this has several problems. One is that the
> JVMs are shipped as installable executable that must be run on the
> target environment to have the files to package with the program, so you
> need one win32 machine, one win64 (when available), one linux x86, one
> linux x86_64, one Mac PPC, one Mac x86, one Solaris, etc. Another
> problem is that the JVMs are not consistent across OSes so you are not
> sure that the evironment is exactly what you expect.
>
> I also believe that there are restrictions on the redistributable
> license for the JVMs (at least Sun's JVMs). This maybe has changed with
> the release of the source code, but you always have to deal with the OS
> installations.
>
> What I would like to see is a 'JVM pack' like the RCP delta pack that
> can be used to automatically package the JVM compiled for the selected
> target OSes, so that you can build the application from whatever OS you
> are developing on and you are sure that the JVM is consistent to your
> expectations because compiled from the same source.
>
> Additionally maybe it is possible to remove all unnecessary code from
> such VMs. For example an RCP application don't need the java plugin or
> webstart systems, and I also believe that it would be possible to remove
> Swing and AWT since we are using SWT (of course if you don't need the
> SWT_AWT bridge). In other words, build a JVM that is specifically
> optimized to be used with Eclipse and RCP applications.
>
> Bye
|
|
|
Powered by
FUDForum. Page generated in 0.02502 seconds
] 
Search
Help
Register
Login
Home
