This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
[Bug java/15474] libgcj jar file should always be in classpath at runtime
- From: "green at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 25 Aug 2004 16:17:22 -0000
- Subject: [Bug java/15474] libgcj jar file should always be in classpath at runtime
- References: <20040516104929.15474.green@redhat.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From green at redhat dot com 2004-08-25 16:17 -------
(In reply to comment #4)
> There is no good reason why
> bytecode must be available at runtime.
I suppose -- but if it's installed, what's the harm?
> Unfortunately, if there are important applications that rely for some reason
on being able to do this,
> then we may not be able to avoid it. Anthony, what prompted this PR exactly?
The testsuite for a bytecode munging library required it. I believe it was a
dependency of Groovy.
> If we decide to do this, there is the issue of how to _find_ the right
libgcj.jar at runtime.
What's wrong with the sun.boot.class.path property we're already depending on in
Ant?
> That may be useful in other ways, such as automatically finding the right extdir.
We have the java.ext.dirs property.
AG
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15474