On Tuesday 20 February 2007 15:11, Wayne Fay wrote:
> I don't disagree that this is probably a solution for his problem, but
> I do feel it is reasonable to expect that such files will end up in
> all artifact packages (compiled jar, source, javadoc), and so I
> believe this should be filed as a bug.

Oh, definitely.   It's a bug and should be filed, fixed, etc...   No arguement 
there.

However, filing a bug is not likely to yield a "fix" in the next week or two 
at least, and even then, probably in a SNAPSHOT form.  I just wanted to 
propose an alternative that could possibly work with what's released today.

For some people, a bird in the hand is worth more than two in some future 
bush.   :-)

Enjoy!
Dan


>
> Wayne
>
> On 2/20/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> > Matthias,
> >
> > On Tuesday 20 February 2007 04:37, Matthias Wessendorf wrote:
> > > I have the following files:
> > > -notice.txt
> > > -license.txt
> > >
> > > inside of:
> > > $PROJECT/src/main/resources/META-INF
> > >
> > > They are in the meta-inf folder of the -sources JAR, but not inside
> > > the -javadoc jar
> > > Any ideas ?
> >
> > One option may be to use the maven-remote-resources-plugin to create the
> > NOTICE/LICENSE files.   If you package your license and notice files in a
> > remote resource bundle, and then use the remote-resources plugin to
> > unpack/include them, the javadoc plugin will automatically pick them up
> > and include them.
> >
> > Docs at:
> > http://maven.apache.org/plugins/maven-remote-resources-plugin/
> > (1.0-alpha-2 was just released to the apache repository an hour or so
> > ago. Wait a few hours for it to sync to central then to the mirrors)
> >
> > An example would be:
> > <plugin>
> >    <artifactId>maven-remote-resources-plugin</artifactId>
> >    <version>1.0-alpha-2</version>
> >    <executions>
> >        <execution>
> >            <goals>
> >                <goal>process</goal>
> >            </goals>
> >            <configuration>
> >                <resourceBundles>
> > <resourceBundle>org.apache:apache-jar-resource-bundle:1.1</resourceBundle
> >>
> > <resourceBundle>org.apache:apache-incubator-disclaimer-resource-bundle:1.
> >0</resourceBundle> </resourceBundles>
> >                <properties>
> >                    <addLicense>true</addLicense>
> >                </properties>
> >            </configuration>
> >        </execution>
> >    </executions>
> > </plugin>
> >
> > That fragment will add the Apache license, the Apache incubator
> > disclaimer, and a NOTICE file created from all the dependencies
> > (including the License URL for each when available) into all the jars
> > (source, javadoc, and the actual jar).    If that's in the "parent" pom,
> > ALL the jars would get it.
> >
> > Anyway, that is now how all the maven plugins and other maven parts do
> > the LICENSE/NOTICE.
> >
> > Enjoy!
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727    C: 508-380-7194
> > [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]

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to