I've setup a nexus on geronimo.zones.apache.org (as the gbuild user),
and then setup geronimo/repository/trunk (which contains copies of
what is currently in geronimo/server/trunk/repository) exposed as a
hosted repository here:
http://geronimo.zones.apache.org:8081/nexus/content/repositories/geronimo
Right now this is just a test, but if this looks like a viable
solution to our repository problems, and mvn builds don't balk on
connection problems, then I will setup automatic updates of the tree
via cron and get rid of the ick .svn stuff that shows up in the listing.
Shall we give it a try?
Ping me on IRC if you want the admin password.
--jason
On Dec 2, 2008, at 8:12 AM, David Jencks wrote:
In order to get the build to work with my use of nexus I've added
the trunk svn repo (server/trunk/repository) to the nexus
repositories.
This makes me wonder if we should just set up a single repo in svn
and put all our private builds there rather than having branch-
specific repos. Would this result in more or less or the same load
on the svn server?
I also wonder if our policy of patching apache projects and coming
up with our own psuedo releases is really the best idea or if we
should just copy their code over in svn and build it more directly.
I also discovered a couple of weeks back that the lack of poms in
this repo was causing significant build delays while maven was
looking everywhere it could think of for them so I added them when I
could easily find them in the artifacts. I think we should add them
for the other artifacts as well.
thanks
david jencks
