Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Ean Schuessler
I still don't understand what this achieves that alternatives do not. There is nothing particularly special about Java that requires a more elaborate alternatives mechanism than any other interpreter. If the wrapper script for each VM does its job properly then the classpath should get set to what

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Ean Schuessler
I still don't understand what this achieves that alternatives do not. There is nothing particularly special about Java that requires a more elaborate alternatives mechanism than any other interpreter. If the wrapper script for each VM does its job properly then the classpath should get set to what

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Jan Schulz
Hello Ean, Tuesday, October 7, 2003, 9:38:20 PM, you wrote: > I still don't like the findjava idea. What is the goal? The goal is to provide a search mechnism for the alternatives. The discussion in debian-java has shown, that the alternative machnism isn't enough and especial isn't reliable. fi

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Jan Schulz
Hello T., Tuesday, October 7, 2003, 10:41:52 PM, you wrote: > 1) Standardize the invocation interface, so that it is feasible to have >java packages that will have a hope of running on a VM that the >packager did not directly support. The discussion has shown, that we can't standardisize

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Jan Schulz
Hello Ean, Tuesday, October 7, 2003, 9:38:20 PM, you wrote: > I still don't like the findjava idea. What is the goal? The goal is to provide a search mechnism for the alternatives. The discussion in debian-java has shown, that the alternative machnism isn't enough and especial isn't reliable. fi

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Jan Schulz
Hello T., Tuesday, October 7, 2003, 10:41:52 PM, you wrote: > 1) Standardize the invocation interface, so that it is feasible to have >java packages that will have a hope of running on a VM that the >packager did not directly support. The discussion has shown, that we can't standardisize

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread T. Alexander Popiel
In message: <[EMAIL PROTECTED]> Ean Schuessler <[EMAIL PROTECTED]> writes: >I still don't like the findjava idea. What is the goal? It looks like >this script provides a common interface to all of the java execution >systems (compilers, JITs, interpreters or otherwise) by concentrati

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Ean Schuessler
I still don't like the findjava idea. What is the goal? It looks like this script provides a common interface to all of the java execution systems (compilers, JITs, interpreters or otherwise) by concentrating shell script adapters into a single file. I think it is much more maintainable to define t

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread T. Alexander Popiel
In message: <[EMAIL PROTECTED]> Ean Schuessler <[EMAIL PROTECTED]> writes: >I still don't like the findjava idea. What is the goal? It looks like >this script provides a common interface to all of the java execution >systems (compilers, JITs, interpreters or otherwise) by concentrati

Bug#212863: java-common: New java policy including tools to manage the changes

2003-10-07 Thread Ean Schuessler
I still don't like the findjava idea. What is the goal? It looks like this script provides a common interface to all of the java execution systems (compilers, JITs, interpreters or otherwise) by concentrating shell script adapters into a single file. I think it is much more maintainable to define t

Re: Installing a Java VM on Debian

2003-10-07 Thread Jan Schulz
Hello Ben, Sunday, October 5, 2003, 3:50:30 PM, you wrote: > and broken - they're still using gcc2 builds, which can (in my experience) > cause apps using C++ native libraries to crash randomly and frequently. Not only that, a wrong java plugin will stop mozilla from working. What a shit! Jan --

Re: Fw: RFS: libxt-java (0.20020426a-1) -- An implementation in Java of XSL Transformations

2003-10-07 Thread Jaldhar H. Vyas
On Sun, 5 Oct 2003, Arnaud Vandyck wrote: > Hi all, > > I'm still looking for a sponsor for libxt-java. I did found one but > forgot who (sorry), but he doesnt like to upload a package I'm not yet > the maintainer. I can send a signed mail of Ola ([EMAIL PROTECTED]) who > says he > has n

Re: Installing a Java VM on Debian

2003-10-07 Thread Jan Schulz
Hello Ben, Sunday, October 5, 2003, 3:50:30 PM, you wrote: > and broken - they're still using gcc2 builds, which can (in my experience) > cause apps using C++ native libraries to crash randomly and frequently. Not only that, a wrong java plugin will stop mozilla from working. What a shit! Jan --

Re: Fw: RFS: libxt-java (0.20020426a-1) -- An implementation in Java of XSL Transformations

2003-10-07 Thread Jaldhar H. Vyas
On Sun, 5 Oct 2003, Arnaud Vandyck wrote: > Hi all, > > I'm still looking for a sponsor for libxt-java. I did found one but > forgot who (sorry), but he doesnt like to upload a package I'm not yet > the maintainer. I can send a signed mail of Ola ([EMAIL PROTECTED]) who says he > has not