Incorrect license metadata after inheriting org.apache:apache:6

[Jukka Zitting]

Hi,

In Jackrabbit we recently upgraded to the org.apache:apache:6 parent
POM to get the latest repository.apache.org settings, but as a
side-effect we started getting extra LICENSE, NOTICE, and DEPENDENCIES
files in the META-INF directories of our jar artifacts.

This would be nice if the included license metadata was correct, but
unfortunately it is not at least in our case. For example, we have
many components where we're including external code snippets with
separate licenses or copyright notice requirements.

We already include our own custom license metadata files in the jar
artifacts and it's confusing to have the remote resources plugin add
these extra files. To avoid this confusion, is there some way (apart
from not using org.apache:apache:6) for us to either disable the
inclusion of these extra files or customize the files to match our
needs?

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[djencks]

These are added by the maven-remote-resources-plugin and you can  
customize the output using per-project velocity templates in src/main/
appended-resources/META-INF/ to add stuff to the basic LICENSE and  
NOTICE files. The plugin docs have more instructions.  I think I saw  
that someone figured out how to not include the DEPENDENCIES file but  
I don't know what they did.


thanks
david jencks

On Jul 2, 2009, at 4:13 AM, Jukka Zitting wrote:

> Hi,
>
> In Jackrabbit we recently upgraded to the org.apache:apache:6 parent
> POM to get the latest repository.apache.org settings, but as a
> side-effect we started getting extra LICENSE, NOTICE, and DEPENDENCIES
> files in the META-INF directories of our jar artifacts.
>
> This would be nice if the included license metadata was correct, but
> unfortunately it is not at least in our case. For example, we have
> many components where we're including external code snippets with
> separate licenses or copyright notice requirements.
>
> We already include our own custom license metadata files in the jar
> artifacts and it's confusing to have the remote resources plugin add
> these extra files. To avoid this confusion, is there some way (apart
> from not using org.apache:apache:6) for us to either disable the
> inclusion of these extra files or customize the files to match our
> needs?
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jukka Zitting]

Hi,

On Thu, Jul 2, 2009 at 8:16 PM, David Jencks<david_jencks@...> wrote:
> These are added by the maven-remote-resources-plugin and you can customize
> the output using per-project velocity templates in
> src/main/appended-resources/META-INF/ to add stuff to the basic LICENSE and
> NOTICE files. The plugin docs have more instructions.

Thanks, I'll try that. Looking at the docs I also found the
<skip>true</skip> option that gives me a plan B.

BTW, the copyright year in the NOTICE file should (AFAIK) be the year
of publication of the compilation (e.g. the jar artifact) instead of
the range of years of during which the contents of the compilation
have been authored. Where should I file an issue for this?

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jukka Zitting]

Hi,

On Fri, Jul 3, 2009 at 10:21 AM, Jukka Zitting<jukka.zitting@...> wrote:
> BTW, the copyright year in the NOTICE file should (AFAIK) be the year
> of publication of the compilation (e.g. the jar artifact) instead of
> the range of years of during which the contents of the compilation
> have been authored. Where should I file an issue for this?

I couldn't find an appropriate issue tracker, so see below for the
proposed patch (against apache-jar-resource-bundle).

BR,

Jukka Zitting


Index: src/main/resources/META-INF/NOTICE.vm
===================================================================
--- src/main/resources/META-INF/NOTICE.vm (Revision 790822)
+++ src/main/resources/META-INF/NOTICE.vm (Arbeitskopie)
@@ -21,7 +21,7 @@

 #if ($projectName)$projectName#else${project.name}#end

-Copyright ${projectTimespan}#if($project.organization.name)
$project.organization.name#else The Apache Software Foundation#end
+Copyright ${presentYear}#if($project.organization.name)
$project.organization.name#else The Apache Software Foundation#end


 This product includes software developed at

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[dkulp]

I'm not sure I agree with this change.   Why should it just be the present
year?   If the jar contains schemas or other works that are copyright over the
entire range, why would it NOT be the full range?

Dan


On Tue July 7 2009 11:15:23 am Jukka Zitting wrote:
> Hi,
>
> On Fri, Jul 3, 2009 at 10:21 AM, Jukka Zitting<jukka.zitting@...>
wrote:

