Doing
<resources>
<resource>
<includes>
<include>NOTICE.txt</include>
</includes>
</resource>
</resources>
in the <build> kind of works. You get a NOTICE.txt in the jar, but it's
not in the META-INF as the LICENSE.txt is.
Is this important? Anyone got smart ideas for a fix?
Hen
On Fri, 27 Feb 2004, Henri Yandell wrote:
>
> I tell if something has been ASF2.0-ised based on whether the LICENSE.txt
> in the top directory is 2.0 or 1.1.
>
> So a simple grep should be able to tell. As Stephen's pointed out, I've
> neglected to put NOTICE.txt's in place and they need to go into the jars
> [maven <resource> I presume].
>
> Hen
>
> On Fri, 27 Feb 2004, matthew.hawthorne wrote:
>
> > Henri Yandell wrote:
> > > Will start doing so tonight. I estimate more than 5 minutes :)
> > >
> > > relicence
> > > new licence.txt
> > > new notice.txt
> > > include notice in jar
> > > build each component
> > > cvs ci
> >
> >
> > Can someone post the script used to change the licenses in source files?
> > I think Stephen
> > posted it originally. Better yet, could somebody just place it in their
> > ~/public_html dir so it's
> > easy for anyone to access?
> >
> > Also, is there a list somewhere of which commons components have been
> > re-licensed? Maybe
> > we could make a small HTML page somewhere.
> >
> > Thanks.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
