Well, the mirrors point to the same place. We started with using the
element instead of the element. It probably doesn't
make sense to have both.
On Tue, Nov 10, 2015 at 3:54 PM, Daan Hoogland
wrote:
> Jeff, I am definitely not god amongst maven users so I have to start
> guessing now. It migh
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 wrote:
> Yes
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 element which points to
archiva releases repo and archiva snapshots repo.
* Added mirrors for both the releases and snapshots repo.
* Deployed a built version
Jeff, kicking in an open door: did you edit your .m2/settings.xml?
On Tue, Nov 10, 2015 at 3:27 PM, Jeff Hair 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 ou
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 wrote:
> Hi,
>
> We are setting up an internal Mave
