I'm holding off on being helpful until you all are clear on what you're trying to do.
On Tue, Nov 22, 2011 at 5:31 AM, Paolo Castagna <[email protected]> wrote: > > > Andy Seaborne wrote: >> On 22/11/11 09:24, Paolo Castagna wrote: >>> >>> >>> Andy Seaborne wrote: >>>> 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? >>> >>> In the snapshot|staging repository (in addition to all the other >>> artifacts we already have): >>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-dist/2.6.5-incubating-SNAPSHOT/jena-dist-2.6.5-incubating-20111122.000215-1-src.zip >>> >>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-dist/2.6.5-incubating-SNAPSHOT/jena-dist-2.6.5-incubating-20111122.000215-1-bin.zip >>> >> >> apache-jena-* seem to be copies of the build state, not the release tree >> >> 1/ There are lots of .class files >> 2/ Directories have been renamed. >> >> It's produced by assembly-sources.xml from stuff processed (filtered, >> selected etc) into target/ -- don't we need a true copy of the release >> tree? >> >> The simple way to do that is a small script that zip/tars the right svn >> trees. > > Ok, I am moving the JenaDist back to the Scratch area. > > Paolo > >> >> Next up - release notes. >> >> Andy >> >>> The name needs to change from jena-dist to apache-jena. >>> <fileName> does not work as you pointed out. >>> >>>> Have you run "mvn clean install -Papache-release" and looked at the >>>> contents? (I have - I see strange things.) >>> >>> I have been testing with mvn -Papache-release clean package. >>> I'll see what happens with mvn clean install -Papache-release. >>> >>>> 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. >>> >>> Ack. >>> >>> Paolo >>> >>>> >>>> Andy >>>> >>>>> >>>>> Paolo >> >
