From: mbutcher <mbutcher@aleph-null.tv>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Java ebuild problems
Date: Wed, 3 Apr 2002 13:26:43 -0700 [thread overview]
Message-ID: <20020403180205.7A9F917248@www.aleph-null.tv> (raw)
In-Reply-To: <3CAB0E79.9020304@ksu.edu>
I ran into that exact problem a week ago (though I am using j2sdk 1.4.1). It
stemmed from the absence of ant.jar in $ANT_HOME (/usr/share/ant). I searched
the entire filesystem for ant.jar and couldn't find it.
I ran the ebuild again, figuring that it might have given an unnoticed error
the first time, and it rebuilt correctly, placing ant.jar in /usr/share/ant
I figured I had done something wriong, and didn't think to file a bug, but if
you are seeing the same thing too... perhaps it should be filed.
Let me know the outcome.
Matt
On Wednesday 03 April 2002 07:15 am, Matthew Baxa wrote:
> While trying to work on a EJB project in Gentoo, I needed to emerge the
> Java stuff. The sun-j2ee.ebuild needed to be modified to take the
> correct version available (j2sdkee-1_3_1-linux.tar.gz instead of the old
> j2sdkee-1_3_01-linux.tar.gz) as well as "S=${WORKDIR}/j2sdkee1.3.1"
>
> But my problem lies with Ant. After emerging ant (and sun-jdk) when I
> try to run ant I get:
> bash-2.05a$ ant
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/tools/ant/Main
>
> Any ideas on how to fix?
>
> ---------------------
> Matthew Baxa
> http://www.cis.ksu.edu/~mbb1810/
> Student Systems Administrator
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2002-04-03 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 14:15 [gentoo-dev] Java ebuild problems Matthew Baxa
2002-04-03 20:26 ` mbutcher [this message]
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=20020403180205.7A9F917248@www.aleph-null.tv \
--to=mbutcher@aleph-null.tv \
--cc=gentoo-dev@gentoo.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