Ping?
Maybe a different phrasing of the question would help:
How could I publish an artifact generated by a maven project, but also
make sure that artifact did NOT include any dependencies? The desired
result is: When some other project depends on this artifact, the project
would not see any transitive dependencies.
For example:
myWSDL pom snippet:
...
<groupId>com.mine</groupId>
<artifactId>myWSDL</artifactId>
<version>1.0-SNAPSHOT</version>
...
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>attach-artifacts</id>
<phase>package</phase>
<goals>
<goal>attach-artifact</goal>
</goals>
<configuration>
<artifacts>
<artifact>
<file>target/generated/wsdl/mywsdl.wsdl</file>
<type>wsdl</type>
</artifact>
</artifacts>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Some other project pom that uses the mywsdl file:
<artifactId>serviceClient</artifactId>
...
<dependencies>
<dependency>
<groupId>com.mine</groupId>
<artifactId>myWSDL</artifactId>
<type>wsdl</type>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
How can I prevent 'serviceClient' project from seeing the transitive
dependencies of 'myWSDL'?
I found other posts that mention things like:
'Maven Remote Resources Plugin' -
http://www.mail-archive.com/[email protected]/msg112195.html
'Don't do it' -
http://www.mail-archive.com/[email protected]/msg90783.html
We want non-maven projects to be able to use these WSDLs easily (eg:
using maven ant tasks to pull in the WSDL), so even though a WSDL is a
small artifact, we want to publish and version it as a standard artifact
(with a custom "type").
Dan
On 08/28/2012 03:30 PM, Dan Rollo wrote:
Hi,
We have a maven project that produces both a .war file and a WSDL file.
The WSDL is auto-generated by the project. Right now we are publishing
the WSDL as an attachment (to the packaged 'war' file) with a custom
type="wsdl".
This allows us to use the WSDL artifact as a dependency in other
projects. The problem is when we use the "wsdl" dependency, it includes
all the dependencies of the project that generated the WSDL (eg: all the
deps of the 'war' project).
How can we publish/use a generated WSDL file, and avoid getting
dependencies that where used to generate the WSDL?
Thanks,
Dan Rollo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
