On 16/12/11 17:03, Dave Reynolds wrote:
On Wed, 2011-12-14 at 17:45 +0000, Andy Seaborne wrote:
Hi,
Here vote on a release build for Jena 2.7.0
Versions:
jena-top 0-incubating
jena-iri 0.9.0-incubating
jena-code 2.7.0-incubating
jena-arq 2.9.0-incubating
jena-zip 2.7.0-incubating
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-331/
Proposed dist/ area:
http://people.apache.org/~andy/dist-apache-jena-2.7.0-incubating-RC-1/
Keys:
https://svn.apache.org/repos/asf/incubator/jena/dist/KEYS
+1
Fantastic job Andy!!
Checked basic signatures, hashes, BUILD/LICENSE/NOTICE files, maven
install from sources and test of random jena code using the results of
maven install. All fine as far as I can see
Trivial nits that don't affect release:
Bother.
If anything is changed, then the release will have to be restaged.
(we need to find away to do release candidates - something that is
almost but not quite a release, but which is "frozen" in someway).
If any bytes are changed, then it's not the same vote so we'd go round
again.
My expectation is that incubator-general@ will turn up something and
we'll have top go round the loop again.
As you have said the corrections don't affect the release, I'll continue
with the bytes that currently exist.
Andy
# Release message:
s/jena-code/jena-core/
Possible also s/jena-zip/apache-jena/ to match the artefact name.
# BUILD files for all projects
These reference in various places to:
jena-zzz-VER-incubator*
whereas the candidate release artefacts are all called:
jena-zzz-VER-incubating*
# jena-core README.txt
Refers to doc/readme.html which does not exist any more.
# jena-core ReleaseNotes.txt
Top entry is for "Jena 2.6.5" shouldn't that be 2.7.0?
(It's right in apache-jena/ReleaseNotes-Jena.txt).
# jena-arq pom.xml
The maven-resources-plugin is declared twice which causes Maven (3.0.3)
to complain:
"""
Some problems were encountered while building the effective model for
org.apache.jena:jena-arq:jar:2.9.0-incubating
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but
found duplicate declaration of plugin
org.apache.maven.plugins:maven-resources-plugin @ line 200, column 15
[WARNING]
"""
# jena-arq README.txt
For setting up the command line arguments the README talks about setting
JENAROOT. If I try that the scripts complain that they were expecting
ARQROOT.
Might be worth explicitly mentioning in here that when working from an
ARQ source release and wanting to set up command line use then you also
need to do:
mvn -DoutputDirectory=lib dependency:copy-dependencies
# apache-jena-sources DEPENDENCIES
Looks odd in having several duplicate entries (three references to each
of jena-core and jena-arq for example) and having xerces as being from
an unknown organization.
# apache-jena-sources BUILD
s/alternativbely, yo/alternatively, you/
Dave
