Yes. It's like this. Not all of this may make sense as I don't normally have a custom MVN repo set up. * Edited settings.xml to have a new <repositories> element which points to archiva releases repo and archiva snapshots repo. * Added mirrors for both the releases and snapshots repo. * Deployed a built version of 4.5.3-SNAPSHOT to archiva using mvn deploy * Wipe out local ~/.m2/repository and see what happens. This leads to the error I described in the first post.
On Tue, Nov 10, 2015 at 3:34 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > Jeff, kicking in an open door: did you edit your .m2/settings.xml? > > On Tue, Nov 10, 2015 at 3:27 PM, Jeff Hair <j...@greenqloud.com> wrote: > > > Also, mirroring is probably not the best term. We are not mirroring the > > build artifacts from the official build servers. We are attempting to > > deploy artifacts produced by our build system into Archiva. > > > > On Tue, Nov 10, 2015 at 2:23 PM, Jeff Hair <j...@greenqloud.com> wrote: > > > > > Hi, > > > > > > We are setting up an internal Maven repository to speed up our inhouse > > > builds that depend on CloudStack on the 4.5 branch (which contains > > > 4.5.3-SNAPSHOT right now). > > > > > > It's mostly working, but we are running into something very strange > with > > > the checkstyle dependency. After uploading all artifacts with mvn > deploy, > > > our repository server is directing mvn to go to > > > repository.apache.org/snapshots in order to download the checkstyle > > > dependency... which of course does not exist. > > > > > > Has anyone gone through the experience of putting CloudStack SNAPSHOT > > > artifacts into an in-house Maven repository? > > > > > > > > > > > -- > > *Jeff Hair* > > Technical Lead and Software Developer > > > > Tel: (+354) 415 0200 > > j...@greenqloud.com > > www.greenqloud.com > > > > > > -- > Daan > -- *Jeff Hair* Technical Lead and Software Developer Tel: (+354) 415 0200 j...@greenqloud.com www.greenqloud.com
