From: Jon Severinsson <jon@severinsson.net>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Re: problems compiling junit
Date: Thu, 13 Apr 2006 13:34:40 +0200 [thread overview]
Message-ID: <443E3750.4030400@severinsson.net> (raw)
In-Reply-To: <1144929960.26742.3.camel@localhost>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> I'm running java-1.5 as a *generation 2* system vm without any
>> problems. The only problem is if you at one point where using 1.5 as
>> a *generation 1* system vm (e.g. before you started using the
>> migration overlay).
>> You can safely do "java-config-2 -S sun-jdk-1.5", as long as
>> "java-config-1 -f" doesn't list a 1.5 jdk and
>> /etc/java-config-2/build/jdk.conf doesn't list a 1.5 jdk for 1.4.
>> (e.g. doesn't give a version if you use the *=sun-jdk syntax)
> Then, the migration document should state how to set the generation-2
> system vm. It only tells about java-config-2 -s ...
Perhaps it should. On the other hand you don't have to, it will be set
automatically during the vm update process (which is described).
java-config-2 -s is only mentioned because it differers from the plain
portage case.
>> Anyway I have two problems right now:
>> 1. If I do java-config-2 -S sun-jdk-1.4, ant-core continues to build
>> with sun-java-1.5
Because system vm has nothing to do with emerge. For that you set the
build jdk. Note that system vm can be a jre or a jdk, while compilation
jdk has to be a jdk. This procedure differs from a plain portage
installation, and should perhaps be mentioned somewhere.
>> 2. Junit does not compile even having compiled ant-core with 1.4 vm
>> (I had to modify jdk.conf)
The the default jdk.conf will not make 1.4 sources build with a 1.5 jdk,
so you do not *have* to modify jdk.conf. However, you *must not* changee
jdk.conf to an invalid state, which is currently possible (and you must
have done). Perhaps there should be a warning in the sample file?
(something like "# Warning: Do NOT set a 1.5 jdk for use with anything
but 1.5 sources!")
If Junit doesn't compile after having (re-)emerged all java-packages
with a corrected jdk.conf, file a bugreport. To find all packages you
have to re-emerge use java-1.5-fixer from the list.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEPjdQOOpxqcksWu4RAjjqAJ42uRyFXdqavyXNszJvqHOGiB8wTgCgnHsu
wqQylcrz1/tz8ArfaK9ovoM=
=bc0Z
-----END PGP SIGNATURE-----
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-13 11:32 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 [this message]
[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
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=443E3750.4030400@severinsson.net \
--to=jon@severinsson.net \
--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