Re: [hibernate-dev] Importing OGM in Eclipse: workaround needed [AKA: the domino effect of fixing your own tools..]

2016-08-10 Thread Sanne Grinovero
On 10 August 2016 at 07:12, Guillaume Smet wrote: > Hi Sanne, > > First, sorry for not mentioning it as I run into this problem a few > weeks ago. I must admit that, as noone complained about it, I thought > I was the only one with the problem and it was already fixed in recent > Neon releases. I

Re: [hibernate-dev] Importing OGM in Eclipse: workaround needed [AKA: the domino effect of fixing your own tools..]

2016-08-10 Thread Gunnar Morling
Hi, Could you just add a note on the required plug-in version to the readme and/or contribution guide. Thanks, --Gunnar 2016-08-10 10:15 GMT+02:00 Sanne Grinovero : > On 10 August 2016 at 07:12, Guillaume Smet > wrote: > > Hi Sanne, > > > > First, sorry for not mentioning it as I run into th

Re: [hibernate-dev] Importing OGM in Eclipse: workaround needed [AKA: the domino effect of fixing your own tools..]

2016-08-10 Thread Sanne Grinovero
On 10 August 2016 at 09:42, Gunnar Morling wrote: > Hi, > > Could you just add a note on the required plug-in version to the readme > and/or contribution guide. Ok, adding to readme however let's hope it won't have to stay there for long: - https://github.com/hibernate/hibernate-ogm/pull/747 Si

Re: [hibernate-dev] Importing OGM in Eclipse: workaround needed [AKA: the domino effect of fixing your own tools..]

2016-08-10 Thread Gunnar Morling
> Since you felt this needed some addressing, wouldn't you rather apply my workaround to the project? Yes, any solution not requiring manual interfering would be preferred, but I understood Guillaume that the workaround is not really viable: > The fact is that using maven-jar-plugin 3.0.0 is not

Re: [hibernate-dev] Importing OGM in Eclipse: workaround needed [AKA: the domino effect of fixing your own tools..]

2016-08-10 Thread Guillaume Smet
On Wed, Aug 10, 2016 at 12:18 PM, Gunnar Morling wrote: > Yes, any solution not requiring manual interfering would be preferred, but I > understood Guillaume that the workaround is not really viable: > >> The fact is that using maven-jar-plugin 3.0.0 is not an option as it > has memory issues > >

Re: [hibernate-dev] Importing OGM in Eclipse: workaround needed [AKA: the domino effect of fixing your own tools..]

2016-08-10 Thread Sanne Grinovero
On 10 August 2016 at 11:18, Gunnar Morling wrote: >> Since you felt this needed some addressing, wouldn't you rather apply > my workaround to the project? > > Yes, any solution not requiring manual interfering would be preferred, but I > understood Guillaume that the workaround is not really viabl

Re: [hibernate-dev] Importing OGM in Eclipse: workaround needed [AKA: the domino effect of fixing your own tools..]

2016-08-10 Thread Gunnar Morling
Ah, sweet! Yes, then +1 for the workaround of course. 2016-08-10 12:20 GMT+02:00 Sanne Grinovero : > On 10 August 2016 at 11:18, Gunnar Morling wrote: > >> Since you felt this needed some addressing, wouldn't you rather apply > > my workaround to the project? > > > > Yes, any solution not requir