On Tuesday 06 April 2010 13:33:03, Spencer Allain wrote:
> I've not dug into the sources to confirm this, but I suspect that all
> jar/war/tar/zip type tasks for a project are auto-added as dependencies of
> the assemble task (which is always run as part of the build task).
Well - the behaviour of my sample states that you're right.
I consider that kind of suboptimal ;)
For my project I have several archive-tasks, that should not be bound to the
build-task. For me, build is the daily working target for a developing
stage - and I have several archives, that I need to build for release stage
only.
So how can I create archives, that don't get auto-added to the build task?
If that's not possible yet, I'd like to add it to the (not so far) wishlist.
Just to extend my wishes:
Is it possible, to split the task of building all subprojects from the build
of the rootProject?
Currently the build creates an empty jar for the rootProject - and I need the
name of that archive for a release-bundle, created with another task.
kind regards
Geronimo
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
