Ok, that sounds sensible. Shouldn't the new version of the plugin include a prerequisites tag, pointing to the correct version of Maven?
(from the message of Brett, maybe this is still under work). Thx for the info kenney, and my apologies from wrongly accusing your patch. Denis. forge wrote: > > > > Cabasson Denis wrote: >> Hum, after futher investigation, no need to go that deep in changes. >> >> Simply running mvn site on any project results in this class not found >> thingy (after having built the latest maven-site-plugin of course). > > Hi, > > You'll either need to bootstrap maven entirely, or manually mvn package > maven-reporting(-api|-impl), doxia-sink-api, and copy the target/*.jar > to $M2_HOME/lib/ (removing the old versions). > > -- Kenney > >> >> Isn't there any integration test for maven site plugin? :( >> >> Denis. >> >>> -----Message d'origine----- >>> De : Cabasson Denis [mailto:[EMAIL PROTECTED] >>> Envoyé : vendredi 11 août 2006 13:06 >>> À : Maven Developers List >>> Objet : RE: svn commit: r430446 - in >>> /maven/plugins/trunk/maven-site-plug in: pom.xml >>> src/main/java/org/apache/maven/plugins/site/ReportDocumentRen >>> derer.java >>> >>> Hi Kenney, >>> >>> Your stuff looks nice, but it seems to be broken :( Well, at >>> list, I can't use it (which is not completly the same thing). >>> >>> I'm trying to build a new Report, using your new >>> AbstractMavenReport. When writing down my report, everything >>> is fine. I the lauch a mvn install and it's installed to my >>> local repo. >>> >>> I then bind it to the reporting section of a integration-test pom. >>> Then when executing mvn site on this integration, it fails with: >>> java.lang.NoClassDefFoundError: >>> org/apache/maven/doxia/sink/SinkFactory >>> >>> Which means new doxia-sink-api (version 1.0-alpha-9-SNAPSHOT) >>> hasn't been loaded. >>> >>> It is declared in the maven-site-plugin as a dependency >>> (transitive one), but I can't be found at runtime. >>> I really don't understand what's happening. >>> >>> I'm working on modello-maven-plugin. >>> Here is the patch (including the integration test) I'm trying to run: >>> http://dcabasson.developpez.com/maven/MODELLO-site-problem.patch >>> >>> Just apply this patch to the current version of >>> modello-mave-plugin, install the plugin, and launch mvn site >>> on the integration-test. >>> >>> Sorry for being so thick about that. >>> >>> Denis. >>> >>>> -----Message d'origine----- >>>> De : Kenney Westerhof [mailto:[EMAIL PROTECTED] Envoyé : >>> vendredi 11 août >>>> 2006 01:41 À : Maven Developers List Objet : Re: svn >>> commit: r430446 - >>>> in >>>> /maven/plugins/trunk/maven-site-plugin: pom.xml >>>> src/main/java/org/apache/maven/plugins/site/ReportDocumentRend >>>> erer.java >>>> >>>> >>>> >>>> Brett Porter wrote: >>>>> On 11/08/2006 3:20 AM, [EMAIL PROTECTED] wrote: >>>>>> Modified: maven/plugins/trunk/maven-site-plugin/pom.xml >>>>>> URL: >>>>>> >>> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/po >>>>>> m.xml?rev=430446&r1=430445&r2=430446&view=diff >>>>>> >>>>>> >>> ===================================================================== >>>>>> ========= >>>>>> >>>>>> --- maven/plugins/trunk/maven-site-plugin/pom.xml (original) >>>>>> +++ maven/plugins/trunk/maven-site-plugin/pom.xml Thu Aug >>>> 10 10:20:32 >>>>>> 2006 >>>>>> @@ -79,7 +79,7 @@ >>>>>> <dependency> >>>>>> <groupId>org.apache.maven.reporting</groupId> >>>>>> <artifactId>maven-reporting-api</artifactId> >>>>>> - <version>2.0.2</version> >>>>>> + <version>2.1-SNAPSHOT</version> >>>>>> </dependency> >>>>>> <dependency> >>>>>> <groupId>org.codehaus.plexus</groupId> >>>>> This will block a release of the site plugin until after >>> Maven 2.1, >>>>> which is not desirable. >>>> I know. I've posted a mail on this about 7 mails up in the >>> dev list.. >>>> >>>>> Two questions: >>>>> a) does this change actually make it always require Maven >>>> 2.1, or is >>>>> it only if you use the multi page feature that will trigger >>>> the code? >>>> >>>> Only the latter, actually. But at runtime it will still require the >>>> new code in the maven-reporting-api. >>>> >>>>> b) can we create a branch for it anyway? >>>> A branch for what, exactly? >>>> >>>>> I think the answer to a) is that it does, so it needs a >>>>> <prerequisites> element, and it also makes b) a must for now. >>>> Please take a look at the full problem description in the >>> other mail. >>>> Maybe we've got a bigger design issue here.. >>>> >>>> -- Kenney >>>> >>>> >>>>> Cheers, >>>>> Brett >>>>> >>>>> >>> --------------------------------------------------------------------- >>>>> 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] > > > -- View this message in context: http://www.nabble.com/RE%3A-svn-commit%3A-r430446---in--maven-plugins-trunk-maven-site-plug-in%3A-pom.xml-src-main-java-org-apache-maven-plugins-site-ReportDocumentRe-n-derer.java-tf2090126.html#a5764155 Sent from the Apache Maven Developers List forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
