On Wed, 2007-12-19 at 20:55 -0500, Leonardo Uribe wrote:
> Hi
>
> I have done the release procedure again including
>
> <groupId>org.apache.myfaces.trinidadbuild</groupId>
> <artifactId>maven-plugin-parent</artifactId>
>
> For resolve MYFACES-1790 and moved LICENSE and NOTICE to META-INF
> folder for both myfaces api and impl.
The convention used in apache commons is that each module has a
LICENSE.txt and NOTICE.txt file in its root directory, ie next to the
pom.xml file and then they are output into the jar using a resource
definition in the pom:
<resource>
<directory>.</directory>
<targetPath>META-INF</targetPath>
<includes>
<include>NOTICE.txt</include>
<include>LICENSE.txt</include>
</includes>
</resource>
This means that people who check out the code (or browse the repository
online) see the LICENSE and NOTICE in the obvious place (first dir that
anyone sees), but the jar has it in *its* obvious place (with the rest
of the jar meta-data). Having the NOTICE in the module root dir also
means developers are more likely to keep it up-to-date if adding code
with special license conditions.
I would highly recommend using this approach for myfaces too. But it's
not a release-blocker IMO, as the license/notice *are* in svn and in the
jar.
As it happens, there is quite a vigorous discussion going on right now
in both apache commons and legal-discuss lists regarding NOTICE and
LICENSE files. Some people would like to use a maven feature to
auto-generate LICENSE and NOTICE files. This is quite controversial,
though, and a number of people prefer the existing apache-commons way
(including myself).
Regards,
Simon
