Re: [hibernate-dev] improved Eclipse project support

I'll take a look. Thanks Gunnar! On Fri 03 May 2013 06:13:53 AM CDT, Gunnar Morling wrote: > Hi Steve, > > I've pushed some commits for using the Animal Sniffer plug-in to > discover the usage of Java 7 APIs to my fork [1]. This uses the Ant > task and fails the build when using methods not exist

Re: [hibernate-dev] improved Eclipse project support

Hi Steve, I've pushed some commits for using the Animal Sniffer plug-in to discover the usage of Java 7 APIs to my fork [1]. This uses the Ant task and fails the build when using methods not existent in Java 6 such as emptyIterator(). I'm still in the process of testing this but thought it would

Re: [hibernate-dev] improved Eclipse project support

2013/4/17 Steve Ebersole > 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. > I'll give it a try. > On 04/16/2013 09:44 AM, Gunnar Morling wrote: > > 2013/4/16 Steve Ebersole > >> What is "conf

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] 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

Re: [hibernate-dev] improved Eclipse project support

I am not touching this :) I think I have explained this 198,052 times thus far lol https://community.jboss.org/wiki/GradleWhy see #4 On 04/15/2013 04:10 PM, Gunnar Morling wrote: > Hi Brett, > > That's good news, thanks for your efforts. Based on step 3 from your blog > post it seems as there st

Re: [hibernate-dev] improved Eclipse project support

Hi Brett, That's good news, thanks for your efforts. Based on step 3 from your blog post it seems as there still is a circular dependency between some of the modules/projects. Just out of interest, could you give some more details why this kind of setup is required? --Gunnar 2013/4/15 Brett Me

[hibernate-dev] improved Eclipse project support

There's been several complaints about ORM's use of Gradle not generating Eclipse projects correctly. This was recently cleaned up in HHH-7617 [1]. FYI, there's a quick blog post [2] about how to quickly get up-and-running. Please let me know if there are any further ways we could streamline t