> > BTW, the copyright year in the NOTICE file should (AFAIK) be the year
> > of publication of the compilation (e.g. the jar artifact) instead of
> > the range of years of during which the contents of the compilation
> > have been authored. Where should I file an issue for this?
>
> I couldn't find an appropriate issue tracker, so see below for the
> proposed patch (against apache-jar-resource-bundle).
>
> BR,
>
> Jukka Zitting
>
>
> Index: src/main/resources/META-INF/NOTICE.vm
> ===================================================================
> --- src/main/resources/META-INF/NOTICE.vm (Revision 790822)
> +++ src/main/resources/META-INF/NOTICE.vm (Arbeitskopie)
> @@ -21,7 +21,7 @@
>
>  #if ($projectName)$projectName#else${project.name}#end
>
> -Copyright ${projectTimespan}#if($project.organization.name)
> $project.organization.name#else The Apache Software Foundation#end
> +Copyright ${presentYear}#if($project.organization.name)
> $project.organization.name#else The Apache Software Foundation#end
>
>
>  This product includes software developed at
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[dkulp]

On Tue July 7 2009 11:22:38 am Daniel Kulp wrote:
> I'm not sure I agree with this change.   Why should it just be the present
> year?   If the jar contains schemas or other works that are copyright over
> the entire range, why would it NOT be the full range?

The text on the apache legal page states:
http://www.apache.org/legal/src-headers.html#notice

The top of each NOTICE file should include the following text, suitably
modified to reflect the product name and year(s) of distribution of the
current and past versions of the product:

          Apache [PRODUCT_NAME]
          Copyright [yyyy] The Apache Software Foundation

Note it specifically says "year(s)".

Also, the sample notice file linked to from there:
http://www.apache.org/licenses/example-NOTICE.txt
specifically uses a range:

   Apache HTTP Server
   Copyright 1999-2006 The Apache Software Foundation

Thus, I think the current version is correct.

Dan

>
> Dan
>
> On Tue July 7 2009 11:15:23 am Jukka Zitting wrote:
> > Hi,
> >
> > On Fri, Jul 3, 2009 at 10:21 AM, Jukka Zitting<jukka.zitting@...>
>
> wrote:
> > > BTW, the copyright year in the NOTICE file should (AFAIK) be the year
> > > of publication of the compilation (e.g. the jar artifact) instead of
> > > the range of years of during which the contents of the compilation
> > > have been authored. Where should I file an issue for this?
> >
> > I couldn't find an appropriate issue tracker, so see below for the
> > proposed patch (against apache-jar-resource-bundle).
> >
> > BR,
> >
> > Jukka Zitting
> >
> >
> > Index: src/main/resources/META-INF/NOTICE.vm
> > ===================================================================
> > --- src/main/resources/META-INF/NOTICE.vm (Revision 790822)
> > +++ src/main/resources/META-INF/NOTICE.vm (Arbeitskopie)
> > @@ -21,7 +21,7 @@
> >
> >  #if ($projectName)$projectName#else${project.name}#end
> >
> > -Copyright ${projectTimespan}#if($project.organization.name)
> > $project.organization.name#else The Apache Software Foundation#end
> > +Copyright ${presentYear}#if($project.organization.name)
> > $project.organization.name#else The Apache Software Foundation#end
> >
> >
> >  This product includes software developed at
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@...
> > For additional commands, e-mail: dev-help@...

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Jukka Zitting]

Hi,

On Tue, Jul 7, 2009 at 5:42 PM, Daniel Kulp<dkulp@...> wrote:

> The text on the apache legal page states:
> http://www.apache.org/legal/src-headers.html#notice
>
> The top of each NOTICE file should include the following text, suitably
> modified to reflect the product name and year(s) of distribution of the
> current and past versions of the product:
>
>          Apache [PRODUCT_NAME]
>          Copyright [yyyy] The Apache Software Foundation
>
> Note it specifically says "year(s)".

Good point, though I still think it's incorrect. :-) I'm engaging
legal-discuss@ to know for sure.

> Thus, I think the current version is correct.

Agreed. I'll get back to this in case the status quo changes.

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...