On 17 Dec 06, at 10:27 AM 17 Dec 06, Kenney Westerhof wrote:
Yes - built from trunk. The jar includes it. But see below:
Now for some of the new classworlds magic! :-) Don't be frightened :-)
which is to be expected. Too bad this doesn't work, since all
reporting plugins are really
plugins for the site plugin and should be in a sub-realm of the
site plugin.
The reporting-api from the m2 installation is used, not the site
one, so this is fine.
The noClassDef is from the report plugin, not from site plugin
(should've made that clearer).
Ok, I can sort this out but really it's only 2.0.4 I care about right
now.
Will 2.0.5 include the new maven-reporting-api?
(mvn site takes 11 seconds)
With maven 2.1-SNAPSHOT I get:
(btw mvn site takes about 4 minutes since it pings all snapshot
repos multiple
times for each artifact)
Caused by:
org.codehaus.plexus.util.xml.pull.XmlPullParserException:
expected START_TAG or END_TAG not TEXT
(position: TEXT seen ...<menu ref="reports"/>\n\n\t\t[]\n
</... @35:5)
My site.xml only includes ${reports} and ${modules}, not the new-
style <menu ref/>.
Ok, I can swap whatever is necessary.
In the site plugin we are looking for those old references and
changing them to the new.
[snip]
The '[]' is the problem. This is on the exact location of the
original ${modules} tag, so that one needs fixing.
Sure, you want to JIRA that for 2.0, I pushed all the issues off
to 2.0.1 but I'll fix those couple things and release doxia and
call the rest can wait until 2.0.1.
Ok will do - this has to be fixed before the next release, since it
used to work.
Agreed. Maybe snag your site that you used and we'll turn it into an
integration test.
jason.
Jason.
-- Kenney
Jason van Zyl wrote:
The maven-site-plugin should be good now.
Jason.
On 17 Dec 06, at 8:16 AM 17 Dec 06, Kenney Westerhof wrote:
Hi Jason,
In trunk, I'm finding 2 maven-site-plugin dirs: maven-site-plugin
and maven-site-plugin-with-compat-for-2.0.4
There are lots of changes between these two - almost all files
are different (mostly license headers).
Which version is the right one? Which one will be merged to the
other?
Shouldn't the maven-site-plugin-with-compat-for-2.0.4 be in
branches/?
-- Kenney
Jason van Zyl wrote:
Hi,
I have managed to get the site plugin working with 2.0.4 and
it really wasn't a simple matter of rolling back some stuff.
In order for the site plugin to work with 2.0.4 the version of
doxia that is in MAVEN_HOME/lib must be used which is
doxia-1.0-alpha-7. The version of doxia in trunk is not very
much like 1.0-alpha-7 at all and creating a bridge required a
compat package with bits from maven-reporting, doxia-core,
doxia-site-renderer, doxia-document-render. Maybe I'm missing
something but I don't see how what's in trunk could work at
all as there are so many class that are different with methods
removed, or classes not present in doxia-1.0-alpha-7. Another
problem was relying on some changes in plexus-utils that are
not available in the version used in 2.0.4
I have created a tag in svn that marks the point right before
I created the bridge for reverting if something is wrong here:
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-site-
plugin-pre-compat-with-doxia-1.0-alpha-7/ I have created some
notes about the compatibility here:
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-
plugin/compatibility-notes.txt I have checked in what I have
that makes it work for the /maven/components site generation
and I have deployed a snapshot that people can try:
http://people.apache.org/repo/m2-snapshot-repository/org/
apache/maven/plugins/maven-site-plugin/2.0-SNAPSHOT/ So for
that poor fellow who was trying to jump through rings of fire
to generate his sites, this one's for you :-)
Thanks,
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]
--------------------------------------------------------------------
-
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
