Thanks for your reply Peter.  I do understand your response and I know that
the gradle way of doing this will work just fine.  On a personal level I'm
fine with the solution.

However, this became a big discussion in the office and it felt a little
like the old maven conversations. "It works fine if you do it the way the
way they want, which is clearly documented, but no, we can't do it our way
without writing our own plugin."  You see we have a rather common business
model with FTE's working out of multiple offices, varying numbers of
contractors, and varying numbers of off shore developers.  So, when our
build makes a physical statement like "src/scala" we intend it to be a true
statement.  Not all developers would think to look in src/scala for java
files.  I know this is a mundane problem and is easily solved through
effective communication.  However, since we aren't communicating effectively
by placing java files in the scala directory, that argument is not a very
strong one.  

When I did the first the POC for gradle I was blown away by how configurable
it was! I could take a LARGE and COMPLEX legacy java app (over 10 years old)
and get it working with gradle in the EXACT same way as in ant, but with
hundreds of fewer lines in the build files.  The gradle folks really seemed
to nail the concept of configurable convention!  But this one little wrinkle
with scala challenges how configurable gradle really is.  So, if the answer
is "no, you cannot configure the workflow" I'm fine with communicating that
to my superiors.  I just don't want to make a false statement.  I've read as
much I can find using google, and I don't really have any answers yet. 
That's why I'm asking here.

Thanks for your thoughtful responses.

Bart

--
View this message in context: 
http://gradle.1045684.n5.nabble.com/Mixed-Scala-Java-project-tp3378120p4381989.html
Sent from the gradle-user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to