I've released AtomBeat 0.2-alpha-7 which fixes a bug found in 0.2-alpha-6
relating to use of the new plugin-util module. For more information see:
http://code.google.com/p/atombeat/wiki/ReleaseNotes#0.2-alpha-7
For information on downloading and using AtomBeat, see:
http://code.google.com/p/atombeat/wiki/AtomBeat#Downloads
Cheers,
Alistair
--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health <http://cggh.org>
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Web: http://purl.org/net/aliman
Email: alim...@gmail.com
Tel: +44 (0)1865 287669
I have tweaked the Jenkins config again, hope it will go end-to-end
without manual intervention next time.
The 0.2-alpha-7 all deployed nicely to the Maven repository, but the
0.2-alpha-8-SNAPSHOT only triggered for
the parent and the utility projects.
I am not sure if this was my oversight or if the configuration mutates!
I have also added a periodic build to all projects (monthly), to catch
any rust, and reinstated IRC notification.
cheers
Tim
--
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org
http://jenkins.cggh.org/view/AtomBeat/job/atombeat-parent/135/
seems to suggest that the maven release/prepare plugin is being a bit quick:
both the release and the prepare are being caught up in a single build.
I could be wrong, have not looked into it.
cheers
Tim
On 1 March 2011 12:10, aliman wrote:
> Thanks Tim. I didn't see your message before doing another release
> this morning, but will check it next time.
>
> Cheers,
>
> Alistair
>
--
Tim Pizey - http://pizey.net/~timp