On Jun 18, 2010, at 17:10, Steve Ebersole wrote: > How does it not work with Hibernate though? I mean at the end of the > day, Hibernate is not that complicated of a project structure. Yes > there are some peculiarities with regards to mixed jdks and some other > stuff, but that is not the sort of things you previously discussed as > lacking in the gradle eclipse plugin.
hmm...that is an example of the challenges with things not separated out. note, for hibernate core this is probably fine in the IDE. > Before you had mentioned enabling > "features" inside the eclipse project. What special features are we > using here? If I want to enable lets say the FindBugs plugin or some Antlr plugin then it will overwritten by these shot-and-forget generation. > To me in IntelliJ, that would equate to things like we are producing a > war and want container integration enabled. But we dont have that in > Hibernate no, I know. > > Or we are writing some groovy stuff and want the Groovy facet enabled. > Again, none of that here. I thought the gradle scripts were groovy so sounds rather relevant here does it not ? > So I am totally lost what you mean here. Or are you just talking about > in general and there is no specific issue in importing Hibernate into > eclipse? Its certianly something you probably can live without and those using the IDE for more than a java compiler and fancy editor its fine. It is though a step backwards - but I agree its a smaller step backwards than the step forward you hope to go with using Gradle instead of mvn. /max > > On Fri, 2010-06-18 at 16:40 +0200, Andersen Max wrote: >> On Jun 18, 2010, at 16:26, 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?) >>> >>> 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 ;( >> >> note, I haven't checked the last gradle eclipse stuff but last time it was >> *very* basic. >> >> But just wanted to point that out in case someone comes back and tell me >> they improved >> it greatly in some recent release ;) >> >> /max >> > > -- > Steve Ebersole <st...@hibernate.org> > http://hibernate.org > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
