From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: ceph-devel@vger.kernel.org
Cc: James Page <james.page@canonical.com>,
Noah Watkins <jayhawk@cs.ucsc.edu>,
Gary Lowell <gary.lowell@inktank.com>,
Sage Weil <sage@inktank.com>
Subject: Re: [PATCH] configure.ac: check for org.junit.rules.ExternalResource
Date: Tue, 15 Jan 2013 10:32:08 +0100 [thread overview]
Message-ID: <50F52218.9020106@bisect.de> (raw)
In-Reply-To: <50F51B9F.8020504@canonical.com>
Am 15.01.2013 10:04, schrieb James Page:
> On 12/01/13 16:36, Noah Watkins wrote:
>> On Thu, Jan 10, 2013 at 9:13 PM, Gary Lowell
>> <gary.lowell@inktank.com> wrote:
>>>>
>>>> Thanks Danny. Installing sharutils solved that minor issue.
>>>> We now get though the build just fine on opensuse 12, but sles
>>>> 11sp2 gives more warnings (pasted below). Should we be using a
>>>> newer version of autoconf on sles? I've tried moving
>>>> AC_CANONICAL_TARGET earlier in the file, but that causes some
>>>> other issues with the new java macros.
>> We could also move away from using autoconf/automake for Java, and
>> use a packaging/dependency system designed for Java, like Maven.
>
> If this route it taken please bear in mind that use of Maven will
> create some challenges in Ubuntu; specifically with regards to the
> fact that ceph is in main and supported by Canonical and Maven +
> associated toolchain is *huge* in terms of packages and is not in main.
>
> Ant however is in main and fully supported.
I would also prefer to not add another huge build dependency to ceph,
especially since it's e.g. not supported by SLES11 and since ceph
currently builds fine (even with these small warnings from autotools).
Danny
next prev parent reply other threads:[~2013-01-15 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 21:35 [PATCH] configure.ac: check for org.junit.rules.ExternalResource Danny Al-Gaaf
2013-01-09 21:35 ` Danny Al-Gaaf
2013-01-09 21:54 ` Noah Watkins
2013-01-10 4:32 ` Gary Lowell
2013-01-10 7:55 ` Danny Al-Gaaf
2013-01-11 5:13 ` Gary Lowell
2013-01-12 16:36 ` Noah Watkins
2013-01-15 9:04 ` James Page
2013-01-15 9:32 ` Danny Al-Gaaf [this message]
2013-01-15 14:55 ` Noah Watkins
2013-01-15 17:36 ` Gregory Farnum
2013-01-12 21:59 ` Danny Al-Gaaf
2013-01-14 20:41 ` Gary Lowell
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=50F52218.9020106@bisect.de \
--to=danny.al-gaaf@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=gary.lowell@inktank.com \
--cc=james.page@canonical.com \
--cc=jayhawk@cs.ucsc.edu \
--cc=sage@inktank.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.