2009/1/31 Hans Dockter <[email protected]> > In a chat I had with Jon Cox he had some interesting ideas for improving > our command line and path handling. > > Path handling: > > It would be much nicer to have a *nix path separator for our project and > task paths. The reason why we use a colon as a separator is that we have > file and directory tasks, where the task name contains a slash. > > What we could do instead it to allow a slash separator like: > /project1/subproject2/task3 > If you have a directory task you can do: /project1/subproject2/+/dir1/dir2 > > As directory paths are rarely referenced by there full path and are usually > not used as a primary task for execution, I can live with this pretty well. > One exciting thing about slash separators is that you can use tab completion > in case of a hierarchical project layout.
That would be very nice indeed. > > > Command Line usage: > > gradle /project1/subproject2 clean compile +/dir1/dir2 -test > > /project1/subproject2 sets the project where the tasks should be applied > to. Those tasks use name matching for execution. This means if subproject2 > has further subprojects with this task names in its hierarchy, they are > palso executed. > > One thing I like very much is -test instead of -Dskip.test And again a very nice idea, cool ideas all the way :) > > > - Hans > > -- > Hans Dockter > Gradle Project lead > http://www.gradle.org > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
