MartyMcFly wrote: > > It directly converts dependencies in your workspace to project > dependencies if these projects exists. If the project does not exists, it > uses the jar from the repo. > > I was wondering if this behaviour is cloneable in gradle with the concept > of configurations. >
This is a very powerful concept, and I've wondered whether gradle would support it eventually. There are some issues to consider, but if it really is an accepted idiom, then it is worthy of consideration. Ideally there would be some way to specify a dependency as a regular project() like now that says, I need it available locally for things to work, and a remotableProject() that tries to find it locally, but digs up things in a repository otherwise. Along a similar vein, I was hoping at some point for there to be optionalProject() or optionalDependency() that says to include it in the dependencies it if it can find it, and set some variable that can be used to determine things like conditional compilation (exclusion usually) or other behavior. -Spencer -Spencer -- View this message in context: http://old.nabble.com/Problems-with-understanding-%22configurations%22-tp27418881p27452222.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
