From: Henrique Ferreiro <henrique.ferreiro@gmail.com>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Re: problems compiling junit
Date: Fri, 14 Apr 2006 17:24:06 +0200 [thread overview]
Message-ID: <1145028246.26742.25.camel@localhost> (raw)
In-Reply-To: <443EFB00.3080309@gentoo.org>
Thank you very much. I unmerged and merged junit successfully.
I am using java-1.5-fixer from migration overlay. It seems that it does
not unmerge the offending packages first. When are you going to do
another release?
O Xov, 13-04-2006 ás 20:29 -0500, Joshua Nichols escribiu:
> Henrique Ferreiro wrote:
> >>>> I did not modify jdk.conf. Every line is commented.
> >> Then ant-core, as well as junit, should be build with 1.4. Is that the case?
> > No. ant-core is being built with jdk-1.5. Anyway junit does not compile using
> > 1.4 with ant-core.
> >
> >
>
>
> Alright... I'm pretty sure what the problem is. If you take a look at
> /usr/bin/ant... at some point, it pulls in a bunch of jars from several
> packages. This is necessary to make sure that all the ant tasks work
> properly. One of these happens to be junit....
>
>
> So what I believe is happening... you have junit installed (and built
> with 1.5), then go to rebuild with 1.4. The ebuild calls ant, which
> pulls in junit compiled with 1.5 onto the classpath. When javac tries to
> resolve junit classes... it's getting them from the 1.5-built junit,
> instead of the junit which is being built. So, the workaround would be
> to unmerge junit before trying to rebuidl it with 1.4.
>
> Essentially, this problem comes down to who we handle /usr/bin/ant, and
> how it pulls in all its dependencies. It is currently hardcoded to bring
> in certain packages, which is less than ideal, because we need to have
> fine-grain control over the classpath. In particular, when building
> packages, we don't want to include the already-compiled version that is
> living on the system.
>
> Aside from this, I recommend you try the java-1.5-fixer I posted in a
> different thread. It actually goes through all of ant's dependencies,
> and if any were built with 1.5, will unmerge them, and merge them again.
>
> Hope this helps,
>
> Josh
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-14 14:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 12:09 [gentoo-java] problems compiling junit Henrique Ferreiro
2006-04-12 11:36 ` [gentoo-java] " Wiktor Wandachowicz
2006-04-12 12:53 ` Henrique Ferreiro
2006-04-12 12:21 ` Wiktor Wandachowicz
2006-04-13 0:58 ` Henrique Ferreiro
2006-04-13 4:38 ` Joshua Nichols
2006-04-13 6:03 ` Jon Severinsson
2006-04-13 12:06 ` Henrique Ferreiro
2006-04-13 11:34 ` Jon Severinsson
[not found] ` <1144932831.26742.8.camel@localhost>
2006-04-13 12:05 ` Jon Severinsson
2006-04-13 14:07 ` Henrique Ferreiro
2006-04-13 14:09 ` Henrique Ferreiro
2006-04-14 1:29 ` Joshua Nichols
2006-04-14 15:24 ` Henrique Ferreiro [this message]
2006-04-14 14:47 ` Joshua Nichols
2006-04-14 21:19 ` Wiktor Wandachowicz
2006-04-12 11:51 ` Wiktor Wandachowicz
2006-04-12 13:25 ` Joshua Nichols
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=1145028246.26742.25.camel@localhost \
--to=henrique.ferreiro@gmail.com \
--cc=gentoo-java@lists.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