On 16/12/11 17:03, Dave Reynolds wrote:
...
Trivial nits that don't affect release:

Thanks for checking - I was more word-blind than usual.


# Release message:

s/jena-code/jena-core/

Possible also s/jena-zip/apache-jena/ to match the artefact name.

I'll fix this in the incubator-general@ message

# 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*

Fixed in SVN


# jena-core README.txt

Refers to doc/readme.html which does not exist any more.

Removed in SVN.

# 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).

Relief - it's right in the copy we ship!

Numbering restarted in the in-project versions.

# 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]
"""

Yes - I found that after the event - fixed - another X,000 warnings to go.

# 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.

Fixed.

The scripts in the dev system are different to the download zip ones. Sort of preparation for when/if we have a "command zip".

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

Done.

# 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.

That file was autogenerated by RAT. There should have been a manually edited version (automatic one neatened up).

I've put in a manual, better looking one here and other places.

Unfortunately, the DEPENDENCIES in the jars in WEB-INF always seems to be auto-generated by RAT and has the same oddities - anyone know how to control the choice of file?

# apache-jena-sources BUILD

s/alternativbely, yo/alternatively, you/

Done.



Dave

        Andy

Reply via email to