Not sure I understood this correctly. It appears that you want to have a
1..n RELEASE
repositories, that are access controlled. There are couple of ways you can
go about
it (I think):
- if you use a Repository Manager like Nexus, you can get what you want,
maintaining
the same "settings.xml"
- Or you can always have a settings.xml with various mirror settings. Or
there are also
options available in the Maven Client command to *override* the default
settings.xml
locations.
Don't know if that is what you are looking for.
Thanks,
mohan kr
-----Original Message-----
From: gorgophol [mailto:benjamin.h...@inter.de]
Sent: Wednesday, June 17, 2009 2:21 AM
To: users@maven.apache.org
Subject: Re: Can I prevent maven from searching dependencies in
localRepository?
Stephen Connolly-2 wrote:
>
> sounds like you are not using versions correctly.
>
> -SNAPSHOT versions are for untested local stuff.
>
> non-SNAPSHOT versions are pulled from repositories and have been
> tested. They are only produced from a build machine, so no developer
> should have a non-SNAPSHOT version unless it came from a remote repo
>
Maybe we're not using versions and SNAPSHOTs as expected. It's not
practicable in our context here. Well I'm the supervisor of the build
server, where one central installation of maven runs, and designed the
release process, trying to use maven. There are several company rules that
have to be fulfilled. Every build of every java developer group in the
company has to be done via this central installation. Builds can only be
started out of scm (cvs in our case). Moving an artifact to another
repository has to be done without re-building it, so its absolutly sure,
that nothing has changed.
So using SNAPSHOT gets very complicated, because first developers have to
check in all their poms with all dependencies (which can count up to more
than 100) with a SNAPSHOT version and test it. This could not be used, so
they have to build it again, removing all SNAPSHOT entries in every of the
poms (and the poms dependencies ...), check In again an re-build. Then have
to test again, because there is no guarantee everything is the same as
tested before. Deploying artifacts into a share-repository by re-building
them is not allowed.
So I always get into trouble with the local repository. Well I'm just trying
to bring maven into this company, but I have to concern the development
contexts already existing. In my oppinion maven seems to be flexible enough
for that. This is really the last obstacle before my release process can get
productive. But there are things that cannot be changed now, so I have to
find a possibility to exclude localRepsitory from the artifact search
process in maven.
I'd prefer a solution maven might provide in his depth somewhere. My other
option is to delete artifacts from localRepository after every build and
deploy.
--
View this message in context:
http://www.nabble.com/Can-I-prevent-maven-from-searching-dependencies-in-loc
alRepository--tp24054742p24068271.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
