Re: [hibernate-dev] Project layout
On Fri, 2010-06-18 at 16:26 +0200, Andersen Max wrote:
I'm still confused why these things are to be mixed together and
not just separated out so the IDE's classpath/scopes
matches the compile scopes (seems like neither Eclipse, intellij nor netbeans would be
able to mimic
what is being attempted in Gradle?)
Consider:
`cd core`
`mvn install` <- works ok, the *unit* tests passed
`cd ../testsuite`
`mvn test` <- well shoot, now we have failures.
Sure would have been nice if the hibernate-core installation could have
failed, huh? ;)
Anyway, eclipse can have multiple output directories, but only one classpath so you would
probably
be able to get things to compile or code complete in eclipse that won't compile in
the Gradle build but if that is not a concern
then things should be fine.
btw. Its really a shame core will no longer be easy to import into Eclipse.
It's back to the "everyone attempts their best in creating an eclipse
config" from the old Ant days ;(
`gradle eclipse`
Why is that "everyone attempts their best in creating an eclipse
config"?
--
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org