On 17/06/2011, at 6:49 PM, Mirko Schroeder wrote:
Now I've separated the build into several parts as there are the
main/default build, the site build, and some other useful tasks nothing to
do with the actual build.
How have you separated them?
There are some archive tasks in the project,
On 18/06/2011, at 1:13 AM, Gerwin Jansen wrote:
I have the following use case:
My multi-project setup needs to support subversion partial check-out.
This means that my subprojects are sometimes part of the check-out and
sometimes not. So a subproject is sometimes a project dependency and
So I finally took the time to extract that part in a seperate plugin.
I also put in a little sample.
http://projects.emesit.de/projects/gradle-eclipselinkprojects/wiki
Am 17.06.2011 15:38, schrieb James Carr:
Is your plugin published somewhere?
On Thu, Jun 16, 2011 at 4:55 PM, Ruediger
well in this case it is fetching data from an external source (web
service call). There is no way to know if it's up-to-date or not,
it's a human judgement call.
This issue would be solved if I could count on the order of
buildLanguagePackTask.dependsOn([localeExportMessages,
If the order of dependsOn tasks is guarantied, you open up a whole can
of worms with dependencies being in the wrong/conflicting order, or
the inferred order from resources being in a different order. It's
just not the right direction to head. It's just serious bad times.
You're swimming against