Heya,
This is the behavior I've experienced when changing the packaging to
pom. Whenever the packaging is changed to pom, this is the pom file
that gets uploaded into the internal repository.
4.0.0
javax.xml
jaxrpc
pom
1.3
POM was created from deploy:deploy-file
deployed
So, the pom doesn't contain the necessary dependencies. If I add the
parameter -pomFile and specify the pom file, the right pom file gets
deployed, but then a jar also gets created. I'm wondering if I'm
overlooking something really simple here. :)
Thanks,
Ryan
On 2/3/2006, "Allan Ramirez" <[EMAIL PROTECTED]> wrote:
>Hi there,
>
>Try this,
>
>Change the packaging to "pom"
>
>mvn deploy:deploy-file -DgroupId=
>-DartifactId=
>-Dversion=
>-Dfile=
>-Dpackaging=pom
>-DrepositoryId=
>-Durl=
>
>-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...
>>
>>
>> 4.0.0
>> javax.xml
>> jaxrpc
>> 1.1.3
>> JAXRPC Package
>>
>> Part of the Java Web Services Developer Pack 2.0
>>
>>
>>
>> javax.xml
>> jaxrpc-api
>> 1.1.3
>>
>>
>> javax.xml
>> jaxrpc-impl
>> 1.1.3
>>
>> ...
>>
>>This way, developers can just add the following dependency to their
>>project and get all the jaxrpc libraries.
>>
>>
>> javax.xml
>> jaxrpc
>> 1.1.3
>>
>>
>>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]
