Robert Burrell Donkin ha scritto:
On Sat, May 10, 2008 at 11:49 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Robert Burrell Donkin ha scritto:
i'll fix this in the ant build

i'm happy to leave choice of tool to the release manager

+1

2) Added the rat checks to the pom so I was able to run rat easily.
Everything is ok but I had to add this excludes:
<exclude>NOTICE.base</exclude>
<exclude>LICENSE.apache</exclude>
they are used by the ANT build to put "better" NOTICE/LICENSE in the
resulting jars.

<exclude>src/site/resources/rfc2234.txt</exclude>
<exclude>src/site/resources/rfc2244.txt</exclude>
<exclude>src/site/resources/rfc2298.txt</exclude>
<exclude>src/site/resources/rfc3028.txt</exclude>
They are rfc: do they need a license header?

they include a license header just not an Apache one ;-) it should be
retained unchanged.

i'm not sure whether to remove them complete and just use links or to
add a LICENSE.rfcs document at top level (since we only distribute
them with the source).

rfc are documents not likely to be removed from the internet so I think there is no need to include them in our source distribution and we can simply use links in our website.

It does not make sense to worry about licensing and notice for not critical files: let's remove them.

Anyone against this?

<exclude>stage/oro/poms/oro-2.0.8.pom</exclude>
This is a very simple pom (the one automatically generated by maven for the
artifact) from an ASF project. It does not have a license header and I guess
we should include as is.

i was a little unsure too

if it's simple i'd prefer a clean room implementation with header and
known provenance

The currnet pom is exactly what maven automatically generates if we ask him to generate a clean pom simply providing the artifactId/groupId/version informations. BTW I think we can remove that pom: we already removed poms in the stage for every other library and the m2 based build should not be using the local stage anymore.

Anyone against the removal of the oro pom.xml?

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to