On Sep 4, 2009, at 1:56 AM, Adam Murdoch wrote:
Hi,
I'd like to make some changes to our lifecycle tasks, which I think
will simplify things, and make the intent a bit clearer:
1. Collapse 'libs' and 'dists' into a single task. I like the term
'package'.
Which is unfortunately a reserved word, isn't it?
That is, you package a java project into a deployable thing, which
might be a library, a web app, a command-line app, or whatever.
I guess it depends very much on your project. For some project it
makes sense to have the two different tasks we have now. They
sometimes want to produce the jars, other times the zips. On the other
hand often one of both is superfluous. So it might make sense to
settle on something more abstract which fits every project. For
example in the gradle build, the root project would produce the dist
and gradle-core the jar. And then people can somehow customize
something more fine grained on top of that, if needed.
2. Move 'check' from the code quality plugin to the java plugin (or
maybe the base plugin). Change 'check' to depend on 'test'. Possibly
rename it to 'verify'. That is, verification becomes a basic
concept, and tests become a type of verification.
I like this very much.
3. Move the 'dists' configuration out of the java plugin. It would
be added by any plugin which actually produces a distribution, such
as a java application plugin. Perhaps the war plugin should add the
war to this configuration.
As I understood you above, they would use the 'package' task for this,
wouldn't they?
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
