Hi there,
Try this,
Change the packaging to "pom"
mvn deploy:deploy-file -DgroupId=<your group>
-DartifactId=<artifact>
-Dversion=<version>
-Dfile=<path-to-your-pom.xml>
-Dpackaging=pom
-DrepositoryId=<repoId>
-Durl=<url-to-deploy>
-allan
[EMAIL PROTECTED] wrote:
Here's my situation... I've setup an internal proxy where everyone
internal to our organization can download from. Some of our projects
depend on the JWSDP packages, and for example, if you're using the
JAX-RPC Sun libraries, there's about 10 other libraries it depends on.
I want to be able to just deploy this pom to the internal repository...
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>javax.xml</groupId>
<artifactId>jaxrpc</artifactId>
<version>1.1.3</version>
<name>JAXRPC Package</name>
<description>
Part of the Java Web Services Developer Pack 2.0
</description>
<dependencies>
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxrpc-api</artifactId>
<version>1.1.3</version>
</dependency>
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxrpc-impl</artifactId>
<version>1.1.3</version>
</dependency>
...
This way, developers can just add the following dependency to their
project and get all the jaxrpc libraries.
<dependency>
<groupId>javax.xml</groupId>
<artifactId>jaxrpc</artifactId>
<version>1.1.3</version>
</dependency>
However, I haven't found a way to use deploy:deploy-file to just deploy
the Pom w/ Dependencies into the internal repository. Can someone lend
some insight into a possible solution. I'm trying to avoid just
copying the structure into the internal repository and I was wondering
if the deploy plugin could do something for me.
Thanks,
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]