buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Assaf Arkin" <ar...@intalio.com>
Subject Git experiment
Date Mon, 12 May 2008 22:37:00 GMT
I'm running a little Git experiment to get a better feeling for working with
it, so I picked a small patch to get started with.
BUILDR-4 was opened to deal with the versioning problem of extensions, in
this particular case, XML Beans.  Buildr hardcodes one version, but you
might want to use a different one in your project without patching Buildr,
or waiting for the next release to happen.  It's an old one, but we didn't
have a ready solution back then.

1.3 gives us three ways for solving this.  There's artifact namespaces
(thanks, Victor), passing version to compile_xml_beans (as suggested by
Tammo) and using build.yaml.

I added two patches, one for passing version number, the other for using
build.yaml [1] to add the two other options.  (You'll need to apply both
since they depend on each other).  I must add this code is untested, mostly
for getting a feeling for whether or not it's something we'd like to see for
XML Beans and other extensions.

Now for the Git part.  You can also check out a patched copy of Buildr to
test on your own build [2].  If you're starting from scratch you can clone
the repository and checkout the BUILDR-4 branch:

git clone git://github.com/Assaf/buildr.git
git fetch origin BUILDR-4:BUILDR-4
git checkout BUILDR-4

If you already have a local repository for Buildr, no need to create another
one, just checkout this branch from there:

git remote add assaf git://github.com/Assaf/buildr.git
git fetch assaf BUILDR-4:BUILDR-4
git checkout BUILDR-4

After which, rake install as usual.

Let's see how easy/painful this is.

Assaf

[1]
https://issues.apache.org/jira/browse/BUILDR-4?focusedCommentId=12596211#action_12596211
[2] http://github.com/Assaf/buildr/commits/BUILDR-4

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message