Kohsuke, Vivek
Thanks for the help on creating a project on java.net and for the future approval of this plugin :)
Unfortunately, I am facing some problems. Everything works fine in a 'client' configuration : java sources are generated and the maven compiler plugin can compile them. This implies that this operation should be bound to a phase before the 'compile' phase of the build lifecycle (for example the generated-sources phase).
This gets complicated with the 'server' configuration : to generate java sources will not work because we need remote interfaces and implementations class files in input to get ties and WSDL :| So we cannot be bound to the generated-sources phase (I have a RMIModeler error about classes not found). If I decide to be bound to the process-classes phase (after the compile phase), generated sources will never be compiled :(
To bypass this, I decided in this case to generate compiled class files with the CompileTool class. And I have classpath problems :)
I think there are two ways of solving this :
1- using the CompileTool class with a correct classpath ;
2- generating sources with the CompileTool class and compile them with the maven compiler plugin. The question is : how to use it (calling it, injecting classpath, environment, etc.) ?
I hope you could help me on the first point. But if you think the second way is better, please let me know :) However that may be, I will keep on searching on this second point.
Eric
> -----Message d'origine-----
> De : Kohsuke Kawaguchi [mailto:Kohsuke.Kawaguchi_at_Sun.COM]
> Envoyé : lundi 20 novembre 2006 23:04
> À : Eric Tournier; Regis Dutertre
> Cc : dev_at_jax-rpc.dev.java.net; Vivek Pandey
> Objet : RE: JAX-RPC Plugin for Maven 2
>
> > Hi Vivek,
> >
> > Thanks for taking time to help :)
> > Could you tell me in details all the steps I have to do
> to build a
> > subproject of JAX-RPC as you suggested (licence, code conventions,
> > naming of the packages, documentation, Maven web site, etc.) ?
> >
> > I will be very glad to join the glassfish project and the JAX-WS
> > community :)
>
> Wonderful!
>
> First you need to create a project on java.net. This is no
> different from any other projects on java.net. You get a
> java.net user id, then start from
> http://www.java.net/request_project.html
>
> Once your project is created, let us know. We know the
> strings to pull :-), so to speak, so we can make that your
> project gets approved in a speedy fashion, and we can also
> move your project under jax-rpc. Beyond that, we can help you
> set up your project, by "installing" various things like
> mailing list auto responder or project role request handler.
>
>
> Since your plugin is really a separate set of code, you can
> use whatever coding convention that you feel comfortable. The
> same goes for license.
> That said, it would make it easier for all of us if we can
> use the Java coding convention [1] and CDDL, just because all
> the glassfish projects do that.
>
> The package name convention for a java.net project is
> "org.jvnet.YOURPROJECTNAME". Don't ask me why, but I recommend that.
>
>
> This should do for now. If you need any help, let us know!
>
>
>
> [1] http://java.sun.com/docs/codeconv/
> --
> Kohsuke Kawaguchi
> Sun Microsystems kohsuke.kawaguchi_at_sun.com
>