Niall Pemberton wrote:
On Jan 8, 2008 7:12 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On Jan 8, 2008 6:49 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
On Jan 8, 2008 4:19 PM, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
On Jan 8, 2008 12:11 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
Sorry, if I am coming up with this question so late. Nevertheless:
Does the current parent pom deal with adding NOTICE.txt and
LICENSE.txt to the javadoc jar files?
No - but AIUI it doesn't need to since it only contains the generated
javadoc and not anything we develop.
I'll be more than happy if we'll be able to get rid of that policy.
Nevertheless it is what I was forced to do for releases of
commons-fileupload and commons-io in the past. And, AFAIK, it is
automatically enforced by the maven-remote-resources-plugin.
Actually remote resourcs doesn't.
Actually it does. maven-remote-resources-plugin places the remotely
fetched resources in a special directory. These resources are then
included into the created jar file by maven-javadoc-plugin and
maven-source-plugin.
Well I tried it and it didn't.
Apologies - I just tried specifying the latest javadoc plugin version
(2.3) and it worked. I'm just wondering why the javadoc jar plugin
doesn't also do the "local" resources as well?
You normally don't want the javadoc-plugin to include your normal
resources, the ones that end up in target/classes during the build. You
can however tell the javadoc-plugin to use special javadoc resources if
you want to:
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/javadoc-resources.html
Niall
Niall
Niall
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
