Jonathan Johnson wrote:
> Kohsuke,
>
> Yes, start simple and grow the features as needed. The Ant JAXB features
> are a good guideline
> (http://java.sun.com/webservices/docs/1.6/jaxb/ant.html) for Mavenizing. As
> you suggested using com.sun.tools.xjc.XJC2Task would be best since it builds
> on the ant experience, eases the transition from ant and adapts to future
> needs.
I then realized that you'd probably want to take some of the values from
Maven project setting --- such as where to place generated source files.
So perhaps instead of just copying XML, your plugin would probably want
to do additional configuration.
> Thanks for the CVS access. I'm new to contributing to open source. Can you
> point me to the guidelines and standards for create and submitting code.
There's not so much of "guideline and standards". You can just take it
easy and start writing code, and we can adjust as we go along :-)
If you are going to help an existing code, that usually calls for more
"guidelines and standards", but since this plugin is from scratch, it's
more like what you do will decide guidelines.
> What java version is the target?
Since JAXB2 itself requires Tiger, there's no point in not using Tiger
features, I think.
> Do I create a build.xml as well (no pom.xml) ;-(? Etc..
Since you are writing a plugin for Maven2, there's no reason not to use
Maven2 as the build system. That would probably be the easiest, as Maven
defines all sorts of goals for developing plugins.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com