On 08/03/13 15:41, Sergio Fernández wrote:
Hi,
On 08/03/13 16:24, Andy Seaborne wrote:
We gave up on maven at that point - the dist/ area is built with a shell
script to control the layout and exactly which files go in.
Custom script per project or something standard for all Apache projects?
It's Jena's script.
There are some standard patterns in projects but also minor differences
in many ways by the time the detail of requirements of each project are
factored in.
I'll take a look how you do it in Jena.
I noticed that some headers in files are still (c). POMs especially.
Particularly POMs: I need to check why the maven-license-plugin does not
cover those files.
What else did you detected?
Generally, it looks pretty good. My original msg was more about the
time it takes and doing after everything else is ready leads to a longer
release cycle. Sometimes things that need discussion or specific
checkign come oup, which means it not just a "doing" task.
I haven't been systematic in looking at the state of the git repo.
On a quick wander though the tree:
NOTICE.txt has "@@TODO@@" :-)
The import of jsonld-java needs handling.
Some of the test materials are different copyright/license (drop a
specific NOTICE/LICENSE files in the directory, maybe a README, so
anyone going straight there finds them)
platform/marmotta-sparql/src/test/resources/test-suite-archive
Andy, tanks for all your support!
NP - it's the mentors job to get you through what is one of the most
important thing about an Apache release - the quality of all the
non-technical aspects.
Working code? That's taken for granted!
Andy
Cheers,
