We already have an xml-maven-plugin. So you'd simply add your mojo to that plugin.
If this is a utility in Castor, I suppose I don't have a problem adding it to the castor-maven-plugin. But it really makes the most sense if it lives in a generic "xml" plugin, right? I am just thinking about a new user who is looking for an xml to xsd function... Is he going to look at the Castor plugin for that functionality, or the Xml plugin? Wayne On 8/17/07, Stefano Lenzi <[EMAIL PROTECTED]> wrote: > Wayne Fay wrote: > > Is the castor plugin the right place for this mojo? It sounds like > > more of a generic XML function that might belong to xml-maven-plugin. > > > > Unless there is some castor-specific-ness in the generated XSD, I > > think it should go elsewhere. > > The new goal simply expose a utility available in the Castor suite, > that's way I have added it to castor-maven-plugin, but if you think that > it's better to create a brand new xml-maven-plugin, I'll do that :) > > > > > Wayne > > > > On 8/17/07, Stefano Lenzi <[EMAIL PROTECTED]> wrote: > >> Hi All, > >> > >> I have just developed a new goal for the castor-maven-plugin which take > >> an XML file in input and produce an XML Schema based on it. > >> > >> What do you think? > >> > >> I'll commit the code if I don't get any feedback in the next 2 days :) > >> > >> Ciao, > >> Stefano "Kismet" Lenzi > >> > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
