He was lookin at the wrong plugin. It wasn't a problem of the pom v3
but the plugin NOT working on maven 2, so no need for a m2 pom
On 3/10/06, Matthew L Daniel <[EMAIL PROTECTED]> wrote:
> > When is the latest edition supporting POM v4.0.0 expected?
>
> I wondered about this as well when I was trying to get the xdoclet2
> maven2 plugin up and running. It would find poms, but they weren't
> Maven2 poms and it was MOST upset.
>
> It was my thought that either M2 take that logical step and say,
> "oh, this is a v3 pom, I'll use the v3 reader"
> or if no one likes that idea, have .pom3, .pom4 etc so when Maven3.14
> ships with its Own Metadata Format(tm), we won't have to ask what
> version your pom is.
>
> I cheat lots: I have an xslt that migrates the v3 to v4 poms. :-)
>
> -- /v\atthew
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
