[
https://issues.apache.org/jira/browse/AXIS2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bull updated AXIS2-3470:
------------------------------
Description:
The plugin guide states that "By default, it is assumed that [services.xml] is
already present in classesDirectory/META-INF". classesDirectory is the location
of the compiled classes and, as such, will be deleted whenever clean is invoked.
Could you please consider conforming to the usual maven behaviour of copying
configuration files from the src directory: my suggestion would be something
like;
src->main->aar
(c.f. src->main->webapps etc.)
was:
If you use the AAR plugin on its own, it doesn't create the "service.xml".
Would it be possible to introduce a dependency upon the java2wsdl plugin so
that if you type:
mvn clean axis2-aar:aar
it will create the service.xml file before packaging the archive (or at least
make this a configurable option)
Summary: AAR maven2 plugin: request to change default location of
service.xml (was: AAR maven2 plugin should depend upon java2wsdl maven2 plugin)
> AAR maven2 plugin: request to change default location of service.xml
> --------------------------------------------------------------------
>
> Key: AXIS2-3470
> URL: https://issues.apache.org/jira/browse/AXIS2-3470
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 1.3
> Environment: Maven 2.0.8
> Cygwin 1.5.24 running on Windows XP
> Reporter: David Bull
>
> The plugin guide states that "By default, it is assumed that [services.xml]
> is already present in classesDirectory/META-INF". classesDirectory is the
> location of the compiled classes and, as such, will be deleted whenever clean
> is invoked.
> Could you please consider conforming to the usual maven behaviour of copying
> configuration files from the src directory: my suggestion would be something
> like;
> src->main->aar
> (c.f. src->main->webapps etc.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
