Simon Helsen wrote:
> Paulo,
> 
> thanks. The pom.xml information is certainly useful as it proves how the 
> tests were run. In most cases this will be enough. However, problems start 
> happening when a later component (e.g. LARQ) has been tested with later 
> snapshots than the current release. I think it is important that all 
> components can run with a release for the other components (perhaps you 
> already guarantee this?) Now, even if this is the case, it may still be 
> tricky because approvals or adoptions by jena consumers (like myself) are 
> done on a specific version release and updating it quickly because one 
> component was not released before may be hard or even impossible.
> 
> So, from a consumer point of view, you ideally release everything together 
> :-). It would also get rid of the various unaligned version numbers of 
> different components, which are very confusing. Ideally, I just say "Jena 
> 2.7.1" (and includes IRI 2.7.1, ARQ 2.7.1, TDB 2.7.1, etc.) 
> 
> Simon

Hi Simon,
yep, thanks for sharing.

This is relevant to JENA-191 where Jena multi-module structure and build system
is discussed, there is a hint to a "single version number build for Jena" as
well: https://issues.apache.org/jira/browse/JENA-191

I also think that one of the benefits of a single version number for users would
be to reduce confusion.

The biggest drawback is that all modules needs to be released together (at the
rate we are making releases, I don't think this can be a problem). However there
is a potentially bigger issue. What if one of the modules is not ready to be
released and you need a bug fix release? If it's an optional module, you can
exclude it, if it is not an optional module you have a problem.

Having said this, I would still be in favor of a single version number build for
Jena given the fact that for most of the Jena modules the trunk is always in a
releasable state.

For LARQ (being an optional extension) problems are even less. Indeed, at the
moment, it is not even included in what we call the "Apache Jena" distribution.

Paolo

Reply via email to