Steve Ebersole wrote:
>
> 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.
>
All that's needed to achieve standardization is another lifecycle task that
Gradle provides out-of-the-box, e.g. "docs".
Steve Ebersole wrote:
>
> 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?
>
task generateSources {
outputDir = ...
...
}
sourceSets.main.java.srcDir generateSources.outputDir
compileJava.dependsOn generateSources
With some effort we should be able to get rid of the last line. IDEA and
Eclipse tasks handle additional source dirs fine.
--
Peter Niederwieser
Principal Engineer, Gradleware
http://gradleware.com
Creator, Spock Framework
http://spockframework.org
Twitter: @pniederw
--
View this message in context:
http://gradle.1045684.n5.nabble.com/GenerateSources-functionality-for-SourceSets-tp4600652p4785039.html
Sent from the gradle-dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
