What are the build exceptions in JDBC / JenaStatement? Rob
On 9/6/13 2:29 PM, "Andy Seaborne" <[email protected]> wrote: >Is everything ready? > >All the modules are now integrated into the build and the snapshots will > now be what the release is except for signing and version numbers so >please poke and prod the builds. > >I've made some changes: > >1/ Instead of the default being a developer build, the default is a >complete build and there is a restricted set of modules built with >profile "dev". This is to avoid mistakes doing a release :-) > >The Jenkins deploy job is now doing a full build (which takes 15mins on >my machine even without any uploads). > >The Jenkins test job is a -Pdev build. > >Maybe we need more profiles. Please take a look and see what >improvements can be made. > >2/ jena-spatial now in the Fuseki server build > >Still need to check the distribution versions of NOTICE and LICENSE but >jena-spatial only adds com.spatial4j:spatial4j over what that added by >jena-text. > >3/ Include SDB in apache-jena > >jena-sdb in the apache-jena lib/ directory. > >Not sure is this is the right thing to do - opinions? options? > >4/ The website needs link checking > >Could someone volunteer and run a link checker on the staging site? I >think some of converted pages may have bad internal links - this is >probably not new. > >5/ The build exceptions in JDBC / JenaStatement > >... are really quite worrying to the RM! > >6/ An "advanced notice" email sent to users@ > > Andy
