directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Knecht <fel...@apache.org>
Subject Re: [Studio] Heavy refactoring on Studio's build (was Re: [Studio] Using the Maven Release Plugin)
Date Fri, 26 Sep 2008 09:20:21 GMT
Pierre-Arnaud Marcelot schrieb:
> Hi Felix,
>
> I followed the indications given by David and added the correct files
> to src/main/appended-resources/META-INF to the projects that needed to
> include others licenses and notice informations.
>
> Everything is fine now:
>
>     * The MANIFEST.MF files are now automatically generated by Maven
>       (configuration is taken from the pom).
>     * The META-INF folder has been deleted.
>     * The legal situation is OK.
>
> This is much cleaner than what we had before. :)

A lot cleaner!
Thanks for the heavy work :-)
>
> I'm now going to test if using the release plugin is possible or not.
> I'm confident everything will work now.

I'm sure having it working it will make the release process easier and
handier when having the same release process for all the directory projects.

Thanks
Felix
>
> Regards,
> Pierre-Arnaud
>
> On Thu, Sep 25, 2008 at 5:52 PM, Felix Knecht <felixk@apache.org
> <mailto:felixk@apache.org>> wrote:
>
>     David Jencks schrieb:
>     > I don't know what is in your jars under discussion.
>     >
>     > My understanding of the policies about LICENSE and NOTICE files
>     is that
>     > they apply to what is actually in the artifact (jar in this
>     case) being
>     > distributed.  The DEPENDENCIES file you mention includes information
>     > about stuff that is not included in the artifact but is likely to be
>     > needed to actually use it: this is provided purely as a
>     convenience for
>     > users that want to get a head start on tracking the licenses of
>     these
>     > dependencies.
>     >
>     > So, unless you are actually including in the jar some code under a
>     > different license or that has been contributed to apache with
>     additional
>     > NOTICE requirements then the standard LICENSE and NOTICE files
>     from the
>     > maven remote resources plugin with the latest apache bundle
>     should be fine.
>     >
>
>     Ok. Following this (reasonable) argumentation I'd say the we can
>     remove the META-INF folder on any subproject which
>     doesn't adds the dependency artifact to the jar itself like e.g.
>     the jars subproject.
>
>     For those I suggest to move the specific licenses to a folder
>     {module}/src/licenses and have them added to the
>     jar/META-INF directory using the <resources> tag in the pom.
>
>     WDOT?
>     Felix
>
>


Mime
View raw message