Hi Jason
You're quite right about the surrogate parent. I had seen the commits
about it but didn't connect it with the circular dependency problem.
Thanks for clearing that up.
Now, the only error left is about the missing examples. I'll leave the
decision about that up to you.
--
Dennis Lundberg
Jason van Zyl wrote:
Hi Denis,
Just did a little checking. The JXR/Javadoc are not added automatically
as it causes the cycle problem. So that's what the surrogate plugin
parent POM is and it has a profile for reporting. So if you use
-Preporting you'll get the reports.
Jason.
On 30 Nov 06, at 2:15 PM 30 Nov 06, Dennis Lundberg wrote:
The Remote Resources Plugin does not pass the DOCCK check:
The following documentation problems were found:
o Maven Remote Resources Plugin (5 errors, 0 warnings)
[ERROR] pom.xml is missing the <prerequisites> tag.
[ERROR] pom.xml has no report plugins configured.
[ERROR] pom.xml is missing the report plugin:
maven-javadoc-plugin.
[ERROR] pom.xml is missing the report plugin: maven-jxr-plugin.
[ERROR] There are no example files in your site directory (in
html|xml|apt format). They should either be called "example*.(
html|xml|apt)" or they should be located in the "examples" directory
--Dennis Lundberg
Jason van Zyl wrote:
Hi,
This is a group release to attempt to deal with the licensing
resources that need to be packaged up in all the archives we
distribute. This is, in particular, and attempt to deal with the JARs
we release. Namely the binary, source, and javadoc JARs we create
with the JAR, Source, and JavaDoc plugins respectively.
I have created the Remote Resources Plugin which is documented here:
http://people.apache.org/~jvanzyl/maven-remote-resources-plugin/
And I have created a diagram of the process that is currently
happening as a result of the changes I have made to the Source, and
JavaDoc plugins:
http://idisk.maven.org/jvanzyl/Public/RemoteResourcesHandling.png
Essentially the remote resources plugins creates a directory of
resources and modifies the POM at runtime so it carries with it the
information about this directory. The other archiving plugins then
look for this resource and insert it into the archives they create if
found. Ideally the Resource element should have a unique id but the
directory name will do for now.
You can see here that I've created a profile which will enable the
remote resources plugins and pull down the bundle that contains the
standard license and notice files:
http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml
And I have deployed all the plugins above with this tool chain so you
can see them here:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-remote-resources-plugin/1.0-SNAPSHOT/
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-source-plugin/2.0.2-SNAPSHOT/
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-javadoc-plugin/2.2-SNAPSHOT/
If I can release these plugins then I think we can solve most of the
licensing/resource doldrums.
Jason.
---------------------------------------------------------------------
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]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
