[GRADLE-467] Improve the command-line interface Created: 06/May/09  Updated: 04/Jan/13  Resolved: 31/Aug/09

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.8

Type: New Feature
Reporter: Hans Dockter Assignee: Hans Dockter
Resolution: Won't Fix Votes: 0

Comment by Hans Dockter [ 06/May/09 ]

This is a proposal from Steve Appling in regard on how to build project dependencies. Steve added this initially to http://jira.codehaus.org/browse/GRADLE-220

How about an extension to the task path syntax to handle this instead of more command line options.

Something like appending a '!' character to a project or task name to mean - just do this one without dependencies.

For example - in a two project system (consumer, provider subprojects), consumer depends on provider:

gradle :consumer:test
This will run full lifecycle (init-libs) on provider before init-test of consumer

gradle :consumer!:test
This would only run init-test tasks on consumer project (ignoring all task dependencies on other projects)

gradle :consumer!:test!
This would run only the test task only on the consumer project (ignoring all task dependencies) .

gradle test!
This would run only the test task in all projects.

In a large build system this can be very handy when you are trying to repeatedly run a task in a single module and know that the archives for the dependencies have already been built.

Comment by Hans Dockter [ 31/Aug/09 ]

We have implemented a different way of solving the underlying problem by introducing a lifecycle task.

Generated at Wed Jun 30 11:30:51 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.