> We are running Nexus 1.8. I am considering upgrading to the latest version.
> Would our artifacts be migrated safely?
This mailing list supports Apache Maven. Sonatype Nexus has its own
mailing lists. Please use them for such questions.
Wayne
---
Oh, thanks for the pointer... I figured it out... The permissions were wrong.
Thank you very much for your help.
We are running Nexus 1.8. I am considering upgrading to the latest version.
Would our artifacts be migrated safely?
--
View this message in context:
http://maven.40175.n5.nabble.com/F
This may be helpful
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html
-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Wednesday, June 06, 2012 1:02 PM
To: Maven Users List
Subject: Re: How does one mirror a maven repository?
Nexus Pro
Found the email Russ ;-)
Anyway, repository.s.o isn't intended to be a mirror, it's just a
proxy used primarily by us for internal use and for oss users building
our stuff. http://search.maven.org has replaced the need to use rso's
search as well.
Regarding why the files aren't in the repository,
Nexus Pro has functionality that would allow you to do mirroring, we have a
bunch of customers doing exactly what you ask.
On Fri, Jun 1, 2012 at 12:53 PM, Phillip Hellewell wrote:
> Hi,
>
> Our company would like to mirror our Maven repository at a remote
> location. Currently we've been using
possibly version mismatch on one of your dependent jars..i would try
contacting1)atlassian
2)maven users group
Martin-
___
...extensive disclaimer goes here...
> Date: Wed, 6 Jun 2012 10:20:58 -0400
> Subject: Re: Editing a plugin announcement doesn't work
> From: davelnew...@gmail
That method will work fine with projects external repos. Just as long as
there are no svn:external links inside the folders itself come from
svn:externals link.
Other important thing to note is that if you are using separeate aggregation
and root pom's in the project. then you must have definiti
Start with reading the Maven release plugin description, specially prepare
and perform action's documentation.
This problem with svn:externals is that IF you are using svn:externals that
link to the project itself the release branch will point to the trunk.
release:prepare phase will
1. crawls
