Re: [hibernate-dev] improved Eclipse project support

I think it would be great if you wanted to try including this in the ORM build. Worst case you could just use the sniffer ant tasks from Gradle. On 04/16/2013 09:44 AM, Gunnar Morling wrote: > 2013/4/16 Steve Ebersole > > > What is "configured JDK baseline

Re: [hibernate-dev] improved Eclipse project support

2013/4/16 Steve Ebersole > Well, maybe you have not seen > https://hibernate.atlassian.net/browse/HHH-8140 > No, I haven't. Nice, seems we agree then :) > But really, tell me what is wrong with this "circularity"? And try not to > use IDEs as the justification; I mean conceptually, what is w

Re: [hibernate-dev] improved Eclipse project support

2013/4/16 Steve Ebersole > What is "configured JDK baseline"? Do you have to point to a JDK path? If > so, no difference than just setting the javac bootstrap option to a local > path. No, you don't point to another JDK path, you use the JDK you are on, i.e. Java 7. You just say which JDK vers

Re: [hibernate-dev] improved Eclipse project support

Well, maybe you have not seen https://hibernate.atlassian.net/browse/HHH-8140 But really, tell me what is wrong with this "circularity"? And try not to use IDEs as the justification; I mean conceptually, what is wrong with this "circularity". And note that i use quotes here ;) On 04/16/2013

Re: [hibernate-dev] improved Eclipse project support

Gunnar, somehow replying to your replies always forces my email client to use my from address that is not registered to this list :( Anyway... What is "configured JDK baseline"? Do you have to point to a JDK path? If so, no difference than just setting the javac bootstrap option to a local pa

Re: [hibernate-dev] improved Eclipse project support

In HV, we use the Animal Sniffer plug-in [1] for that purpose. This checks the code base against a configured JDK baseline and fails the build, when e.g. using a method which is not part of the targeted JDK release. In other words, you still use your current JDK for building (avoiding any bootstra

Re: [hibernate-dev] improved Eclipse project support

Mainly thats an issue with that fact that so far we have not defined 'bootstrap class path' option to javac to go along with the source/target compatibility settings. The difficulty is that defining bootstrap for javac becomes very system specific (it needs to name a path). Sure we could exte

Re: [hibernate-dev] hooking native MongoDB queries on mapped entities

I've applied the changes following Emmanuel suggestions: https://github.com/DavideD/hibernate-ogm/commits/nativeq I've created a very simple implementation of SqlQuery and with this prototype it is possible to execute session.createSqlQuery(...) and entityManager.createNativreQuery(...). I've cha

Re: [hibernate-dev] improved Eclipse project support

On a related note: I know Java 7 is required to compile ORM, but is Java 7 also the required runtime Java version now (I vaguely remember a related discussion around the JPA API JAR)? I'm asking, because the Java 7 method Collections#emptyIterator() is used at two places, making this code not run

Re: [hibernate-dev] improved Eclipse project support

2013/4/15 Steve Ebersole > I am not touching this :) > > I think I have explained this 198,052 times thus far lol > I must have missed this then. Or I was not yet part of the team at that time. > > https://community.jboss.org/**wiki/GradleWhysee > #4