1) Making IDE setup simpler does not necessarily mean making the CLI
builds more complicated. That is a somewhat obvious statement, but one
I think we need to keep in mind here.
2) The AnnotationProcessor question was kind of a separate question. I
am curious why you think that combining the
On 17 Jan 2013, at 9:53 PM, Steve Ebersole wrote:
> Personally I find it funny. To me this question of "circularity" is exactly
> the same. Works great in the build in any and all ways, but the IDEs have
> issue with it to varying degrees. Yet everyone wants to change the
> circularity thi
On 17 Jan 2013, at 9:33 PM, Brett Meyer wrote:
> "Get the sources and load it directly in your IDE. IMO that is stupid."
>
> Honestly, that's always been the absolute *first* thing I do. I'd argue that
> most contributing developers are interested in the src, first and foremost.
For sure. I
e
>
> - Original Message -
> From: "Steve Ebersole"
> To: "Hardy Ferentschik"
> Cc: "hibernate-dev"
> Sent: Wednesday, April 17, 2013 12:58:19 PM
> Subject: Re: [hibernate-dev] Build and AnnotationProcessors
>
> On Wed 17 Apr 2013 11:44:18 AM
e
- Original Message -
From: "Steve Ebersole"
To: "Hardy Ferentschik"
Cc: "hibernate-dev"
Sent: Wednesday, April 17, 2013 12:58:19 PM
Subject: Re: [hibernate-dev] Build and AnnotationProcessors
On Wed 17 Apr 2013 11:44:18 AM CDT, Hardy Ferentschik wrote:
For the Eclipse side its actually pretty simple to add this capability
of generating all sources when the project is generated since the
recommendation seems to be to do this from the Gradle side (`gradlew
eclipse`). We'd just need to add a doFirst action to call the
generateSources task. The
Just to chime in on the IDE use. While hibernate is on the significantly
complex side of things for OSS projects go most projects I deal with
that are using Maven or Gradle I do just checkout in my IDE and expect
to work.
For 99% of maven projects this is the case, I checkout/clone the
project, im
On Wed 17 Apr 2013 11:44:18 AM CDT, Hardy Ferentschik wrote:
>
> On 17 Jan 2013, at 6:30 PM, Sanne Grinovero wrote:
>
>> AFAIK the reason we originally had a separate phase for annotation
>> processors was to workaround the following javac bug:
>> http://bugs.sun.com/view_bug.do?bug_id=6512707
>
>
On 17 Jan 2013, at 6:30 PM, Sanne Grinovero wrote:
> AFAIK the reason we originally had a separate phase for annotation
> processors was to workaround the following javac bug:
> http://bugs.sun.com/view_bug.do?bug_id=6512707
>From a Maven perspective (not an ORM issue longer) there is/was also
AFAIK the reason we originally had a separate phase for annotation
processors was to workaround the following javac bug:
http://bugs.sun.com/view_bug.do?bug_id=6512707
Apparently the problem wouldn't trigger when running the annotation
processor in a separate phase.
Seems resolved now, still that
On Wed 17 Apr 2013 11:08:28 AM CDT, Hardy Ferentschik wrote:
>
> On 17 Jan 2013, at 5:32 PM, Steve Ebersole wrote:
>
>> As discussed a little in HHH-8140[1] and on the earlier Eclipse thread,
>> I'd like to look at simplifying the build a bit around making IDE setup
>> easier. One thing that came
On 17 Jan 2013, at 5:32 PM, Steve Ebersole wrote:
> As discussed a little in HHH-8140[1] and on the earlier Eclipse thread,
> I'd like to look at simplifying the build a bit around making IDE setup
> easier. One thing that came to mind was looking at source generation.
> Today we have sourc
12 matches
Mail list logo
