Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Deploying local artifacts from autobuild/uploadToMaven.xml

Will,

 

Yes, you are looking at the right process for the official release build to upload maven artifacts. build.deps.dir is the location where the release build looks for all the dependencies for the build/release,  specifically for the process of uploading artifacts to maven, it’s the location where it looks for the dependency mavenant task jar ${build.dpes.dir}/mavenant/maven-ant-tasks-2.1.3.jar

Btw, uploadToNexus.xml is used for current release build to upload artifacts to sonatype, uploadToMaven.xml was once used to upload artifacts to maven central which is now obsolete. You can reference both for your purpose of uploading artifacts to your local maven repo.

 

Liu Bo

 

From: William Dazey [mailto:dazeydev.3@xxxxxxxxx]
Sent: Tuesday, May 05, 2015 5:07
To: eclipselink-dev@xxxxxxxxxxx
Subject: [eclipselink-dev] Deploying local artifacts from autobuild/uploadToMaven.xml

 

I am looking for some help uploading eclipselink artifacts to a local maven repo as a part of a local build of the 2.6_WAS branch. I noticed autobuild.xml and uploadToMaven.xml and suspect these are the process that already builds artifacts for sonatype. It seemed general enough that I thought I could pass in my own "maven.repo.url" and "maven.repo.dir", but there seems to be a "build.deps.dir" that is stored on the server that normally invokes this process and has it's own hardcoded dependencies. Before I invest too much in trying to reverse-engineer what is needed, I figured I'd ask if there is are steps someone has worked out for this process? Is there anyone familiar enough with this maven process that could tell me if reuse of uploadToMaven.xml, pointed at another repo, is plausible.

Thanks,

Will Dazey


Back to the top