Updates to Athena since Feb 2010
Ease of use
- build.xml is now simpler. Sample project template updated. You can now use the same build.xml script to run a build in Eclipse or in Hudson from an Ant-based job. Note that the page Build In Hudson/Ant Script is no longer current. See also bug 304800.
- You can now run
buildExtra.xml#extraPackagingviabuild.steps=buildExtrarather than requiringbuild.steps=buildZips.
- Publishing support will improve thanks to bug 306854... anyone want to contribute to writing a Hudson job, please feel free!
Packaging Support
- bug 306300 Athena removes .jar files and only contains pack 200 files in update site - new default setting (keep both artifact types) is
removeUnpackedJars=false, but can revert to old behaviour (and smaller update site) withremoveUnpackedJars=true
- bug 307016 SDK and Runtime zips produced with buildZips target are missing {notice,epl-v10}.html files; if root files exist they will now be copied into the SDK, Runtime, Examples zips; ${allZip} will also include this so it can be copied from there too (custom packaging in buildExtra.xml#extraPackaging task)
Testing Support
- bug 296352 Can't connect to vnc server - fixed using Xnvc option in Hudson job and improvements to testLocal task
Publishing Support
- bug 302170 Work around Hudson's missing lastS*Build folders - promote.xml will now recurse into Hudson job tree looking for correct build to publish
- Publishing support will improve thanks to bug 306854... anyone want to contribute to writing a Hudson job, please feel free!
Bug Fixes
- bug 304800 Temporary regression caused by adopting new build.xml script with too-aggressive cleanup default
- bug 307016 SDK and Runtime zips produced with buildZips target are missing {notice,epl-v10}.html files; if root files exist they will now be copied into the SDK, Runtime, Examples zips; ${allZip} will also include this so it can be copied from there too (custom packaging in buildExtra.xml#extraPackaging task)
Documentation & Branding
- EclipseCon 2010 Presentation, "Dash Athena Exposed" is available here.
- Common Build Infrastructure/Getting Started and Common Build Infrastructure/Getting Started/Build In Eclipse updated.
- Sample project template & generic build.xml updated.
- bug 272723 Logo design contest for Athena under way: vote early, vote often!
2 comments:
Is Athena tied to the eclipser.org infrastructure or is it something that any Eclipse plugin project could use? I've been wanting to look at using it to automate Subclipse builds in Hudson but I have always thought it only applied to Eclipse projects. If you read the documentation with the thought that this is the case there is nothing that really disavows of you this idea.
In your presentation I see screenshots of your JBoss projects using it, so now I am thinking I must be wrong and anyone can use this?
Are there any docs written from the perspective of an external plugin that has to setup all their own infrastructure? Do you still use the Eclipse releng tools etc?
Some defaults are used on build.eclipse.org to simplify use for Eclipse projects, but there's no reason you can't reuse this elsewhere. It just needs bootstrapping.
As to releng tools, yes, you can use that but AFAIK it only works with CVS. For now, anyway.
Regarding setting up your own infra elsewhere:
* http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started#Commandline_.2F_Server
I've got a todo to convert the bootstrapping script I use to build pi4soa and other JBoss Tools projects from shell to ant and port it back to Athena. It runs in our JBoss Hudson to set up the workspace and build in one step.
* https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/trunk/releng/hudson/run.sh
Post a Comment