On 06.05.2014 09:07, Dan Tran wrote:
Ofcourse, I do have Maven repo manager ̣ nexus at this time), however still
struggle on how to get only plugin's artifact goto one proxy and others
goto to another proxy using mirror settings.
Are you able to do so?
-Dan
I'm none to sure that this would even help at all:
Presumably you are trying to separate artifacts used by plugins during
your build (where you might use e.g. GPL licensed modules) from
artifacts used as dependencies in your project proper (where using that
same GPL licensed modules would make your legal department scream) by
separating the repositories used to provide them.
As far as I know/understand all artifacts are downloaded to the same
local cache repository (~/.m2/repository), regardless of whether they
were required by some plugin or as a dependency of your project.
This makes them available for both purposes and thus obliterates all
your efforts of keeping them separate.
Maven Masters: Please correct me if I'm wrong.
Cheers,
Wolf
On Mon, May 5, 2014 at 11:59 PM, Christian Domsch <[email protected]> wrote:
Hi Dan,
Did you consider using nexus? There you can setup any kind of strange repo
setup your mind can come up with ;-) For your case, create one repo for
your project stuff and one repo for your plugin stuff. Create a group for
both for easy access and control access by authorization...
Christian
On 06.05.2014 06:29, Dan Tran wrote:
Thanks Barrie,
Will see what I can can do.
On Mon, May 5, 2014 at 5:04 PM, Barrie Treloar <[email protected]>
wrote:
On 6 May 2014 09:21, Dan Tran <[email protected]> wrote:
for legal purpose ( btw, please dont drill me here), I would like to use
one mirror as a gate way for all of of my project dependencies,and
another
mirror as a gate way for all of my plugins and their dependencies
is it possible? Posting a settings.xml config here is very much
appreciated
Having not done this, here is some more insane advice.
I'd use three.
One proxy to proxy the other two proxies.
All developers point to the master proxy.
You can then configure the master proxy to refer to the project
dependencies proxy and another for plugins dependencies proxy.
You might need a more sophisticated maven repository manager that you can
restrict what is allowed in the proxies (i.e. it just doesn't go and grab
stuff for you).
You're going to have to do a lot of fiddling to get this to work.
I'm not convinced it is going to give you what legal thinks it will...
If you could write up what you tried and whether it worked it would be
helpful for anyone else attempting the same thing...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
