Roland,
We did this for multiple 3rd party jars and didn't have any issues.
In settings.xml define the server entry for your server where you want to
deploy the jar.
1. <server>
<id>inhouse_release</id>
<username>maven</username>
<privateKey>/home2/wasadm/.ssh/maven_key</privateKey>
</server>
then in the profile section define the entry
2. <id>releaserepository</id>
<repositories>
<repository>
<id>inhouse_release</id>
<name>Inhouse Release Repository</name>
<url>
http://foobar.org/maven2_repositories/inhouse_release/
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
ensure that you enable the profile
3. you need to deploy it using mvn deploy
mvn deploy:deploy-file -Dfile=ibm-j2ee.jar
-DgroupId=com.ibm-DartifactId=ibm-j2ee -Dversion=
1.3 -Dpackaging=jar -DgeneratePom=true -DrepositoryId=inhouse_release
-Durl=scp://foobar.org/apps/maven2/release_repository
4. In your pom you can use this
<groupId>com.ibm</groupId>
<artifactId>ibm-j2ee</artifactId>
<version>1.3</version>
SNAPSHOTS should only be used for artifacts for whom work is in progress and
not for relased version of third party artifacts.
-Sanjay
On 4/14/06, Roland Asmann <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm trying to deploy 3rd party snapshots to our local maven-proxy, but
> have
> problems when my builds try to access the libraries. I've already found
> out
> that the POM and JAR do not have the same name, but have a buildnumber
> appended to their names, which differs between the two.
> Then, when I add sources, those get an even higher number!
>
> Just wondering, is there a way to turn OFF the replacing of 'SNAPSHOT'
> with
> the deployment date/time, since this would solve my whole problem?!
>
> Thanks!
>
> Roland
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
