I was going to suggest that as a stop gap solution, but realistically you should be telling that other team that it is the year 2012 and they should be using a repository manager. In the extreme case set it up for them and get their release process going as well.
manfred On Wed, September 19, 2012 8:09 am, Anthony Dahanne wrote: > hello, > why don't you push those private jars as snapshot versions into your > local nexus ? > Then in your build, use something like -U to make sure maven grabs the > latest snapshots. > Anthony > > On Wed, Sep 19, 2012 at 11:04 AM, mlandman99 <[email protected]> wrote: >> Hi, >> >> My java project has several dependencies, both external (i.e. in the >> public >> repo) and private (built by our own company). It's a QA project, that >> can be >> run locally in Eclipse, and also runs on a CI server (teamcity). When it >> 'builds', it runs then maven phase: "integration-test", which then runs >> testNG tests within my classes. So far so good. >> >> Unfortunately the private jars that it uses are not under any sort of >> control. They are built by a different team in my company, and are >> placed in >> an available network-share, but that's it. They don't seem to be >> properly >> 'versioned', and are not placed in any local (nexus) repository, unless >> I >> manually put them there. >> >> For running nightly automated testing, I want to ensure I always utilize >> the >> most recent version of those private jars. So far, I've manually placed >> a >> version of them in a local nexus repo, and they are successfully pulled >> down >> when teamcity runs the build. But I don't have a way of getting the >> nightly >> builds up inside that nexus repo. Even if I did, they would always just >> be >> "version 1.0" and probably won't be re-downloaded anyway. >> >> So... I'm looking for suggestions re: a strategy on how to *ensure* that >> each time my project is built, that it properly grabs the new version of >> those private jars, of which the only reliable way to access them is in >> a >> network share drive. The other public jars are successfully managed by >> maven. >> >> Is there a way to use Maven to help me pull in these private jars that >> exist >> on a network share? If anyone has any suggestions on a strategy re: how >> I >> can proceed, I'd appreciate it! >> >> Thanks! >> >> >> >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/strategy-for-incorporating-private-jars-into-a-project-tp5722524.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
