On Sep 12, 2008, at 12:28 AM, Adam Murdoch wrote:
Hans Dockter wrote:
Hi Adam,
On Aug 29, 2008, at 2:44 PM, Hans Dockter wrote:
I'm still thinking about the best way to marry this with the
current convenient definition of a hierarchical physical project
layout. One other issue is how to do partial builds. For virtual
hierarchies there is no way to automatically find the root
project if you are in a subproject. My idea is to specify the
rootproject with a command line option. What do you think?
1.) Execute a specific task of a project from anywhere within the
multi-project hierarchy.
a.) Physical Hierarchical Layout (PHL):
gradle :<projectPath>:<taskPath>
b.) Virtual Layout (VL): gradle -
R<fileRootProjectPath> :<projectPath>:<taskPath>
2.) Execute a task based on name matching in a subproject hierarchy:
a.) PHL: Go to the subproject dir and type gradle <taskName>
b.) PHL: From anywhere: gradle -p<fileSubProjectPath> <taskName>.
But we have to specify the physical path of the subproject here.
c.) PHL: From anywhere within the multi-project hierarchy via
Gradle project paths. This is not possible yet. Should we enable
this?
What about c.)?
I think it makes sense. How would this work on the command line?
May be by using s special separator. That way we could continue to
mix, which is pretty cool I think.
For example:
gradle :<projectPath>*taskName1 :<projectPath>*taskName2
clean :<projectPath>:taskName3
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
