I am very pragmatic when it comes to Maven, since not everything works
as you might expect.
I'd add it to your plugin dependency directly, file a bug report,
watch the bug, and when it is eventually resolved, remove the plugin
dependency.
Wayne
On 3/19/06, Subhash Chandran <[EMAIL PROTECTED]> w
Adding it to my dependency will not work. My application compile classpath
will not be available to the javancss plugin. Yes, I can add it to the
javancss maven plugin pom.xml. But if the same is done by the maintainers of
javancss maven plugin, it will benefit all.
While writing this mail, I sear
add jaxen as a dependency to your pom
or directly to the plugin itself
jaxen
jaxen
1.1-beta-8
compile
Wayne
On 3/19/06, Subhash Chandran <[EMAIL PROTECTED]> wrote:
> My pom.xml has:
>
>
> org.codehaus.mojo
> javancss-maven-plugin
> 2
My pom.xml has:
org.codehaus.mojo
javancss-maven-plugin
2.0-alpha1-SNAPSHOT
I get this Exception when running this report:
[INFO] Generate "JavaNCSS Report" report.
[INFO]
[ERROR] FATAL E
