So I have taken a look at merging in jena-csv I can get it merged into the main git repository though it takes a bit of git magic to convert from SVN and merge it such that the commit history is left intact but it is doable.
However I then run into the fact that the code does not align with the rest of the mainline code base. In particular it relies on parts of the now removed atlas.csv package which mostly now just exists as a shim around Commons CSV. Also the command line tool has some dependency on a protected variable of CmdLangParse which appears to have been removed. Neither of these issues I could see quick fixes for so if someone who is more familiar with that code (you/Ying) could get it fixed up that would be much appreciated. Otherwise I will leave it out of my new release candidate when I do that tomorrow Rob On 01/10/2014 13:02, "Andy Seaborne" <[email protected]> wrote: >I suppose cumulatively it's worth re-rolling, thank you. > >The jena-security build failure is weird. > >Looking back what was wrong was wrong before so /personally/ if they >were fixed in master, I would be OK with a release. > >The bug fixes are just the usual bug fixes and fix things that have been >around for a while. > >One thing though - would it be easier to add jena-csv to build? If this >is a delay, then I'd say don't wait. If it's easy, then it makes >managing dist/ easier. > >I'll see if it just drops into the build ... > > Andy > > >On 01/10/14 12:34, Rob Vesse wrote: >> Due to various issues discovered with the release candidate this vote is >> now cancelled. >> >> You are still invited to check this release candidate in case there are >> other issues that need addressing. >> >> Can the relevant developers please take a look at and try and address >>the >> various issues Andy has raised with the release candidate. I will plan >>on >> rolling a new release candidate tomorrow unless anyone seriously objects >> >> Thanks, >> >> Rob >
