On Mar 20, 2007, at 11:52 PM, Brett Porter wrote:

I was under the impression the latest release had updated to qdox and it could deal with it (where it contains annotations, not using them for the mojo parameters themselves obviously).

What version of the plugin plugin are you using, and what version of qdox does it drag in?

I was using 2.2 of m-p-p which appears to be using qdox-1.6.1. I also tried using 2.3-SNAPSHOT (whatever is up there in the m2- snapshot-repo) and it looked like it was using qdox-1.6.1 as well. Both behave the same way.

I've not tried using the 2.3 version which is currently being voted upon.

2.2 looks like its using maven-plugin-tools-java-2.0.5.jar and 2.3/2.3-SNAPSHOT is using maven-plugin-tools-java-2.1.jar. And if I recall this is the component that handles the descriptor extraction for Java mojos. But I could be wrong, been many months since I was digging into plugin descriptor generation fluff.


On 21/03/2007, at 5:48 PM, Jason Dillon wrote:

On a somewhat related note... are there any plans to use annotations for plugin metadata in Maven proper in any time in the nearish future?

I think we'll do that over the course of time, but I doubt it's nearish future. We haven't yet bitten the Java 5 bullet across the board.

I would see it as:
- 2.1 adds toolchain support, making the executing JVM largely irrelevant
- 2.2 adds support for Java 5 features in mojo authoring

Just as a wild stab in the dark.

Okay. I hope that 2.2 comes sooner rather than later. Its getting harder and harder to live with-out Java 5 ;-) And annotations would really be a nice plus for Mojo developers instead of Javadoc tags, so that the Mojo could be inspected at run time for meta-data.

Thanks for the info.

Its starting to look like I'm going to need to craft a custom parser to parse out javadoc tags from *.groovy sources to generate the plugin descriptor... :-|

--jason

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

Reply via email to