Hi,
On Tue, May 31, 2011 at 10:40 PM, Tom Hobbs <tvho...@googlemail.com> wrote:
> The artifacts can be found here;
>
> http://people.apache.org/~thobbs/river/
>
> Hopefully I've done it all right, if not then please let me know and I
> can get it fixed.
-1 The release package doesn't build:
$ tar zxf apache-river-2.2-src.tar.gz
$ cd apache-river-2.2
$ ant
[...]
BUILD FAILED
.../apache-river-2.2/build.xml:513: .../apache-river-2.2/asm not found.
Instead of using a script to build the release package, I'd rather
just package up an svn export of the release tag:
$ svn export http://svn.apache.org/repos/asf/river/jtsk/tags/x.y.z
apache-river-x.y.z
$ tar zcf apache-river-x.y.z.tar.gz apache-river-x.y.z
This way you'd never have unexpected build problems like the one shown above.
On a related note, there's no tag for this release. It would be good
if all releases were properly tagged.
BR,
Jukka Zitting
