From: Olaf H. <ha...@in...> - 2009-07-30 11:49:14
|
Hey Tim, On Thursday 30 July 2009 12:36:46 Tim Pizey wrote: > On Thursday 30 Jul 2009 10:30:53 you wrote: > > On Thursday 30 July 2009 11:20:26 Tim Pizey wrote: > > > I nearly had everything compiling with jena 2.6.0 but now loads of > > > compile problems with 2.6.2! > > > > I guess that's due to API changes in Jena or ARQ. > > Grrr. These permanent changes are very annoying. > > Wow, I seem to have fixed it! > > I now have ng4j building with Maven and latest and tests passing. Great job! Thanks! > I will go back over what I have done and look. > > Before I commit we need to tag the current tree as 'working with 2.5.7' > > This could even be a small release, however I do wish to keep up the > momentum, I go on holiday at the end of this week for two weeks, so it > would be good to commit today or tomorrow. > > What about: > > I tag current tree and make a 0.9.3 release, then commit my work so that we > can have a 0.9.3-SNAPSHOT for a while, during which we remove grddl. I don't want to stifle your enthusiasm but I don't see the justification for a new release. What would be the contribution of such a release except 'it works with Jena 2.5.7'? (Jena 2.6 would be something different, BTW) Apart from this doubt I must admit I didn't had the time yet to take a look at your work, unfortunately, and this won't change until the end of this week. I'm really sorry for this! I propose you tag the current tree as v0_9_1_for_Jena_2_5_7 and then you commit your Jena 2.6.2 compatible work. Would this be okay for you? Greetings, Olaf |