Manfred Moser wrote > Write a script that invokes the the mvn deploy plugin with the deploy goal > and invoke that as separate freestyle build step before your other build > > e.g. > > mvn deploy:deploy-file -D ... > > More info on parameters and stuff at > > http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html > > manfred
Done! Was easier than I thought. I've stored the logic in a java class within "project 1". On the CI server, I'll have a separate maven build step that only runs that one class as a testNG test, which will get those 4-5 jars to the repo. Then, my next maven build step in the same project (but with a -U) should enforce that it rebuilds with those guaranteed-to-be-new internal jars. Thanks for the help, all! -- View this message in context: http://maven.40175.n5.nabble.com/strategy-for-incorporating-private-jars-into-a-project-tp5722524p5723825.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]
