From: Serkan Kaba <serkan@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] XOM ebuild
Date: Sun, 20 Feb 2011 07:48:03 +0200 [thread overview]
Message-ID: <4D60AB13.7010300@gentoo.org> (raw)
In-Reply-To: <201102201452.12237.ali_bush@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 20-02-2011 03:52, Alistair Bush wrote:
>> Ken (mostly) and I gave a shot at bug 146593 bumping XOM in tree. After
>> a few iterations we have hit the issue that has been discovered in the
>> past, circular dependency on Jaxen. I'm asking if splitting xom to
>> xom-core and xom-jaxen is OK, as don in jdom.
>
> Yes. Please also file a bug with upstream.
>
>
Upstream does more weird stuff checking out jaxen sources from scm
during xom build.
- --
Sincerely,
Serkan KABA
Gentoo Developer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1gqxMACgkQRh6X64ivZaI1FACfRqeqK8wSPa2LeqfVsgef2L/0
ATEAn1sk7B/xH7wAZWJk9vgjdFBwQTdg
=uBZ+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-20 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 22:59 [gentoo-java] XOM ebuild Serkan Kaba
2011-02-20 1:52 ` Alistair Bush
2011-02-20 5:48 ` Serkan Kaba [this message]
2011-02-20 7:03 ` Alistair Bush
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=4D60AB13.7010300@gentoo.org \
--to=serkan@gentoo.org \
--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