You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dan Tran <da...@gmail.com> on 2014/05/06 01:51:31 UTC
use separate mirrors for project dendencies and plugin dependencies ??
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
Thanks
-D
BTW
as documented, I am currently able to get both type of artifacts to use
the same mirror to my repo manager
http://maven.apache.org/guides/mini/guide-mirror-settings.html does not
seem to support what I am looking for
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Anders Hammar <an...@hammar.net>.
>
> Also, do i need to redefine 'central' it looks redundant to me
It's best-practice IMO. It ensures that the central definition declared in
the super-POM is overwritten with a dummy (not working) URL. It will/should
then be handled by the mirror so that it is redirected to the internal
mirror. If, for any reason, the mirror definition is removed or not
correctly declared you will then quickly noticed this as your Maven build
will not work (as the calls to 'central' will fail).
/Anders
>
> Thanks
>
> -D
>
>
>
> On Mon, May 26, 2014 at 10:34 PM, Anders Hammar <an...@hammar.net> wrote:
>
> > For my solution on this topic I didn't declare a mirror for
> > 'plugin-central', i.e. I didn't have the 'plugin-repo' mirror
> declaration.
> > I does not add anything as it is only a mirror for one repo.
> >
> > /Anders
> >
> >
> > On Sun, May 25, 2014 at 3:00 AM, Dan Tran <da...@gmail.com> wrote:
> >
> > > I got some thing working
> > >
> > > 1. at my repo manager, create a proxy, called plugin-central, to host
> > > another central.maven.org/maven2
> > > 2. reconfigure my global settings.xml with the following contents.
> Please
> > > help to review this content
> > >
> > > <mirrors>
> > > <mirror>
> > > <id>product-repo</id>
> > > <mirrorOf>*,!plugin-central</mirrorOf>
> > > <name>Internal Maven Repository Manager</name>
> > > <url>http://repos.xxx.com:8081/nexus/content/groups/public</url>
> > > </mirror>
> > > <mirror>
> > > <id>plugin-repo</id>
> > > <mirrorOf>plugin-central</mirrorOf>
> > > <name>Internal Maven Repository Manager for plugin and its
> > transitive
> > > dependencies</name>
> > > <url>
> http://repos.xxxx.com:8081/nexus/content/groups/plugin-public
> > > </url>
> > > </mirror>
> > > </mirrors>
> > >
> > > <profiles>
> > > <profile>
> > > <id>redefine-default-repositories</id>
> > > <repositories>
> > > <repository>
> > > <!-- do we really need this?? since it is mirrored any way
> -->
> > > <id>central</id>
> > > <url>http://central</url>
> > > <releases><enabled>true</enabled></releases>
> > > <snapshots><enabled>true</enabled></snapshots>
> > > </repository>
> > > </repositories>
> > > <pluginRepositories>
> > > <!-- this allow use to separate product and plugin dependencies
> > > into separate mirrors/proxy -->
> > > <pluginRepository>
> > > <id>plugin-central</id> <!--must be first in list -->
> > > <url>http://central</url>
> > > <releases><enabled>true</enabled></releases>
> > > <snapshots><enabled>true</enabled></snapshots>
> > > </pluginRepository>
> > > <!-- plugin download should never get here since 'central'
> > already
> > > cover by another proxy in plugin-central mirror-->
> > > <pluginRepository>
> > > <id>central</id>
> > > <url>http://central</url>
> > > <releases><enabled>true</enabled></releases>
> > > <snapshots><enabled>true</enabled></snapshots>
> > > </pluginRepository>
> > > </pluginRepositories>
> > > </profile>
> > > </profiles>
> > >
> > > <activeProfiles>
> > > <activeProfile>redefine-default-repositories</activeProfile>
> > > </activeProfiles>
> > >
> > >
> > > Thank you every one for participate in this discussion, specially
> Anders
> > > for leading to this solution
> > >
> > >
> > > If you have anything you want to add please chime in
> > >
> > >
> > > -Dan
> > >
> > >
> > >
> > > On Sat, May 24, 2014 at 1:19 AM, Anders Hammar <an...@hammar.net>
> > wrote:
> > >
> > > > It will if you use the same id, ie 'central'.
> > > >
> > > > /Anders (mobile)
> > > > Den 24 maj 2014 09:36 skrev "Dan Tran" <da...@gmail.com>:
> > > >
> > > > > Anders' suggestion sounds very logical
> > > > >
> > > > > however, i found this at super pom
> > > > >
> > > > > <repositories>
> > > > > <repository>
> > > > > <id>central</id>
> > > > > <name>Central Repository</name>
> > > > > <url>http://repo.maven.apache.org/maven2</url>
> > > > > <layout>default</layout>
> > > > > <snapshots>
> > > > > <enabled>false</enabled>
> > > > > </snapshots>
> > > > > </repository>
> > > > > </repositories>
> > > > >
> > > > > <pluginRepositories>
> > > > > <pluginRepository>
> > > > > <id>central</id>
> > > > > <name>Central Repository</name>
> > > > > <url>http://repo.maven.apache.org/maven2</url>
> > > > > <layout>default</layout>
> > > > > <snapshots>
> > > > > <enabled>false</enabled>
> > > > > </snapshots>
> > > > > <releases>
> > > > > <updatePolicy>never</updatePolicy>
> > > > > </releases>
> > > > > </pluginRepository>
> > > > > </pluginRepositories>
> > > > >
> > > > > Is there a way to disable/clear out the super pom
> pluginRepositories?
> > > > > If I add my own pluginRepositories, will it override the super pom
> > > > > one?
> > > > >
> > > > >
> > > > > Thanks
> > > > >
> > > > > Dan
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 6, 2014 at 6:20 AM, Barrie Treloar <baerrach@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > On 6 May 2014 20:23, Anders Hammar <an...@hammar.net> wrote:
> > > > > >
> > > > > > > >
> > > > > > > > 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.
> > > > > > > >
> > > > > > >
> > > > > > > I don't think this is correct with Maven 3. Maven 3 uses Aether
> > > which
> > > > > > AFAIK
> > > > > > > keeps the repository id for the artifact to verify from where
> it
> > > was
> > > > > > > downloaded. Haven't verified for this use case though.
> > > > > > >
> > > > > > > So, using Maven 3 it should be possible to specify one
> repository
> > > > > > > declaration for your deps and one pluginRepository declaration
> > > (with
> > > > a
> > > > > > > different repo id) for your plugins (incl deps). If you msut
> use
> > > > mirror
> > > > > > > declarations, I would use this for the deps and add exclusions
> > > (using
> > > > > > '!')
> > > > > > > for any pluginRepository.
> > > > > > >
> > > > > > > /Anders
> > > > > >
> > > > > >
> > > > > > I don't remember what happens for duplicates.
> > > > > > I think it used to complain that the artifact doesn't exist (if
> the
> > > one
> > > > > it
> > > > > > downloaded from is not available, even though its available
> > > elsewhere).
> > > > > >
> > > > > > The GPL example isn't a good one, as the output of running GPL is
> > not
> > > > GPL
> > > > > > itself.
> > > > > >
> > > > > > I think Nexus allows you to restrict things by licence so that
> you
> > > can
> > > > > > curate what is available in your repository manager. You'd have
> to
> > > look
> > > > > at
> > > > > > the docs to find out.
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Dan Tran <da...@gmail.com>.
Hi Ander
that makes sense
now i only have
<mirrors>
<mirror>
<id>product-repo</id>
<mirrorOf>*,!plugin-central</mirrorOf>
<name>Internal Maven Repository Manager</name>
<url>http://repos.xxx.com:8081/nexus/content/groups/public</url>
</mirror>
</mirrors>
Also, do i need to redefine 'central' it looks redundant to me
Thanks
-D
On Mon, May 26, 2014 at 10:34 PM, Anders Hammar <an...@hammar.net> wrote:
> For my solution on this topic I didn't declare a mirror for
> 'plugin-central', i.e. I didn't have the 'plugin-repo' mirror declaration.
> I does not add anything as it is only a mirror for one repo.
>
> /Anders
>
>
> On Sun, May 25, 2014 at 3:00 AM, Dan Tran <da...@gmail.com> wrote:
>
> > I got some thing working
> >
> > 1. at my repo manager, create a proxy, called plugin-central, to host
> > another central.maven.org/maven2
> > 2. reconfigure my global settings.xml with the following contents. Please
> > help to review this content
> >
> > <mirrors>
> > <mirror>
> > <id>product-repo</id>
> > <mirrorOf>*,!plugin-central</mirrorOf>
> > <name>Internal Maven Repository Manager</name>
> > <url>http://repos.xxx.com:8081/nexus/content/groups/public</url>
> > </mirror>
> > <mirror>
> > <id>plugin-repo</id>
> > <mirrorOf>plugin-central</mirrorOf>
> > <name>Internal Maven Repository Manager for plugin and its
> transitive
> > dependencies</name>
> > <url>http://repos.xxxx.com:8081/nexus/content/groups/plugin-public
> > </url>
> > </mirror>
> > </mirrors>
> >
> > <profiles>
> > <profile>
> > <id>redefine-default-repositories</id>
> > <repositories>
> > <repository>
> > <!-- do we really need this?? since it is mirrored any way -->
> > <id>central</id>
> > <url>http://central</url>
> > <releases><enabled>true</enabled></releases>
> > <snapshots><enabled>true</enabled></snapshots>
> > </repository>
> > </repositories>
> > <pluginRepositories>
> > <!-- this allow use to separate product and plugin dependencies
> > into separate mirrors/proxy -->
> > <pluginRepository>
> > <id>plugin-central</id> <!--must be first in list -->
> > <url>http://central</url>
> > <releases><enabled>true</enabled></releases>
> > <snapshots><enabled>true</enabled></snapshots>
> > </pluginRepository>
> > <!-- plugin download should never get here since 'central'
> already
> > cover by another proxy in plugin-central mirror-->
> > <pluginRepository>
> > <id>central</id>
> > <url>http://central</url>
> > <releases><enabled>true</enabled></releases>
> > <snapshots><enabled>true</enabled></snapshots>
> > </pluginRepository>
> > </pluginRepositories>
> > </profile>
> > </profiles>
> >
> > <activeProfiles>
> > <activeProfile>redefine-default-repositories</activeProfile>
> > </activeProfiles>
> >
> >
> > Thank you every one for participate in this discussion, specially Anders
> > for leading to this solution
> >
> >
> > If you have anything you want to add please chime in
> >
> >
> > -Dan
> >
> >
> >
> > On Sat, May 24, 2014 at 1:19 AM, Anders Hammar <an...@hammar.net>
> wrote:
> >
> > > It will if you use the same id, ie 'central'.
> > >
> > > /Anders (mobile)
> > > Den 24 maj 2014 09:36 skrev "Dan Tran" <da...@gmail.com>:
> > >
> > > > Anders' suggestion sounds very logical
> > > >
> > > > however, i found this at super pom
> > > >
> > > > <repositories>
> > > > <repository>
> > > > <id>central</id>
> > > > <name>Central Repository</name>
> > > > <url>http://repo.maven.apache.org/maven2</url>
> > > > <layout>default</layout>
> > > > <snapshots>
> > > > <enabled>false</enabled>
> > > > </snapshots>
> > > > </repository>
> > > > </repositories>
> > > >
> > > > <pluginRepositories>
> > > > <pluginRepository>
> > > > <id>central</id>
> > > > <name>Central Repository</name>
> > > > <url>http://repo.maven.apache.org/maven2</url>
> > > > <layout>default</layout>
> > > > <snapshots>
> > > > <enabled>false</enabled>
> > > > </snapshots>
> > > > <releases>
> > > > <updatePolicy>never</updatePolicy>
> > > > </releases>
> > > > </pluginRepository>
> > > > </pluginRepositories>
> > > >
> > > > Is there a way to disable/clear out the super pom pluginRepositories?
> > > > If I add my own pluginRepositories, will it override the super pom
> > > > one?
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Dan
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, May 6, 2014 at 6:20 AM, Barrie Treloar <ba...@gmail.com>
> > > wrote:
> > > >
> > > > > On 6 May 2014 20:23, Anders Hammar <an...@hammar.net> wrote:
> > > > >
> > > > > > >
> > > > > > > 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.
> > > > > > >
> > > > > >
> > > > > > I don't think this is correct with Maven 3. Maven 3 uses Aether
> > which
> > > > > AFAIK
> > > > > > keeps the repository id for the artifact to verify from where it
> > was
> > > > > > downloaded. Haven't verified for this use case though.
> > > > > >
> > > > > > So, using Maven 3 it should be possible to specify one repository
> > > > > > declaration for your deps and one pluginRepository declaration
> > (with
> > > a
> > > > > > different repo id) for your plugins (incl deps). If you msut use
> > > mirror
> > > > > > declarations, I would use this for the deps and add exclusions
> > (using
> > > > > '!')
> > > > > > for any pluginRepository.
> > > > > >
> > > > > > /Anders
> > > > >
> > > > >
> > > > > I don't remember what happens for duplicates.
> > > > > I think it used to complain that the artifact doesn't exist (if the
> > one
> > > > it
> > > > > downloaded from is not available, even though its available
> > elsewhere).
> > > > >
> > > > > The GPL example isn't a good one, as the output of running GPL is
> not
> > > GPL
> > > > > itself.
> > > > >
> > > > > I think Nexus allows you to restrict things by licence so that you
> > can
> > > > > curate what is available in your repository manager. You'd have to
> > look
> > > > at
> > > > > the docs to find out.
> > > > >
> > > >
> > >
> >
>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Anders Hammar <an...@hammar.net>.
For my solution on this topic I didn't declare a mirror for
'plugin-central', i.e. I didn't have the 'plugin-repo' mirror declaration.
I does not add anything as it is only a mirror for one repo.
/Anders
On Sun, May 25, 2014 at 3:00 AM, Dan Tran <da...@gmail.com> wrote:
> I got some thing working
>
> 1. at my repo manager, create a proxy, called plugin-central, to host
> another central.maven.org/maven2
> 2. reconfigure my global settings.xml with the following contents. Please
> help to review this content
>
> <mirrors>
> <mirror>
> <id>product-repo</id>
> <mirrorOf>*,!plugin-central</mirrorOf>
> <name>Internal Maven Repository Manager</name>
> <url>http://repos.xxx.com:8081/nexus/content/groups/public</url>
> </mirror>
> <mirror>
> <id>plugin-repo</id>
> <mirrorOf>plugin-central</mirrorOf>
> <name>Internal Maven Repository Manager for plugin and its transitive
> dependencies</name>
> <url>http://repos.xxxx.com:8081/nexus/content/groups/plugin-public
> </url>
> </mirror>
> </mirrors>
>
> <profiles>
> <profile>
> <id>redefine-default-repositories</id>
> <repositories>
> <repository>
> <!-- do we really need this?? since it is mirrored any way -->
> <id>central</id>
> <url>http://central</url>
> <releases><enabled>true</enabled></releases>
> <snapshots><enabled>true</enabled></snapshots>
> </repository>
> </repositories>
> <pluginRepositories>
> <!-- this allow use to separate product and plugin dependencies
> into separate mirrors/proxy -->
> <pluginRepository>
> <id>plugin-central</id> <!--must be first in list -->
> <url>http://central</url>
> <releases><enabled>true</enabled></releases>
> <snapshots><enabled>true</enabled></snapshots>
> </pluginRepository>
> <!-- plugin download should never get here since 'central' already
> cover by another proxy in plugin-central mirror-->
> <pluginRepository>
> <id>central</id>
> <url>http://central</url>
> <releases><enabled>true</enabled></releases>
> <snapshots><enabled>true</enabled></snapshots>
> </pluginRepository>
> </pluginRepositories>
> </profile>
> </profiles>
>
> <activeProfiles>
> <activeProfile>redefine-default-repositories</activeProfile>
> </activeProfiles>
>
>
> Thank you every one for participate in this discussion, specially Anders
> for leading to this solution
>
>
> If you have anything you want to add please chime in
>
>
> -Dan
>
>
>
> On Sat, May 24, 2014 at 1:19 AM, Anders Hammar <an...@hammar.net> wrote:
>
> > It will if you use the same id, ie 'central'.
> >
> > /Anders (mobile)
> > Den 24 maj 2014 09:36 skrev "Dan Tran" <da...@gmail.com>:
> >
> > > Anders' suggestion sounds very logical
> > >
> > > however, i found this at super pom
> > >
> > > <repositories>
> > > <repository>
> > > <id>central</id>
> > > <name>Central Repository</name>
> > > <url>http://repo.maven.apache.org/maven2</url>
> > > <layout>default</layout>
> > > <snapshots>
> > > <enabled>false</enabled>
> > > </snapshots>
> > > </repository>
> > > </repositories>
> > >
> > > <pluginRepositories>
> > > <pluginRepository>
> > > <id>central</id>
> > > <name>Central Repository</name>
> > > <url>http://repo.maven.apache.org/maven2</url>
> > > <layout>default</layout>
> > > <snapshots>
> > > <enabled>false</enabled>
> > > </snapshots>
> > > <releases>
> > > <updatePolicy>never</updatePolicy>
> > > </releases>
> > > </pluginRepository>
> > > </pluginRepositories>
> > >
> > > Is there a way to disable/clear out the super pom pluginRepositories?
> > > If I add my own pluginRepositories, will it override the super pom
> > > one?
> > >
> > >
> > > Thanks
> > >
> > > Dan
> > >
> > >
> > >
> > >
> > > On Tue, May 6, 2014 at 6:20 AM, Barrie Treloar <ba...@gmail.com>
> > wrote:
> > >
> > > > On 6 May 2014 20:23, Anders Hammar <an...@hammar.net> wrote:
> > > >
> > > > > >
> > > > > > 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.
> > > > > >
> > > > >
> > > > > I don't think this is correct with Maven 3. Maven 3 uses Aether
> which
> > > > AFAIK
> > > > > keeps the repository id for the artifact to verify from where it
> was
> > > > > downloaded. Haven't verified for this use case though.
> > > > >
> > > > > So, using Maven 3 it should be possible to specify one repository
> > > > > declaration for your deps and one pluginRepository declaration
> (with
> > a
> > > > > different repo id) for your plugins (incl deps). If you msut use
> > mirror
> > > > > declarations, I would use this for the deps and add exclusions
> (using
> > > > '!')
> > > > > for any pluginRepository.
> > > > >
> > > > > /Anders
> > > >
> > > >
> > > > I don't remember what happens for duplicates.
> > > > I think it used to complain that the artifact doesn't exist (if the
> one
> > > it
> > > > downloaded from is not available, even though its available
> elsewhere).
> > > >
> > > > The GPL example isn't a good one, as the output of running GPL is not
> > GPL
> > > > itself.
> > > >
> > > > I think Nexus allows you to restrict things by licence so that you
> can
> > > > curate what is available in your repository manager. You'd have to
> look
> > > at
> > > > the docs to find out.
> > > >
> > >
> >
>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Dan Tran <da...@gmail.com>.
I got some thing working
1. at my repo manager, create a proxy, called plugin-central, to host
another central.maven.org/maven2
2. reconfigure my global settings.xml with the following contents. Please
help to review this content
<mirrors>
<mirror>
<id>product-repo</id>
<mirrorOf>*,!plugin-central</mirrorOf>
<name>Internal Maven Repository Manager</name>
<url>http://repos.xxx.com:8081/nexus/content/groups/public</url>
</mirror>
<mirror>
<id>plugin-repo</id>
<mirrorOf>plugin-central</mirrorOf>
<name>Internal Maven Repository Manager for plugin and its transitive
dependencies</name>
<url>http://repos.xxxx.com:8081/nexus/content/groups/plugin-public
</url>
</mirror>
</mirrors>
<profiles>
<profile>
<id>redefine-default-repositories</id>
<repositories>
<repository>
<!-- do we really need this?? since it is mirrored any way -->
<id>central</id>
<url>http://central</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
</repositories>
<pluginRepositories>
<!-- this allow use to separate product and plugin dependencies
into separate mirrors/proxy -->
<pluginRepository>
<id>plugin-central</id> <!--must be first in list -->
<url>http://central</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</pluginRepository>
<!-- plugin download should never get here since 'central' already
cover by another proxy in plugin-central mirror-->
<pluginRepository>
<id>central</id>
<url>http://central</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>redefine-default-repositories</activeProfile>
</activeProfiles>
Thank you every one for participate in this discussion, specially Anders
for leading to this solution
If you have anything you want to add please chime in
-Dan
On Sat, May 24, 2014 at 1:19 AM, Anders Hammar <an...@hammar.net> wrote:
> It will if you use the same id, ie 'central'.
>
> /Anders (mobile)
> Den 24 maj 2014 09:36 skrev "Dan Tran" <da...@gmail.com>:
>
> > Anders' suggestion sounds very logical
> >
> > however, i found this at super pom
> >
> > <repositories>
> > <repository>
> > <id>central</id>
> > <name>Central Repository</name>
> > <url>http://repo.maven.apache.org/maven2</url>
> > <layout>default</layout>
> > <snapshots>
> > <enabled>false</enabled>
> > </snapshots>
> > </repository>
> > </repositories>
> >
> > <pluginRepositories>
> > <pluginRepository>
> > <id>central</id>
> > <name>Central Repository</name>
> > <url>http://repo.maven.apache.org/maven2</url>
> > <layout>default</layout>
> > <snapshots>
> > <enabled>false</enabled>
> > </snapshots>
> > <releases>
> > <updatePolicy>never</updatePolicy>
> > </releases>
> > </pluginRepository>
> > </pluginRepositories>
> >
> > Is there a way to disable/clear out the super pom pluginRepositories?
> > If I add my own pluginRepositories, will it override the super pom
> > one?
> >
> >
> > Thanks
> >
> > Dan
> >
> >
> >
> >
> > On Tue, May 6, 2014 at 6:20 AM, Barrie Treloar <ba...@gmail.com>
> wrote:
> >
> > > On 6 May 2014 20:23, Anders Hammar <an...@hammar.net> wrote:
> > >
> > > > >
> > > > > 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.
> > > > >
> > > >
> > > > I don't think this is correct with Maven 3. Maven 3 uses Aether which
> > > AFAIK
> > > > keeps the repository id for the artifact to verify from where it was
> > > > downloaded. Haven't verified for this use case though.
> > > >
> > > > So, using Maven 3 it should be possible to specify one repository
> > > > declaration for your deps and one pluginRepository declaration (with
> a
> > > > different repo id) for your plugins (incl deps). If you msut use
> mirror
> > > > declarations, I would use this for the deps and add exclusions (using
> > > '!')
> > > > for any pluginRepository.
> > > >
> > > > /Anders
> > >
> > >
> > > I don't remember what happens for duplicates.
> > > I think it used to complain that the artifact doesn't exist (if the one
> > it
> > > downloaded from is not available, even though its available elsewhere).
> > >
> > > The GPL example isn't a good one, as the output of running GPL is not
> GPL
> > > itself.
> > >
> > > I think Nexus allows you to restrict things by licence so that you can
> > > curate what is available in your repository manager. You'd have to look
> > at
> > > the docs to find out.
> > >
> >
>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Anders Hammar <an...@hammar.net>.
It will if you use the same id, ie 'central'.
/Anders (mobile)
Den 24 maj 2014 09:36 skrev "Dan Tran" <da...@gmail.com>:
> Anders' suggestion sounds very logical
>
> however, i found this at super pom
>
> <repositories>
> <repository>
> <id>central</id>
> <name>Central Repository</name>
> <url>http://repo.maven.apache.org/maven2</url>
> <layout>default</layout>
> <snapshots>
> <enabled>false</enabled>
> </snapshots>
> </repository>
> </repositories>
>
> <pluginRepositories>
> <pluginRepository>
> <id>central</id>
> <name>Central Repository</name>
> <url>http://repo.maven.apache.org/maven2</url>
> <layout>default</layout>
> <snapshots>
> <enabled>false</enabled>
> </snapshots>
> <releases>
> <updatePolicy>never</updatePolicy>
> </releases>
> </pluginRepository>
> </pluginRepositories>
>
> Is there a way to disable/clear out the super pom pluginRepositories?
> If I add my own pluginRepositories, will it override the super pom
> one?
>
>
> Thanks
>
> Dan
>
>
>
>
> On Tue, May 6, 2014 at 6:20 AM, Barrie Treloar <ba...@gmail.com> wrote:
>
> > On 6 May 2014 20:23, Anders Hammar <an...@hammar.net> wrote:
> >
> > > >
> > > > 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.
> > > >
> > >
> > > I don't think this is correct with Maven 3. Maven 3 uses Aether which
> > AFAIK
> > > keeps the repository id for the artifact to verify from where it was
> > > downloaded. Haven't verified for this use case though.
> > >
> > > So, using Maven 3 it should be possible to specify one repository
> > > declaration for your deps and one pluginRepository declaration (with a
> > > different repo id) for your plugins (incl deps). If you msut use mirror
> > > declarations, I would use this for the deps and add exclusions (using
> > '!')
> > > for any pluginRepository.
> > >
> > > /Anders
> >
> >
> > I don't remember what happens for duplicates.
> > I think it used to complain that the artifact doesn't exist (if the one
> it
> > downloaded from is not available, even though its available elsewhere).
> >
> > The GPL example isn't a good one, as the output of running GPL is not GPL
> > itself.
> >
> > I think Nexus allows you to restrict things by licence so that you can
> > curate what is available in your repository manager. You'd have to look
> at
> > the docs to find out.
> >
>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Dan Tran <da...@gmail.com>.
Anders' suggestion sounds very logical
however, i found this at super pom
<repositories>
<repository>
<id>central</id>
<name>Central Repository</name>
<url>http://repo.maven.apache.org/maven2</url>
<layout>default</layout>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>central</id>
<name>Central Repository</name>
<url>http://repo.maven.apache.org/maven2</url>
<layout>default</layout>
<snapshots>
<enabled>false</enabled>
</snapshots>
<releases>
<updatePolicy>never</updatePolicy>
</releases>
</pluginRepository>
</pluginRepositories>
Is there a way to disable/clear out the super pom pluginRepositories?
If I add my own pluginRepositories, will it override the super pom
one?
Thanks
Dan
On Tue, May 6, 2014 at 6:20 AM, Barrie Treloar <ba...@gmail.com> wrote:
> On 6 May 2014 20:23, Anders Hammar <an...@hammar.net> wrote:
>
> > >
> > > 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.
> > >
> >
> > I don't think this is correct with Maven 3. Maven 3 uses Aether which
> AFAIK
> > keeps the repository id for the artifact to verify from where it was
> > downloaded. Haven't verified for this use case though.
> >
> > So, using Maven 3 it should be possible to specify one repository
> > declaration for your deps and one pluginRepository declaration (with a
> > different repo id) for your plugins (incl deps). If you msut use mirror
> > declarations, I would use this for the deps and add exclusions (using
> '!')
> > for any pluginRepository.
> >
> > /Anders
>
>
> I don't remember what happens for duplicates.
> I think it used to complain that the artifact doesn't exist (if the one it
> downloaded from is not available, even though its available elsewhere).
>
> The GPL example isn't a good one, as the output of running GPL is not GPL
> itself.
>
> I think Nexus allows you to restrict things by licence so that you can
> curate what is available in your repository manager. You'd have to look at
> the docs to find out.
>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Barrie Treloar <ba...@gmail.com>.
On 6 May 2014 20:23, Anders Hammar <an...@hammar.net> wrote:
> >
> > 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.
> >
>
> I don't think this is correct with Maven 3. Maven 3 uses Aether which AFAIK
> keeps the repository id for the artifact to verify from where it was
> downloaded. Haven't verified for this use case though.
>
> So, using Maven 3 it should be possible to specify one repository
> declaration for your deps and one pluginRepository declaration (with a
> different repo id) for your plugins (incl deps). If you msut use mirror
> declarations, I would use this for the deps and add exclusions (using '!')
> for any pluginRepository.
>
> /Anders
I don't remember what happens for duplicates.
I think it used to complain that the artifact doesn't exist (if the one it
downloaded from is not available, even though its available elsewhere).
The GPL example isn't a good one, as the output of running GPL is not GPL
itself.
I think Nexus allows you to restrict things by licence so that you can
curate what is available in your repository manager. You'd have to look at
the docs to find out.
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Anders Hammar <an...@hammar.net>.
>
> 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.
>
I don't think this is correct with Maven 3. Maven 3 uses Aether which AFAIK
keeps the repository id for the artifact to verify from where it was
downloaded. Haven't verified for this use case though.
So, using Maven 3 it should be possible to specify one repository
declaration for your deps and one pluginRepository declaration (with a
different repo id) for your plugins (incl deps). If you msut use mirror
declarations, I would use this for the deps and add exclusions (using '!')
for any pluginRepository.
/Anders
>
> Cheers,
> Wolf
>
>
>>
>>
>> On Mon, May 5, 2014 at 11:59 PM, Christian Domsch <ma...@landrus.de>
>> 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 <ba...@gmail.com>
>>>> wrote:
>>>>
>>>> On 6 May 2014 09:21, Dan Tran <da...@gmail.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: use separate mirrors for project dendencies and plugin dependencies
??
Posted by Wolf Geldmacher <wo...@abacus.ch>.
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 <ma...@landrus.de> 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 <ba...@gmail.com>
>>> wrote:
>>>
>>> On 6 May 2014 09:21, Dan Tran <da...@gmail.com> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: use separate mirrors for project dendencies and plugin dependencies ??
Posted by Bernd Eckenfels <ec...@zusammenkunft.net>.
Hello,
It would be good if Proxy requests would actually carry the repository URLs or names the request is actually proxied for. I havent seen a proxy which allows configuration in this regard (and therefore I think the protocol does not provide this extra information)
Bernd
> Am 06.05.2014 um 09:07 schrieb Dan Tran <da...@gmail.com>:
>
> 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
>
>
>
>> On Mon, May 5, 2014 at 11:59 PM, Christian Domsch <ma...@landrus.de> 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 <ba...@gmail.com>
>>> wrote:
>>>
>>>> On 6 May 2014 09:21, Dan Tran <da...@gmail.com> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Dan Tran <da...@gmail.com>.
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
On Mon, May 5, 2014 at 11:59 PM, Christian Domsch <ma...@landrus.de> 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 <ba...@gmail.com>
>> wrote:
>>
>> On 6 May 2014 09:21, Dan Tran <da...@gmail.com> 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...
>>>
>>>
>
Re: use separate mirrors for project dendencies and plugin dependencies
??
Posted by Christian Domsch <ma...@landrus.de>.
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 <ba...@gmail.com> wrote:
>
>> On 6 May 2014 09:21, Dan Tran <da...@gmail.com> 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...
>>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Dan Tran <da...@gmail.com>.
Thanks Barrie,
Will see what I can can do.
On Mon, May 5, 2014 at 5:04 PM, Barrie Treloar <ba...@gmail.com> wrote:
> On 6 May 2014 09:21, Dan Tran <da...@gmail.com> 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...
>
Re: use separate mirrors for project dendencies and plugin
dependencies ??
Posted by Barrie Treloar <ba...@gmail.com>.
On 6 May 2014 09:21, Dan Tran <da...@gmail.com> 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...