cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Hair <j...@greenqloud.com>
Subject Re: Mirroring CloudStack to internal MVN repository
Date Tue, 10 Nov 2015 16:22:00 GMT
Well, the mirrors point to the same place. We started with using the
<mirror> element instead of the <repository> element. It probably doesn't
make sense to have both.

On Tue, Nov 10, 2015 at 3:54 PM, Daan Hoogland <daan.hoogland@gmail.com>
wrote:

> Jeff, I am definitely not god amongst maven users so I have to start
> guessing now. It might be that you need to do magic in the pom for this to
> work. or in MAVEN_OPTS. (what are the mirrors for? these are mirrors of
> your local repo, right?)
>
> On Tue, Nov 10, 2015 at 4:47 PM, Jeff Hair <jeff@greenqloud.com> wrote:
>
> > 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.hoogland@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 <jeff@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 <jeff@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
> > > > jeff@greenqloud.com
> > > > www.greenqloud.com
> > > >
> > >
> > >
> > >
> > > --
> > > Daan
> > >
> >
> >
> >
> > --
> > *Jeff Hair*
> > Technical Lead and Software Developer
> >
> > Tel: (+354) 415 0200
> > jeff@greenqloud.com
> > www.greenqloud.com
> >
>
>
>
> --
> Daan
>



-- 
*Jeff Hair*
Technical Lead and Software Developer

Tel: (+354) 415 0200
jeff@greenqloud.com
www.greenqloud.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message