[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] XDoclet plugin
|
The mapping looks right and m2e is expected to execute
maven2-xdoclet2-plugin as part of workspace build. If you don't see
anything relevant/interesting in m2e log file
.metadata/.plugins/org.eclipse.m2e.logback.configuration/0.log, please
open bugreport in m2e bugzilla and provide complete standalone sample
project and steps to reproduce the problem.
Beware that m2e is not expected to refresh workspace from filesystem, so
resources generated by xdoclet will not be visible until you do this
manually.
As a side note, I am almost certain this maven2-xdoclet2-plugin leaks
classloaders, so don't complain when your eclipse instance crashes with
OOME.
--
Regards,
Igor
On 11-06-16 5:04 PM, Vincent Vandenschrick wrote:
Hi all,
I'm trying hard to migrate from 0.12.1 to 1.0.0 ;-)
As of now, everything is almost working except one "little" thing I
can't explain :
I can't figure out why the XDoclet plugin is not triggered during the
Eclipse build. I've applied the exact same configuration than for the
other plugins I want to trigger and whose lifecycle is not covered by
m2e (nor any extension), i.e. :
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.codehaus.xdoclet</groupId>
<artifactId>maven2-xdoclet2-plugin</artifactId>
<versionRange>[2.0.7,)</versionRange>
<goals>
<goal>xdoclet</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute/>
</action>
</pluginExecution>
However, no XDoclet generation happens and I couldn't find a way to
activate a "debug" mode in the Maven console view to investigate further.
The other plugins I've configured this way fire correctly during the
Eclipse build.
As a side note, The XDoclet plugin execution is attached to the
generate-resources phase of my project, but I don't think it has any
influence on the new M2E build lifecycle, right ?
Thanks for your insights,
Vincent
