>
> Well, one issue is that we don't use maven to generate the site.   Thus,
> putting javadoc on there would be irrelevant.  :-)
>
> In all seriousness, patches would be most welcome, both for the code but
> also
> for the docs on the site:
> http://cwiki.apache.org/CXF20DOC/maven-integration-and-plugin.html
>

Not using maven to generate the doc is not an issue, and as the plugin
mostly uses nested types (Option) to configure the maven generated doc would
not be very usefull. So any user that want to know plugin parameters will
have
1. To discover what's the underlying class (some link to javadoc in wiki
would be great)
2. To analyze the Option attributes as the're is no javadoc

Link to the wsdl-to-java page just help to discover parameters, but is not
very user-friendly

I can help by posting a patch about javadoc,

I'd be pleased to contribute the wiki documentation, but have no write
permission on it (my apache wiki ID is "nicolas").



>
> Dan
>
>
> >
> > Cheers,
> > Nicolas
> >
> > On Mon, Mar 9, 2009 at 5:55 PM, Daniel Kulp <[email protected]> wrote:
> > > On Mon March 9 2009 10:24:10 am nicolas de loof wrote:
> > > > Hi,
> > > > any chance to get CXF-1997 fixed ?
> > > > This may look only a "who cares" issue, but as I'm writing a book on
> > >
> > > maven
> > >
> > > > and would like to use CXF in my samples, I'd prefer to have "best of
> > >
> > > bread"
> > >
> > > > plugins as samples :-)
> > >
> > > I'll update this later today for 2.2.   I'm not going to back port this
> > > to 2.1.x as I'm not really sure what impact this would have on existing
> > > people.
> > > You never know what wacky things people are doing with the generated
> > > code.
> > >
> > > :-)
> > >
> > > I'll add it to the migration guide though.
> > >
> > > > As a side note, is there any plan to refactor the maven plugin to use
> > >
> > > more
> > >
> > > > "mavenized" parameter, better that just getting the command line
> > >
> > > arguments
> > >
> > > > as <extraarg> ?
> > >
> > > I think this has been in since 2.1.3.    The wsdlOption stuff has a
> > > nearly complete set of properties:
> > >
> > >    protected List<String> packagenames;
> > >    protected List<String> extraargs = new ArrayList<String>();
> > >    protected File outputDir;
> > >    List<String> namespaceExcludes;
> > >    Boolean defaultExcludesNamespace;
> > >    Boolean defaultNamespacePackageMapping;
> > >    File dependencies[];
> > >    File redundantDirs[];
> > >    String bindingFiles[] = new String[0];
> > >    String wsdlLocation = DEFAULT_WSDL_LOCATION;
> > >    String frontEnd;
> > >    String dataBinding;
> > >    String wsdlVersion;
> > >    String catalog;
> > >    boolean extendedSoapHeaders;
> > >    boolean validateWsdl;
> > >    String serviceName;
> > >    boolean autoNameResolution;
> > >    boolean noAddressBinding;
> > >
> > > extraargs is still there for compat as well as to specify any extra
> flags
> > > not
> > > addressed above (like -verbose, but that is now auto hooked into mvn's
> -X
> > > flag)
> > >
> > >
> > > --
> > > Daniel Kulp
> > > [email protected]
> > > http://www.dankulp.com/blog
>
> --
> Daniel Kulp
> [email protected]
> http://www.dankulp.com/blog
>

Reply via email to