On 21/11/11 23:31, Paolo Castagna wrote:
Hi Andy
Andy Seaborne wrote:
Paolo,
I'm confused - could you explain how this would be used in our release?
Some examples:
Apache Avro is a multi-module project: one single project, different modules.
It is distributed here: http://www.apache.org/dist/avro/
Maven artifacts are here: http://repo1.maven.org/maven2/org/apache/avro/
Apache Whirr is a another multi-module project: one single project, different
modules.
Distributed here:
http://www.apache.org/dist/incubator/whirr/whirr-0.6.0-incubating/
Maven artifacts are here: http://repo1.maven.org/maven2/org/apache/whirr/
Apache CXF
http://www.apache.org/dist/cxf/
http://repo1.maven.org/maven2/org/apache/cxf/
Apache Lucene
http://www.apache.org/dist/lucene/java/3.4.0/
http://repo1.maven.org/maven2/org/apache/lucene/
The /dist/ is a "-src" artifact.
JenaDist does not build "-src" artifacts.
"-src" are the artifacts that the vote for a release is about (now
called "source-release" if you use current RAT, which we do). Avro does
not use RAT to do it, it uses ant.
They are a complete copy of the release tree.
But there aren't any for JenaDist, or rather it's 16Kbytes which is
rather unlikely (it's just JenaDist).
...
Do these cause you the same sort of confusion?
They do not answer the question or rather they show that JenaDist isn't
complete.
Where is the master artifact (artifacts?) that the vote is about?
Have you run "mvn clean install -Papache-release" and looked at the
contents? (I have - I see strange things.)
It's OK if JenaDist needs time to stabilize. We do a more manual
process this time; I'll kludge something together when I have some time.
Andy
Paolo
