The JSR 166 source tree has some non-Maven-standard features. easily handled in Ant, and it should be just as easy in Gradle. However . . .
The source hierarchy is structured like:
src
├── extra166y
├── jsr166x
├── jsr166y
├── main
│ ├── java
│ │ └── util
└── test
├── extra166y
└── tck
there is more but this is the important structure. The main is actually
Maven 1 structuring since the java is the name of the package java.util.
Using:
sourceSets { main { java { srcDir '../src/main' } } }
in the :jsr166 project works fine. However the jsr166y project always
recompiles using:
sourceSets { main { java { srcDir '../src/jsr166y' } } }
Gradle claims that the class files don't exist even immediately after a
successful compilation. I tried:
compileJava.source = fileTree ( dir : '../src' ).matching { include
'jsr166y/**' }
instead if the sourceSets specification but got exactly the same
recompilation behaviour. So Gradle is looking in a different place than
I am expecting. All the jars get produced as needed so something is
right. Possibly by fluke though.
Clearly I am missing something very simple as I know Gradle can do what
is needed. However it would be good to know what I am missing.
Thanks.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected]
41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected]
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
