Brett Porter wrote:
In that case, you need to do something like:
<maven:get plugin="maven-xdoclet-plugin" var="xdocletPlugin"
property="plugin" />
${xdocletPlugin.getDependencyPath('...')}

Hmm, I've never seen this before. I gave it a shot and nothing echo'ed.

OH, hold on. The maven xdoclet plugin was not installed correctly. I just fixed that and I did get an echo output. It said "Maven XDoclet Plug-in".


I'm still getting the error: "taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found" though which means it hasn't added maven-xdoclet-plugin's dependencies.
I did the following echo:
<echo message="${xdocletPlugin.getDependencyPath('xdoclet')}"/>
and I got: "/Volumes/scratch/SmileyDev/Maven Repository/xdoclet/jars/xdoclet-1.2.jar"
That is promissing. Then I tried something different: <echo message="${xdocletPlugin.getDependencyPath('maven-xdoclet-plugin')}"/>
and I got nothing.



Maybe xdoclet-plugin is not initialised yet.

Hmm, didn't know about that. Though since I got the echo above to output, perhaps it's initialized since I figure that very text came from the plugin somewhere.


This needs to meet one of
the following conditions:
- be in a preGoal on an xdoclet goal
- have an xdoclet goal as a prereq
- utilise a tag library from xdoclet somewhere in maven.xml (if it has
one to use)

I use the ejbdoclet ant tag (part of xdoclet) following my taskdef; so perhaps that qualifies as your 3rd option. I don't want to actually attain any xdoclet plugin goals, I just want to piggy-back off of its project.xml dependencies. Are you sure using an xdoclet ant tag would cause the xdoclet plugin to be initialized? I don't see how that would happen.



 I also tried with maven:pluginVar since maven:get is actually
deprecated according to the docs.  When I enable the -X switch, there is


wrong way around... pluginVar is deprecated. where did you see that?

Oh, I mixed up which replaced which. My bad.


no extra information to help diagnose this.  It would be nice if there
was some debugging information whenever the pattern  ${a.b()} appears so
that I at least know that Maven is trying to evaluate it as a function
and not a direct variable.


You'd drown in the output :)


~ Dave


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to