On Mon, Feb 13, 2012 at 8:16 AM, Andy Seaborne <[email protected]> wrote: > Points raised and current status: > > > 1/ Broken source-release artifact > A "trunk" sneaked in. > [Fixed] > > 2/ LICENSE (& NOTICE, if any requirement) for the distribution needs to > account for things shipped > icu4j, slf4j, jena/plugged in software. > Fixed - Two versions of LICENSE and NOTICE for jar and distribution. > > 3/ The TDB jar has a wrong NOTICE in META-INF. > (err - this is created by Apache RAT - it needs to be overriden) > Fixed - src/main/resources/{LICENSE,NOTICE,DEPENDENCES} > Means unDRYness <sigh/>. > > 4/ release-source and distribution in maven > > ** Discussion point. > > "mvn clean deploy -Papache-release" > puts release-source into the maven repo > > I've moved the distribution files to target/dist but now they don't get > processed by deployment (no signing) nor do we have a route to get snapshot > distributions out for people to pick up and test. > > 5/ dist/ structure > > ** Discussion point. > > It is suggested we have a layout of "sources/" and "binaries/". > This is a bit of a "C" world view. > > We have two audiences: the Apache process and norms, and Jena users. We > distribute direct to users. Some of our users are not experienced Java > programmers so something very clear as to what to download will reduce > support costs. > > A possibility is more appropriate naming: > > source-release/ > download/ > > Even then "source-release" is unclear to anyone not versed in the Apache > naming conventions. > > Or put the user downloads somewhere else entirely. I don't like this > because of the recurring work needed. > > 6/ zip for release-source (no.tar.gz in dist/) > [Done - tar.gz added] > > 7/ KEYS > Confusion - the new dist area is to be merged into the existing one. > > 8/ Eclipse files. > > This is about the SVN tagged, not the source-release which skips those > files. > > A/ It does not set the compiler as far as I can see. > B/ There should be a declaration of category of Java: JavaSE-1.6 > > Having used eclispe:eclispe and m2e on Any23, I can say that they are not > perfect. For both of them, I ended up with a collection of broken Eclispe > projects. > > I don't want to tag something that isn't exactly the state of the project at > the moment of release. > > I see no harm in trying to make "svn checkout" in Eclipse work in a single > step.
With the latest m2e in Indigo, I'm able to open the Maven projects in Eclipse. The maven-antrun-plugin:run goal will have to be marked as "ignore", so you need to build from the command line once to generate the appropriate files. But once that is done, m2e works pretty well. The dependency hierarchy view is quite handy, as well as my favorite feature, which is the auto downloading and attaching of source jars for dependencies as you navigate into them. > ** Discussion point. > > 9/ Minor: > > jena-tdb-0.9.0-incubating-source-release.zip > contains a tmp directory from testing. > [Fixed] > > 10/ In ChangeLog: - should mention change of mvn artifact and groupId ? > [Fixed] > > 11/ log4j.properties and commands > Work needed.
