You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by lastrada <5t...@gmail.com> on 2007/05/01 00:55:22 UTC
Re: Proxying repositories
Arnaud,
Thanks kindly, i upgraded to 2.0.6 and it worked like a charm! Not sure what
you meant by
Arnaud HERITIER wrote:
>
> But be careful, if you mix releases and snapshots, maven 2 will
> automatically update your plugins with snapshots ...
>
Is there an issue here? Could you clarify what you meant? thanks for your
help
rgds,
ls
Arnaud HERITIER wrote:
>
> You have to define a mirror (maven 2.0.5) :
> http://maven.apache.org/guides/mini/guide-mirror-settings.html
>
> <settings>
> .
> .
> <mirrors>
> <mirror>
> <id>internal-repository</id>
> <name>Maven Repository Manager</name>
> <url>http://myhost:8080/archiva/repository/xyz</url>
> <mirrorOf>*</mirrorOf>
> </mirror>
> </mirrors>
> .
> .
> </settings>
>
> But be careful, if you mix releases and snapshots, maven 2 will
> automatically update your plugins with snapshots ...
>
> Arnaud
>
> On 30/04/07, lastrada <5t...@gmail.com> wrote:
>>
>>
>> Thx Wendy,
>>
>> So what I have set up is an Archiva repository with proxies for the N
>> repositories used by the open source project. In my maven settings I have
>> a
>> profile that references the Archiva repository as follows:
>>
>> <profile>
>> <id>Archiva Repository</id>
>> <activation>
>> <activeByDefault>true</activeByDefault>
>> </activation>
>>
>> <repositories>
>> <repository>
>> <id>Archiva</id>
>> <name>Archiva repostiory</name>
>> <url>http://myhost:8080/archiva/repository/xyz
>> </url>
>> <releases>
>> <enabled>true</enabled>
>> </releases>
>> <snapshots>
>> <enabled>true</enabled>
>> </snapshots>
>> </repository>
>> </repositories>
>>
>> <pluginRepositories>
>> <pluginRepository>
>> <id>Archiva</id>
>> <name>Archiva repostiory</name>
>> <url>http://myhost:8080/archiva/repository/xyz
>> </url>
>> <releases>
>> <enabled>false</enabled>
>> </releases>
>> <snapshots>
>> <enabled>true</enabled>
>> </snapshots>
>> </pluginRepository>
>> </pluginRepositories>
>> </profile>
>>
>> I was hoping that all dependency requests made by the os project would
>> now
>> be proxied through Archiva, but it seems to circumvent it and still go
>> straight to the other repositories directly. Is there something else I
>> need
>> to add to make it always defer to archiva? Do i need to set up an http
>> proxy too? Thanks with your help on this
>>
>> rgds,
>>
>> ls
>>
>>
>> Wendy Smoak-3 wrote:
>> >
>> > On 4/27/07, la 5tr4da <5t...@gmail.com> wrote:
>> >> I have a question regarding proxied repositories for open source
>> projects
>> >> using maven and archiva. I would like to build an open source project
>> >> that
>> >> has for example two repositories defined in its pom. I would like to
>> set
>> >> these up as proxies in archiva and have maven retrieve the required
>> >> artifacts via archiva which would then have a cached copy. This would
>> >> allow
>> >> for a pseudo offline build of the project using only the cached
>> artifacts
>> >> in
>> >> archiva. Is this possible, and if so what do I need to do to make this
>> >> happen. Any info on this would be most appreciated.
>> >
>> > Sounds reasonable to me... I do the same thing, including deploying
>> > the older Sun jars that can't be in a public repo to my own 'private'
>> > remote repo.
>> >
>> > It should be fairly straightforward, set up a managed repository and
>> > then a couple of proxied repositories using the buttons at the left.
>> >
>> > Archiva is still under construction, so keep an eye on the dev list to
>> > avoid surprises.
>> >
>> > --
>> > Wendy
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Proxying-repositories-tf3660800.html#a10258113
>> Sent from the archiva-users mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Proxying-repositories-tf3660800.html#a10262027
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Proxying repositories
Posted by lastrada <5t...@gmail.com>.
Thx Nicolas, I'll keep that in mind.
nicolas de loof-2 wrote:
>
> <mirrorOf>* in mirror definition makes maven use the same mirror URL for
> any
> repository/pluginrepository.
>
> If your POM includes some repository dependency with snapshots enabled, it
> will enable request for snapshots on the mirror, so ANY snapshot will be
> accessible.
>
> This can be an issue if you don't specify plugins version for all plugins
> used by your POM
>
> Nico.
>
>
> 2007/5/1, lastrada <5t...@gmail.com>:
>>
>>
>> Arnaud,
>>
>> Thanks kindly, i upgraded to 2.0.6 and it worked like a charm! Not sure
>> what
>> you meant by
>>
>>
>> Arnaud HERITIER wrote:
>> >
>> > But be careful, if you mix releases and snapshots, maven 2 will
>> > automatically update your plugins with snapshots ...
>> >
>>
>> Is there an issue here? Could you clarify what you meant? thanks for your
>> help
>>
>> rgds,
>>
>> ls
>>
>>
>> Arnaud HERITIER wrote:
>> >
>> > You have to define a mirror (maven 2.0.5) :
>> > http://maven.apache.org/guides/mini/guide-mirror-settings.html
>> >
>> > <settings>
>> > .
>> > .
>> > <mirrors>
>> > <mirror>
>> > <id>internal-repository</id>
>> > <name>Maven Repository Manager</name>
>> > <url>http://myhost:8080/archiva/repository/xyz</url>
>> > <mirrorOf>*</mirrorOf>
>> > </mirror>
>> > </mirrors>
>> > .
>> > .
>> > </settings>
>> >
>> > But be careful, if you mix releases and snapshots, maven 2 will
>> > automatically update your plugins with snapshots ...
>> >
>> > Arnaud
>> >
>> > On 30/04/07, lastrada <5t...@gmail.com> wrote:
>> >>
>> >>
>> >> Thx Wendy,
>> >>
>> >> So what I have set up is an Archiva repository with proxies for the N
>> >> repositories used by the open source project. In my maven settings I
>> have
>> >> a
>> >> profile that references the Archiva repository as follows:
>> >>
>> >> <profile>
>> >> <id>Archiva Repository</id>
>> >> <activation>
>> >> <activeByDefault>true</activeByDefault>
>> >> </activation>
>> >>
>> >> <repositories>
>> >> <repository>
>> >> <id>Archiva</id>
>> >> <name>Archiva repostiory</name>
>> >> <url>
>> http://myhost:8080/archiva/repository/xyz
>> >> </url>
>> >> <releases>
>> >> <enabled>true</enabled>
>> >> </releases>
>> >> <snapshots>
>> >> <enabled>true</enabled>
>> >> </snapshots>
>> >> </repository>
>> >> </repositories>
>> >>
>> >> <pluginRepositories>
>> >> <pluginRepository>
>> >> <id>Archiva</id>
>> >> <name>Archiva repostiory</name>
>> >> <url>
>> http://myhost:8080/archiva/repository/xyz
>> >> </url>
>> >> <releases>
>> >> <enabled>false</enabled>
>> >> </releases>
>> >> <snapshots>
>> >> <enabled>true</enabled>
>> >> </snapshots>
>> >> </pluginRepository>
>> >> </pluginRepositories>
>> >> </profile>
>> >>
>> >> I was hoping that all dependency requests made by the os project would
>> >> now
>> >> be proxied through Archiva, but it seems to circumvent it and still go
>> >> straight to the other repositories directly. Is there something else I
>> >> need
>> >> to add to make it always defer to archiva? Do i need to set up an
>> http
>> >> proxy too? Thanks with your help on this
>> >>
>> >> rgds,
>> >>
>> >> ls
>> >>
>> >>
>> >> Wendy Smoak-3 wrote:
>> >> >
>> >> > On 4/27/07, la 5tr4da <5t...@gmail.com> wrote:
>> >> >> I have a question regarding proxied repositories for open source
>> >> projects
>> >> >> using maven and archiva. I would like to build an open source
>> project
>> >> >> that
>> >> >> has for example two repositories defined in its pom. I would like
>> to
>> >> set
>> >> >> these up as proxies in archiva and have maven retrieve the
>> required
>> >> >> artifacts via archiva which would then have a cached copy. This
>> would
>> >> >> allow
>> >> >> for a pseudo offline build of the project using only the cached
>> >> artifacts
>> >> >> in
>> >> >> archiva. Is this possible, and if so what do I need to do to make
>> this
>> >> >> happen. Any info on this would be most appreciated.
>> >> >
>> >> > Sounds reasonable to me... I do the same thing, including deploying
>> >> > the older Sun jars that can't be in a public repo to my own
>> 'private'
>> >> > remote repo.
>> >> >
>> >> > It should be fairly straightforward, set up a managed repository and
>> >> > then a couple of proxied repositories using the buttons at the left.
>> >> >
>> >> > Archiva is still under construction, so keep an eye on the dev list
>> to
>> >> > avoid surprises.
>> >> >
>> >> > --
>> >> > Wendy
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >> http://www.nabble.com/Proxying-repositories-tf3660800.html#a10258113
>> >> Sent from the archiva-users mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Proxying-repositories-tf3660800.html#a10262027
>> Sent from the archiva-users mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Proxying-repositories-tf3660800.html#a10276196
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Proxying repositories
Posted by nicolas de loof <ni...@gmail.com>.
<mirrorOf>* in mirror definition makes maven use the same mirror URL for any
repository/pluginrepository.
If your POM includes some repository dependency with snapshots enabled, it
will enable request for snapshots on the mirror, so ANY snapshot will be
accessible.
This can be an issue if you don't specify plugins version for all plugins
used by your POM
Nico.
2007/5/1, lastrada <5t...@gmail.com>:
>
>
> Arnaud,
>
> Thanks kindly, i upgraded to 2.0.6 and it worked like a charm! Not sure
> what
> you meant by
>
>
> Arnaud HERITIER wrote:
> >
> > But be careful, if you mix releases and snapshots, maven 2 will
> > automatically update your plugins with snapshots ...
> >
>
> Is there an issue here? Could you clarify what you meant? thanks for your
> help
>
> rgds,
>
> ls
>
>
> Arnaud HERITIER wrote:
> >
> > You have to define a mirror (maven 2.0.5) :
> > http://maven.apache.org/guides/mini/guide-mirror-settings.html
> >
> > <settings>
> > .
> > .
> > <mirrors>
> > <mirror>
> > <id>internal-repository</id>
> > <name>Maven Repository Manager</name>
> > <url>http://myhost:8080/archiva/repository/xyz</url>
> > <mirrorOf>*</mirrorOf>
> > </mirror>
> > </mirrors>
> > .
> > .
> > </settings>
> >
> > But be careful, if you mix releases and snapshots, maven 2 will
> > automatically update your plugins with snapshots ...
> >
> > Arnaud
> >
> > On 30/04/07, lastrada <5t...@gmail.com> wrote:
> >>
> >>
> >> Thx Wendy,
> >>
> >> So what I have set up is an Archiva repository with proxies for the N
> >> repositories used by the open source project. In my maven settings I
> have
> >> a
> >> profile that references the Archiva repository as follows:
> >>
> >> <profile>
> >> <id>Archiva Repository</id>
> >> <activation>
> >> <activeByDefault>true</activeByDefault>
> >> </activation>
> >>
> >> <repositories>
> >> <repository>
> >> <id>Archiva</id>
> >> <name>Archiva repostiory</name>
> >> <url>
> http://myhost:8080/archiva/repository/xyz
> >> </url>
> >> <releases>
> >> <enabled>true</enabled>
> >> </releases>
> >> <snapshots>
> >> <enabled>true</enabled>
> >> </snapshots>
> >> </repository>
> >> </repositories>
> >>
> >> <pluginRepositories>
> >> <pluginRepository>
> >> <id>Archiva</id>
> >> <name>Archiva repostiory</name>
> >> <url>
> http://myhost:8080/archiva/repository/xyz
> >> </url>
> >> <releases>
> >> <enabled>false</enabled>
> >> </releases>
> >> <snapshots>
> >> <enabled>true</enabled>
> >> </snapshots>
> >> </pluginRepository>
> >> </pluginRepositories>
> >> </profile>
> >>
> >> I was hoping that all dependency requests made by the os project would
> >> now
> >> be proxied through Archiva, but it seems to circumvent it and still go
> >> straight to the other repositories directly. Is there something else I
> >> need
> >> to add to make it always defer to archiva? Do i need to set up an http
> >> proxy too? Thanks with your help on this
> >>
> >> rgds,
> >>
> >> ls
> >>
> >>
> >> Wendy Smoak-3 wrote:
> >> >
> >> > On 4/27/07, la 5tr4da <5t...@gmail.com> wrote:
> >> >> I have a question regarding proxied repositories for open source
> >> projects
> >> >> using maven and archiva. I would like to build an open source
> project
> >> >> that
> >> >> has for example two repositories defined in its pom. I would like to
> >> set
> >> >> these up as proxies in archiva and have maven retrieve the required
> >> >> artifacts via archiva which would then have a cached copy. This
> would
> >> >> allow
> >> >> for a pseudo offline build of the project using only the cached
> >> artifacts
> >> >> in
> >> >> archiva. Is this possible, and if so what do I need to do to make
> this
> >> >> happen. Any info on this would be most appreciated.
> >> >
> >> > Sounds reasonable to me... I do the same thing, including deploying
> >> > the older Sun jars that can't be in a public repo to my own 'private'
> >> > remote repo.
> >> >
> >> > It should be fairly straightforward, set up a managed repository and
> >> > then a couple of proxied repositories using the buttons at the left.
> >> >
> >> > Archiva is still under construction, so keep an eye on the dev list
> to
> >> > avoid surprises.
> >> >
> >> > --
> >> > Wendy
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Proxying-repositories-tf3660800.html#a10258113
> >> Sent from the archiva-users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Proxying-repositories-tf3660800.html#a10262027
> Sent from the archiva-users mailing list archive at Nabble.com.
>
>