I love your optimism. Integration efforts I worked on for a large company always required to drop 1 run time environment per app. I promise we tried really really hard to make that one. This meant that when a loaded box went out the door there were as many as 8 java runtimes installed on your box.
Spare me the "but my app is totally 1337 and doesn't need that"; it simply doesn't apply to many scenarios. On Thu, Jul 17, 2008 at 06:07:05PM +0000, n0g0013 wrote: > On 17.07-10:13, Marco Peereboom wrote: > [ ... ] > > I am saying that each java app requires its own java runtime because the > > previous/next version is incompatible. Nothing new here. > > this is wrong. java versions are largely compatible and most requirements > are library problems, not runtime compatibility (although i believe > distribution rights to core components would often restrict packaging > for forward compatibility). > > -- > t > t > w
