Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
MIME-Version: 1.0
In-Reply-To: <4D6F6C2C.8090204@adobe.com>
References: <AANLkTi=+fVxT8gp=XcVun+edh2rpKTWpL5ArJgt6e34f@mail.gmail.com>
	<4D6F6C2C.8090204@adobe.com>
Date: Thu, 3 Mar 2011 19:21:29 +0100
Message-ID: <AANLkTikNBGB=z4Pc258-UKeGipPMwYUJBrNvL611Y=jt@mail.gmail.com>
Subject: Re: Is a custom LICENSE.vm needed at all? (was: Re: [VOTE] Release
 chemistry-jar-resource-bundle 0.3.0 (RC1))
From: Gabriele Columbro <gabriele@apache.org>
To: dev@chemistry.apache.org
Cc: Jukka Zitting <jzitting@adobe.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Jukka,
thanks for the clear answer.

On Thu, Mar 3, 2011 at 11:23 AM, Jukka Zitting <jzitting@adobe.com> wrote:
> Hi,
>
> On 03/02/2011 07:05 PM, Gabriele Columbro wrote:
>>
>> Technically speaking, the way we add it to the packages is the proper
>> one I believe (using the maven-shared-resources-plugin just as any
>> Maven ASF artifact).
>
> The main idea behind it is that all release packages should have a LICENS=
E
> file that includes or at least references the license terms of all IP
> included in that package.
>
> Thus we need to include such extra notes only in jars or other packages t=
hat
> include bits that are under other licenses than the ALv2. Most notably Ma=
ven
> dependencies need only be mentioned in the LICENSE file if the build embe=
ds
> the dependencies in the resulting build artifact like is done for example=
 in
> the dist and webapp packages.

I will then implement that for:
- All the WARs (referencing the META-INF/DEPENDENCIES file)
- All the commodity packages including 3rd party JARs (referencing the
root level DEPENDENCIES file)

I don't think we need anything specific then for the JARs since they
do not package anything external.

>
>> Yes having it SVN would be easy. Maybe not in the LICENSE file. In the
>> README would work?
>
> All licensing information should be in the LICENSE file. The best place t=
o
> put such notes is in src/main/appended-resources/META-INF/LICENSE for jar
> archives and in the appropriate other locations for other kinds of archiv=
es.
>
> Using a shared resource bundle for this is useful if you'd otherwise end =
up
> duplicating the same information too many times, but it's probably not wo=
rth
> the extra complexity for eliminating just a few duplicates.

I agree with this approach. I reopened
https://issues.apache.org/jira/browse/CMIS-325 to work on this,
and should be fairly easy to single source those few lines under the
parent project (since we already have a parentBasedir property in all
POMs).

>
>> I'm wondering how other ASF projects (with external dependencies) do.
>
> See [1] and [2] for how this is done in Jackrabbit for jar and war archiv=
es.
> There we explicitly include all the licenses of embedded external
> components, but also just a reference to the relevant license terms would=
 be
> OK.
>
> [1]
> http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-spi-commons/s=
rc/main/appended-resources/META-INF/LICENSE
> [2]
> http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-webapp/src/ma=
in/webapp/META-INF/LICENSE

Thanks for the pointers!

Keep you posted,
Gab


>
> --
> Jukka Zitting
>


--=20
Eng. Gabriele Columbro
Open source and ECM Architect
Alfresco Ltd. - http://www.alfresco.com
-----------------------------------------
http://twitter.com/#!/mindthegabz
-----------------------------------------
"Keyboard not found.
=A0Press F1 to continue"
----------------------------------------