Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Subject: Re: Why use buildr?
From: Martin Grotzke <martin.grotzke@javakaffee.de>
To: users@buildr.apache.org
In-Reply-To: <4D2C7235-B481-440C-97F9-4A90EC115032@gmail.com>
References: <1234826346.4077.104.camel@localhost.localdomain.tld>
	 <5c99d0330902161632j4ab82541lcf0c8b50bf1ff5d6@mail.gmail.com>
	 <1234859954.4056.5.camel@localhost.localdomain.tld>
	 <4D2C7235-B481-440C-97F9-4A90EC115032@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1";
 protocol="application/pgp-signature"; boundary="=-8fTAQywKdPsaOFr8oCku"
Date: Wed, 18 Feb 2009 09:08:38 +0100
Message-Id: <1234944518.4108.1.camel@localhost.localdomain.tld>
Mime-Version: 1.0

--=-8fTAQywKdPsaOFr8oCku
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2009-02-17 at 08:48 -0600, Daniel Spiewak wrote:
> No, quite the opposite.  Buildr has fantastic auto-magical support for =20
> the major test frameworks.  This is especially evident where Scala is =20
> concerned.  Specs and ScalaCheck (my tools of choice) "just work".
Cool, great to hear that! :)

Scala's still on my list of the lets-use-this-in-the-next-project,
however, there are some issues with it (e.g. refactoring support in
eclipse IDE plugin) that probably prevent us from choosing it. but
that's another story :)

Thanx && cheers,
Martin

>=20
> Daniel
>=20
> On Feb 17, 2009, at 2:39 AM, Martin Grotzke <martin.grotzke@javakaffee.de=
=20
>  > wrote:
>=20
> > On Mon, 2009-02-16 at 18:32 -0600, Daniel Spiewak wrote:
> >> I would strongly emphasize the "scripting language not XML" point, =20
> >> since
> >> this is (I think) Buildr's killer feature.  Having written a lot of =20
> >> scripty
> >> Ant in my day, it is incomparably easier to do the same thing in =20
> >> Buildr.
> >>
> >> Another point that might be worth mentioning is Buildr's Scala =20
> >> support,
> >> which is second to none in my opinion.  Maven does support Scala =20
> >> with a
> >> plugin (as does Ant), but support for test frameworks and the like is
> >> lacking IIRC.
> > Are you saying that the support of buildr for test frameworks is
> > lacking?
> >
> > Cheers,
> > Martin
> >
> >
> >>
> >> Daniel
> >>
> >> On Mon, Feb 16, 2009 at 5:19 PM, Martin Grotzke <
> >> martin.grotzke@javakaffee.de> wrote:
> >>
> >>> Hi,
> >>>
> >>> in our next project I'd like to use buildr for build management.
> >>> Now I only have to convince my colleagues, why we should use =20
> >>> buildr and
> >>> not maven or ant+ivy.
> >>>
> >>> I'd say it has the best of both worlds:
> >>> - standard build process (like maven)
> >>> - conventions for project/directory structure (like maven)
> >>> - dependency mgmt using maven repos
> >>> - and though it provides the flexibility as ant does
> >>> - all ant tasks can be used in buildr
> >>>
> >>> It has some advanteges over maven and ant:
> >>> - buildr is even easier and more flexible as ant since you don't =20
> >>> have to
> >>> work with xml to do e.g. an if/then/else - just use ruby (no need to
> >>> create tasks/mojos)
> >>> - build profiles supporting inheritence (and usage of profile
> >>> variables/properties)
> >>> - much more compact than maven and ant
> >>> - great multi-module / multi-project support: if you have project =20
> >>> A and
> >>> B, where B depends on A, then you can just build B, which
> >>> automatically triggers a build of A if necessary
> >>> - fast (I only compared it to maven)
> >>>
> >>> To be fair to my colleagues I'd also like to mention the drawback =20
> >>> I see:
> >>> - relatively new, so there might be some issues we run into
> >>> - not so many examples / documentation available (as it's new),
> >>> however, this is compensated by this great mailing list :)
> >>> - not so many built-in reporting-plugins available as they are =20
> >>> available
> >>> for maven
> >>>
> >>> Would you add/remove/change some item of this list?
> >>>
> >>> Thx && cheers,
> >>> Martin
> >>>
> >>>
> >>>
>=20

--=-8fTAQywKdPsaOFr8oCku
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkmbwgIACgkQ7FvOl7Te+pYsSwCeOkkBTk9JjBShCLd0WT3piBU4
AC4AnRja6NX5MteKIoIbxuUnOmu0ylL8
=kPu5
-----END PGP SIGNATURE-----

--=-8fTAQywKdPsaOFr8oCku--