Russel,
I have the early beginnings of a plugin at
https://github.com/jvasileff/csm-petstore/tree/master/buildSrc/src/main/groovy/com/vasileff/ceylon/gradle
https://github.com/jvasileff/csm-petstore/blob/master/build.gradle
My idea is:
1) Decide on `/source` or `/src/main/ceylon` (or both), and test directory org
2) One or more source directories per task
3) One output directory per task (single invocation of `ceylon compile`. Each output directory is of course a module repository.
4) “Dependency” for Ceylon == module repository (~/.ceylon/repo, Herd, directories from #3, etc.)
5) Tasks inherit the "dependencies" of task’s they depend on
6) If possible, disable all default repository locations by default
On #4, the observation is that the finest granularity of a dependency for Ceylon is a module repository, rather than something like a class file, jar file, or maven module. The build system is pretty much unaware of and has no control over individual modules and versions.
I found item #3 to be important to help gradle’s up-to-date analysis. It also helps to keep things isolated for #4.
As you can see, my last work on this was 3 months ago...
John
> --
> You received this message because you are subscribed to the Google Groups "ceylon-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
ceylon-users...@googlegroups.com.
> To post to this group, send email to
ceylon...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/ceylon-users.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/ceylon-users/1434371847.3613.71.camel%40winder.org.uk.
> For more options, visit
https://groups.google.com/d/optout.