public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/15474] New: libgcj jar file should always be in classpath at runtime
Date: Sun, 16 May 2004 10:49:00 -0000	[thread overview]
Message-ID: <20040516104929.15474.green@redhat.com> (raw)

We should always put the libgcj jar file in the runtime's classpath.  This
should be OK, even if this file isn't installed.

This code...

public class showString
{
  public static void main (String args[]) throws Exception
  {
    Class c = showString.class;
    System.out.println (c.getResource( "/java/lang/String.class"));
  }
}
                                                                                
...should print something like...

jar:file:///home/green/install/jhbuild-inst/share/java/libgcj-3.5.0.jar!/java/lang/String.class

I propose we stick it on the path just after core:/

-- 
           Summary: libgcj jar file should always be in classpath at runtime
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: green at redhat dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15474


             reply	other threads:[~2004-05-16 10:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 10:49 green at redhat dot com [this message]
2004-05-16 11:29 ` [Bug java/15474] " pinskia at gcc dot gnu dot org
2004-05-16 12:06 ` mark at gcc dot gnu dot org
2004-08-25  9:20 ` pinskia at gcc dot gnu dot org
2004-08-25 12:58 ` mckinlay at redhat dot com
2004-08-25 16:17 ` green at redhat dot com
2004-08-25 17:47 ` mckinlay at redhat dot com
2004-08-25 17:52 ` mckinlay at redhat dot com
2004-08-25 18:01 ` green at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040516104929.15474.green@redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).