You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Arnaud Bailly <ab...@oqube.com> on 2006/08/18 17:06:55 UTC
Stuck
Hi to all,
This post is a follow up on my previous posts about trying to extend
doxia with a new input format (eg. muse). As suggested by answers to
my questions, I tried to integrate my module directly into doxia,
(trunk version, ie. 1.0-alpha-9-SNAPSHOT). This implied modification
hence recompiling of maven as there is a dependency in maven on
doxia-core, doxia-sink-api and doxia-site-renderer.
Compilation of doxia is ok. With integrated module (ie. in doxia-core/src/main/java/org.../module/muse
as other base formats), the module and parser get instantiated
correctly in plexus.
Compilation of maven is a bit tricky (and long). I had to modify all
references to doxia version. I first tried 2.1-SNAPSHOT but felt back
on 2.0.x branch as the 2.1 version does not output dependency tree
informations with -e -X flags...
Then I recompiled maven-site-plugin with modified doxia dependencies.
When I tried site generation with this setting, I got an error:
[DEBUG] Trace
java.lang.NoClassDefFoundError: org/apache/maven/doxia/sink/SinkFactory
at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateReports(AbstractSiteRenderingMojo.java:555)
at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateDocuments(AbstractSiteRenderingMojo.java:584)
at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
:
Moreover, the sink-api used is not 1.0-alpha-9 but alpha-7 as there
are other dependencies that need this API (project-info-reports). As
correcting this error rwould imply checking all plugins for the doxia
version used, I am the left with the option to hack current release of
doxia.
I think that:
- either I missed something important
- there is a problem as it should not be so complicated to extend a
component when you are using an IoC container.
As said before, any help appreciated.
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Stuck
Posted by Arnaud Bailly <ab...@oqube.com>.
"Vincent Siveton" <vi...@gmail.com> writes:
> Hi Arnaud,
>
> You need to :
> * svn up and install doxia / maven [1] (and delete files in your old M2_HOME)
> * or manually install maven-reporting, doxia-sink-api, and copy all
> generated jar to your $M2_HOME/lib
THat's what I did, but there seems to be some conflicts with plugins
dependencies. I finally did the following:
- modified and installed 1.0-alpha-7
- modified and installed 1.0-alpha-8
- added tracing (ugly System.err :-( I confess ) in my module to
check instanciation
- used plain maven-2.0.4
I finally managed to have my parser invoked, albeit two times: Here is
the full trace of execution (parsing errors are mine). You can notice
that *both* doxia-core-1.0-alpha-8 and alpha-7 are used as my module
is instantiated two times. I tried forcing version with
<dependencyManagement> but did not work.
Have you gon any clue why the "right" module way does not work ? Same
error than DOXIA-68 I think....
regards,
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Stuck
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Arnaud,
You need to :
* svn up and install doxia / maven [1] (and delete files in your old M2_HOME)
* or manually install maven-reporting, doxia-sink-api, and copy all
generated jar to your $M2_HOME/lib
Cheers,
Vincent
[1] http://maven.apache.org/guides/development/guide-building-m2.html,
Building Maven with Maven installed part
2006/8/18, Arnaud Bailly <ab...@oqube.com>:
> Hi to all,
> This post is a follow up on my previous posts about trying to extend
> doxia with a new input format (eg. muse). As suggested by answers to
> my questions, I tried to integrate my module directly into doxia,
> (trunk version, ie. 1.0-alpha-9-SNAPSHOT). This implied modification
> hence recompiling of maven as there is a dependency in maven on
> doxia-core, doxia-sink-api and doxia-site-renderer.
>
> Compilation of doxia is ok. With integrated module (ie. in doxia-core/src/main/java/org.../module/muse
> as other base formats), the module and parser get instantiated
> correctly in plexus.
>
> Compilation of maven is a bit tricky (and long). I had to modify all
> references to doxia version. I first tried 2.1-SNAPSHOT but felt back
> on 2.0.x branch as the 2.1 version does not output dependency tree
> informations with -e -X flags...
>
> Then I recompiled maven-site-plugin with modified doxia dependencies.
>
> When I tried site generation with this setting, I got an error:
> [DEBUG] Trace
> java.lang.NoClassDefFoundError: org/apache/maven/doxia/sink/SinkFactory
> at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateReports(AbstractSiteRenderingMojo.java:555)
> at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateDocuments(AbstractSiteRenderingMojo.java:584)
> at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> :
>
> Moreover, the sink-api used is not 1.0-alpha-9 but alpha-7 as there
> are other dependencies that need this API (project-info-reports). As
> correcting this error rwould imply checking all plugins for the doxia
> version used, I am the left with the option to hack current release of
> doxia.
>
> I think that:
> - either I missed something important
> - there is a problem as it should not be so complicated to extend a
> component when you are using an IoC container.
>
> As said before, any help appreciated.
>
>
> --
> OQube < software engineering \ génie logiciel >
> Arnaud Bailly, Dr.
> \web> http://www.oqube.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org