Currently, the studio uses the Petals Maven plug-in to create Petals components.
It also ignores custom settings.xml files.
In fact, the studio should take a different approach:
- First, it should provide a better wizard to create components.
- In addition to Maven information, it should customize the generated code (support for providers, consumers, generate code from a WSDL) and not rely on the Petals Maven plug-in anymore.
- A POM should be generated too, from a template and a given version of the CDK, selected in the wizard.
- Once generated, the Java project should be completed by M2 Eclipse to retrieve Maven dependencies.
- Or, there could be an option in the preferences to indicate a local repository or directory of resources (to be thought...).
The wizard may also be replaced by another solution (e.g. to synchronize component's WSDL and code processor): wizard + builder or wizard + action.