incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <>
Subject Re: [VOTE] Approve release Apache UIMA 2.2.1-incubating
Date Mon, 17 Dec 2007 21:27:41 GMT
sebb wrote:
> On 17/12/2007, Martijn Dashorst <> wrote:
>> On Dec 17, 2007 5:49 PM, Kevan Miller <> wrote:
>>> Your interpretation works if your subversion repository is not a
>>> "distribution". IMO, it is and should contain appropriate license/
>>> notice/disclaimer.
> I agree with Kevan.
>> I don't agree with this standpoint as for instance the LICENSE and
>> DISCLAIMER docs can be automatically included into the correct distribution
>> location from officially released bundles. This makes much more sense as it
>> keeps the definition of those documents in one place. This process is
>> repeatable using maven.
>> IMO SVN does not have to mirror an unzipped release (there is no policy
>> directing that, or if there is, please provide a link), as long as it is
>> reproducible from the release tag.
> I have asked about this on the legal discuss list.
> Regardless of the outcome, I think that there are problems with
> generating the NOTICE and LICENSE files automatically. Unless the
> project is pure ASF, there are additional items that may need to be
> added to the N &  L files. In any case, I think it's important that
> these files are carefully considered to ensure that the required
> entries are present. This is difficult if not impossible if the
> contents of the N & L files are automatically generated.
Just to be clear, in the case of UIMA, these files are *not* being
generated (that is, their contents are not being generated) automatically.

The only thing that is happening is that our automated build process for
building the binary and source distributions from our SVN has a step
which copies these files from where they reside in our SVN to the top
level, as required in the distribution.

> The N & L files are unlikely to change frequently, so it really does
> not save much work (if any) to create them by hand. Having them in the
> top-level SVN directory seems sensible to me.
The tools we use for development (Eclipse, mainly) like to have files in
projects; we have adopted an organization where our SVN follows this
convention.  So, for us, it is more convenient to have these files in
SVN inside one of our Eclipse projects, where we can then use the
standard tooling for maintaining them.

>> Martijn
>> --
>> Buy Wicket in Action:
>> Apache Wicket 1.3.0-rc2 is released
>> Get it now:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message