On 05/09/11 14:58, Paolo Castagna wrote:
Hi,
I propose these changes (see patch attached) to the ARQ's pom.xml file
and, if that is ok, similar changes to for Jena and the other Jena modules.
We will be using this<groupId>org.apache.jena</groupId> as groupId for
all the artifacts produced by the Jena project.
We can start publishing SNAPSHOTs to the Apache Maven Repository [1] and
receive feedback on those as well as the technical details of the releases
in Apache.
Paolo
[1] https://repository.apache.org/
There are various things we need to do to get the build into a state
where we can release on Apache. We also need to sort out the build
system (more in another email).
I'd prefer that the changes as seen by our users are made in a single
step, or as few steps as possible. Advanced users do pickup snapshots,
as do builds of the other components that depend on ARQ. Fuseki and
TxTDB are picking up ARQ snapshots currently.
Just moving the non-Apache releaseable snapshots to Apache causes users
(and other modules) to have to do something in order to keep picking up
the latest from the new location. Just making this change and then
using it would force changes things so it has a cost.
Let's at least try to do this with a minimal number of change points,
ideally one. Let's discuss where we want to get to, then see the way to
get there before making incremental steps that cause a number of
external changes.
Andy
