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
