>In order to properly set up an IDE project, you *have to* know the full set of sources, including generated sources right? How do you achieve that as of today in gradle?
In M4+ you can register generated sources via sourceSets and IDE plugins will automagically use this info. Short example: sourceSets.main.output.dir(generatedResourcesDir, buildBy: 'generatedMyResources') More info here: http://gradle.org/releases/latest/docs/dsl/org.gradle.api.tasks.SourceSetOutput.html Cheers! On Thu, Sep 8, 2011 at 9:52 PM, Steve Ebersole <[email protected]> wrote: > Sorry for the late reply on this. Comments inline... > > > On Tue 19 Jul 2011 07:33:32 PM CDT, Luke Daley wrote: > >> >> On 20/07/2011, at 1:39 AM, Steve Ebersole wrote: >> >> Perhaps another way to look at this is the notion of higher level >>> lifecycle tasks (maybe somewhat akin to what Maven calls phases). We had >>> talked about this many times before for stuff like docs. The notion of >>> building docs is a higher level concept where tasks like jdocbook would fit >>> in. >>> >> >> What do you want to do with this grouping though? >> > > Imagine you want to build all documentation. Lets say just javadocs and > docbook to be simple. How do you achieve that today? AFAIU you would need > to execute: > `gradle javadoc buildDocs` (buildDocs is a task added by the jdocbook > plugin). > > Now granted, yes you could set up some task deps: > buildDocs.dependsOn javadoc > > and then: > `gradle buildDocs` is sufficient > > but that is something each project has to do on their own. And it puts > hurdles in place for seamlessly moving between projects since each might do > this differently. > > Of course I am assuming that a developer being able to move from one > project to another seamlessly in this manner is a goal. If not, then I > guess this is all moot. > > > >> Applied here, compilation would be such a higher level concept as would >>> source-generation. In this way it would be nice if the Antlr task could >>> say it "is of source-generation type" or it "is part of the >>> source-generation phase". In the latter case, if source-generation is >>> implemented as a "grouping task", then all the Antlr plugin needs to do is >>> to add its task to the source-generation task deps. >>> >> >> >> I don't see what you would achieve with such a grouping. >> > > Well consider a simple IDE import or IDE project generation. In order to > properly set up an IDE project, you *have to* know the full set of sources, > including generated sources right? How do you achieve that as of today in > gradle? > > > -- > [email protected] > http://hibernate.org > > ------------------------------**------------------------------**--------- > To unsubscribe from this list, please visit: > > > http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email> > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito
