On 23/09/11 13:21, Paolo Castagna wrote:
Andy Seaborne wrote:
On 22/09/11 19:53, Paolo Castagna wrote:
[email protected] wrote:
Modified:
incubator/jena/Jena2/SDB/trunk/lib-src/arq-2.8.9-SNAPSHOT-sources.jar
incubator/jena/Jena2/SDB/trunk/lib-src/arq-2.8.9-SNAPSHOT-test-sources.jar
incubator/jena/Jena2/SDB/trunk/lib/arq-2.8.9-SNAPSHOT-tests.jar
incubator/jena/Jena2/SDB/trunk/lib/arq-2.8.9-SNAPSHOT.jar
I think we should drop these.
And break SDB completely?
No. Why?
The development system relies on those jars as does the distribution.
It hasn't been changed to the new world order (ditto TDB).
SDB latest release will be unaffected by the change.
This keeps SDB development up-to-date with internal changes in ARQ.
I prefer that to having to go back much later and remember how to carry
out all the changes.
SDB development version can choose to depend on ARQ latest stable release
or ARQ latest SNAPSHOT. In this case if someone does something which would
break SDB, Jenkins will spot it (and it will get fixed immediately... i.e.
continuous integration (without manual intervention to update jars in the
lib directory).
?? It did.
I still think we should remove jars from the various modules.
There is still a manual step, it is just moved to development - after
svn update, you would have to do a "mvn dependency:resolve
dependency:sources".
I have ensured there is script, mvn-update, that does the right thing
for each module.
Paolo
Andy
Andy
