Paolo Castagna wrote: > Andy Seaborne wrote: >> Actually, two builds: >> >> https://repository.apache.org/content/groups/snapshots/org/apache/jena/jena-arq/2.8.9-incubating-SNAPSHOT/ >> >> >> Build 1 a normal snapshot build. >> >> 20110929.134615-1 >> >> Build 2 is a build with -Papache-release so it's signed and there is a >> source-release.zip. The latter needs tuning - currently it's got >> class files in it, but it's sideffect of the fact I produced it in >> messy ARQ setup. >> >> 20110929.145040-2 >> >> Andy > > Great! > > Thanks Andy, "keep calm and carry on"! > > Maven requires a lot of patience (until everything works fine). > We are getting there, very close now. > > Later, I'll update LARQ accordingly. It must: > > - depend on the new ARQ SNAPSHOT > - point at the Jena top parent pom.xml
Done. Now LARQ depends on ARQ 2.8.9-incubating-SNAPSHOT. The artifact has been renamed to jena-larq. The LARQ pom.xml file is pointing at jena-top as its parent pom. I also added Jena_Top top to Jenkins. I suggest we use just one single pom.xml file (making pom2.xml (the new ones) the default ones). Paolo > > Once we have one (or two modules working) doing the rest is just > a boring and repetitive task. > > Paolo
