Hello,
this is rather a Nexus question, but so far your solution looks good to me.

Vincent


2012/11/9 Davis, Chad <[email protected]>

> This may be a nexus only question, in which case I'll take it to the nexus
> list.  However, It may also be something better handled from within maven
> itself.  I'm not sure.
>
> Here's my issue.  We have a release build environment.  It has it's own
> nexus server that holds our official release artifacts and serves as the
> legally authorize proxy of the public repos ( maven central, et. al. ).
>  The main purpose of this environment is corporate release building.  For
> our continuous integration needs, we have our own local build servers and a
> local nexus.  This nexus will hold our snapshots, serve as a low latency
> local repo to speed up our ci builds ( the release environment is
> geographically distant ).
>
> I'm trying to figure out how to set this all up to achieve the following
> requirements:
>
>
> 1)      local nexus has same proxy filtering as remote one
>
> 2)      local nexus has an extra "dev" repo that we can add additional
> dependencies to as needed; these might be ones that could be proxied
> through from maven central, but I would like to keep track of our new
> dependencies in an isoloated silo so we can easily keep tabs of them when
> we enter our "legal approval" phase
>
> 3)      no changes to the poms themselves so when we migrate from CI build
> environment to official release build environment we don't have to edit
> "source"
>
> The solution I'm homebrewing for the moment looks like this
>
>
> 1)      set up local nexus to have a proxy repo that proxies the release
> nexus's "public" group, if this even works technically
>
> 2)      set up a hosted repo on local nexus that dev can add dependencies
> to at will, this will aggregate our list of new deps that we will have to
> process through legal before entering release cycle
>
> 3)      group these two together and use settings.xml to mirror the remote
> release nexus ( which is the one officially declared in our poms )
>
> Better ideas?
>

Reply via email to