Re: Maven assembly plugin - Proxies not working with mirrors

[Delany]

Sorry not familiar with proxies. Make sure there isn't a bug at
https://issues.apache.org/jira/projects/MNG/issues/MNG-7642?filter=allopenissues
Delany


On Thu, 22 Dec 2022 at 15:34, Abhinav Sharma 
wrote:

> I have tried with maven 3.8.6 as well. Same error comes.
>
> On Thu, 22 Dec, 2022, 19:00 Delany,  wrote:
>
> > Use Maven v3.8.6 if you can Abhinav
> > Delany
> >
> >
> > On Thu, 22 Dec 2022 at 14:17, Abhinav Sharma 
> > wrote:
> >
> > > Hi,
> > > I am using maven 3.8.2 with java 11 in my system, with remotes
> configured
> > > for jfrog artifactory.
> > >
> > > With both mirror and proxy added, mvn is ignoring the proxies and
> failing
> > > to resolve any dependency. How do I set proxies for maven mirrors as
> > well?
> > >
> > > Without a mirror, the maven assembly plugin is not looking in the
> > > configured jfrog repositories for the dependencies. It starts looking
> at
> > > some random repo.
> > >
> > > [INFO] maven-assembly-plugin:3.3.0:single (make-assembly)sample-project
> > ---
> > > Downloading from jvnet-nexus-staging:
> > > http://maven.java.net/content/repositories/staging/
> > > <
> > >
> >
> http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > > >com/example/sample-project/0.0.1-SNAPSHOT
> > > <
> > >
> >
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > > >/maven-metadata.xml
> > > <
> > >
> >
> http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > > >
> > > Downloading from releases.java.net:
> > > http://maven.java.net/content/repositories/releases/
> > > <
> > >
> >
> http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > > >com/example/sample-project/0.0.1-SNAPSHOT
> > > <
> > >
> >
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > > >/maven-metadata.xml
> > > <
> > >
> >
> http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > > >
> > > Downloading from shapshots.java.net:
> > >
> > >
> >
> http://maven.java.net/content/repositories/snapshots/com/example/sample-project/0.0.1-SNAPSHOT/maven-metadata.xml
> > > <
> > >
> >
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > > >
> > >
> > >
> > > I am expecting to access jfrog maven virtual repo with mirror enabled
> > > behind the company proxy, or force assembly plugin to look into the
> > > repositories defined in settings.xml.
> > >
> > > I am using settings.xml file similar to this:
> > >
> > > 
> > > http://maven.apache.org/SETTINGS/1.2.0
> > > http://maven.apache.org/xsd/settings-1.2.0.xsd"; xmlns="
> > > http://maven.apache.org/SETTINGS/1.2.0";
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> > >   
> > > 
> > >   username
> > >   password
> > >   central
> > > 
> > > 
> > >   username
> > >   password
> > >   snapshots
> > > 
> > >   
> > >   
> > > 
> > >   *
> > >   project-repo
> > >   https://company.jfrog.io/artifactory/project-repo
> > >   project-repo
> > > 
> > >   
> > >   
> > > 
> > >   
> > > 
> > >   
> > > false
> > >   
> > >   central
> > >   project-repo
> > >   https://company.jfrog.io/artifactory/project-repo
> > > 
> > > 
> > >   
> > >   snapshots
> > >   project-repo
> > >   https://company.jfrog.io/artifactory/project-repo
> > > 
> > >   
> > >   
> > > 
> > >   
> > > false
> > >   
> > >   central
> > >   project-repo
> > >   https://company.jfrog.io/artifactory/project-repo
> > > 
> > > 
> > >   
> > >   snapshots
> > >   project-repo
> > >   https://company.jfrog.io/artifactory/project-repo
> > > 
> > >   
> > >   artifactory
> > > 
> > >   
> > >   
> > > artifactory
> > >   
> > >  
> > > 
> > > jfrog-proxy
> > > true
> > > https
> > > proxyhost
> > > proxyport
> > >   
> > > 
> > > 
> > >
> >
>

Re: Maven assembly plugin - Proxies not working with mirrors

[Abhinav Sharma]

I have tried with maven 3.8.6 as well. Same error comes.

On Thu, 22 Dec, 2022, 19:00 Delany,  wrote:

> Use Maven v3.8.6 if you can Abhinav
> Delany
>
>
> On Thu, 22 Dec 2022 at 14:17, Abhinav Sharma 
> wrote:
>
> > Hi,
> > I am using maven 3.8.2 with java 11 in my system, with remotes configured
> > for jfrog artifactory.
> >
> > With both mirror and proxy added, mvn is ignoring the proxies and failing
> > to resolve any dependency. How do I set proxies for maven mirrors as
> well?
> >
> > Without a mirror, the maven assembly plugin is not looking in the
> > configured jfrog repositories for the dependencies. It starts looking at
> > some random repo.
> >
> > [INFO] maven-assembly-plugin:3.3.0:single (make-assembly)sample-project
> ---
> > Downloading from jvnet-nexus-staging:
> > http://maven.java.net/content/repositories/staging/
> > <
> >
> http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > >com/example/sample-project/0.0.1-SNAPSHOT
> > <
> >
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > >/maven-metadata.xml
> > <
> >
> http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > >
> > Downloading from releases.java.net:
> > http://maven.java.net/content/repositories/releases/
> > <
> >
> http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > >com/example/sample-project/0.0.1-SNAPSHOT
> > <
> >
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > >/maven-metadata.xml
> > <
> >
> http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > >
> > Downloading from shapshots.java.net:
> >
> >
> http://maven.java.net/content/repositories/snapshots/com/example/sample-project/0.0.1-SNAPSHOT/maven-metadata.xml
> > <
> >
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> > >
> >
> >
> > I am expecting to access jfrog maven virtual repo with mirror enabled
> > behind the company proxy, or force assembly plugin to look into the
> > repositories defined in settings.xml.
> >
> > I am using settings.xml file similar to this:
> >
> > 
> > http://maven.apache.org/SETTINGS/1.2.0
> > http://maven.apache.org/xsd/settings-1.2.0.xsd"; xmlns="
> > http://maven.apache.org/SETTINGS/1.2.0";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> >   
> > 
> >   username
> >   password
> >   central
> > 
> > 
> >   username
> >   password
> >   snapshots
> > 
> >   
> >   
> > 
> >   *
> >   project-repo
> >   https://company.jfrog.io/artifactory/project-repo
> >   project-repo
> > 
> >   
> >   
> > 
> >   
> > 
> >   
> > false
> >   
> >   central
> >   project-repo
> >   https://company.jfrog.io/artifactory/project-repo
> > 
> > 
> >   
> >   snapshots
> >   project-repo
> >   https://company.jfrog.io/artifactory/project-repo
> > 
> >   
> >   
> > 
> >   
> > false
> >   
> >   central
> >   project-repo
> >   https://company.jfrog.io/artifactory/project-repo
> > 
> > 
> >   
> >   snapshots
> >   project-repo
> >   https://company.jfrog.io/artifactory/project-repo
> > 
> >   
> >   artifactory
> > 
> >   
> >   
> > artifactory
> >   
> >  
> > 
> > jfrog-proxy
> > true
> > https
> > proxyhost
> > proxyport
> >   
> > 
> > 
> >
>

Re: Maven assembly plugin - Proxies not working with mirrors

[Delany]

Use Maven v3.8.6 if you can Abhinav
Delany


On Thu, 22 Dec 2022 at 14:17, Abhinav Sharma 
wrote:

> Hi,
> I am using maven 3.8.2 with java 11 in my system, with remotes configured
> for jfrog artifactory.
>
> With both mirror and proxy added, mvn is ignoring the proxies and failing
> to resolve any dependency. How do I set proxies for maven mirrors as well?
>
> Without a mirror, the maven assembly plugin is not looking in the
> configured jfrog repositories for the dependencies. It starts looking at
> some random repo.
>
> [INFO] maven-assembly-plugin:3.3.0:single (make-assembly)sample-project ---
> Downloading from jvnet-nexus-staging:
> http://maven.java.net/content/repositories/staging/
> <
> http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> >com/example/sample-project/0.0.1-SNAPSHOT
> <
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> >/maven-metadata.xml
> <
> http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> >
> Downloading from releases.java.net:
> http://maven.java.net/content/repositories/releases/
> <
> http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> >com/example/sample-project/0.0.1-SNAPSHOT
> <
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> >/maven-metadata.xml
> <
> http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> >
> Downloading from shapshots.java.net:
>
> http://maven.java.net/content/repositories/snapshots/com/example/sample-project/0.0.1-SNAPSHOT/maven-metadata.xml
> <
> http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml
> >
>
>
> I am expecting to access jfrog maven virtual repo with mirror enabled
> behind the company proxy, or force assembly plugin to look into the
> repositories defined in settings.xml.
>
> I am using settings.xml file similar to this:
>
> 
> http://maven.apache.org/SETTINGS/1.2.0
> http://maven.apache.org/xsd/settings-1.2.0.xsd"; xmlns="
> http://maven.apache.org/SETTINGS/1.2.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>   
> 
>   username
>   password
>   central
> 
> 
>   username
>   password
>   snapshots
> 
>   
>   
> 
>   *
>   project-repo
>   https://company.jfrog.io/artifactory/project-repo
>   project-repo
> 
>   
>   
> 
>   
> 
>   
> false
>   
>   central
>   project-repo
>   https://company.jfrog.io/artifactory/project-repo
> 
> 
>   
>   snapshots
>   project-repo
>   https://company.jfrog.io/artifactory/project-repo
> 
>   
>   
> 
>   
> false
>   
>   central
>   project-repo
>   https://company.jfrog.io/artifactory/project-repo
> 
> 
>   
>   snapshots
>   project-repo
>   https://company.jfrog.io/artifactory/project-repo
> 
>   
>   artifactory
> 
>   
>   
> artifactory
>   
>  
> 
> jfrog-proxy
> true
> https
> proxyhost
> proxyport
>   
> 
> 
>

Maven assembly plugin - Proxies not working with mirrors

[Abhinav Sharma]

Hi,
I am using maven 3.8.2 with java 11 in my system, with remotes configured
for jfrog artifactory.

With both mirror and proxy added, mvn is ignoring the proxies and failing
to resolve any dependency. How do I set proxies for maven mirrors as well?

Without a mirror, the maven assembly plugin is not looking in the
configured jfrog repositories for the dependencies. It starts looking at
some random repo.

[INFO] maven-assembly-plugin:3.3.0:single (make-assembly)sample-project ---
Downloading from jvnet-nexus-staging:
http://maven.java.net/content/repositories/staging/
<http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml>com/example/sample-project/0.0.1-SNAPSHOT
<http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml>/maven-metadata.xml
<http://maven.java.net/content/repositories/staging/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml>
Downloading from releases.java.net:
http://maven.java.net/content/repositories/releases/
<http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml>com/example/sample-project/0.0.1-SNAPSHOT
<http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml>/maven-metadata.xml
<http://maven.java.net/content/repositories/releases/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml>
Downloading from shapshots.java.net:
http://maven.java.net/content/repositories/snapshots/com/example/sample-project/0.0.1-SNAPSHOT/maven-metadata.xml
<http://maven.java.net/content/repositories/snapshots/com/infosys/fbp/platform/fbp-parent-pom/1.5-SNAPSHOT/maven-metadata.xml>


I am expecting to access jfrog maven virtual repo with mirror enabled
behind the company proxy, or force assembly plugin to look into the
repositories defined in settings.xml.

I am using settings.xml file similar to this:


http://maven.apache.org/SETTINGS/1.2.0
http://maven.apache.org/xsd/settings-1.2.0.xsd"; xmlns="
http://maven.apache.org/SETTINGS/1.2.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  

  username
  password
  central


  username
  password
  snapshots

  
  

  *
  project-repo
  https://company.jfrog.io/artifactory/project-repo
  project-repo

  
  

  

  
false
  
  central
  project-repo
  https://company.jfrog.io/artifactory/project-repo


  
  snapshots
  project-repo
  https://company.jfrog.io/artifactory/project-repo

  
  

  
false
  
  central
  project-repo
  https://company.jfrog.io/artifactory/project-repo


  
  snapshots
  project-repo
  https://company.jfrog.io/artifactory/project-repo

  
  artifactory

  
  
artifactory
  
 

jfrog-proxy
true
https
proxyhost
proxyport
  

RE: request for documentation update about mirrors

[mark.yagnatinsky]

True, it is "just a file".  It was actually my first idea, before I emailed 
this list.  But though it's "just a file", it's a file I'd have to keep editing 
every time I updated maven.
It's likewise a file everyone else on the team needs to be taught to edit every 
time they update maven.

Fun fact: the way I discovered this issue is via an accidental maven update.  I 
was using the maven bundled with my IDE.  I then updated my IDE.
The release "highlights" page for the IDE did not even mention it comes bundled 
with a new maven version.

So, another way to describe editing this file is "maintaining our own private 
fork of maven".
As far as forks go, it's a pretty mild one.  It doesn't require us to compile 
maven from source, or anything scary like that.

But it's still a fork.  And it's still annoying.  I'm looking for something 
more like this:
https://stackoverflow.com/questions/67001968/how-to-disable-maven-blocking-external-http-repositores/68394404#68394404

(in fact, maybe that's exactly what I'm looking for.)
_
“This message is for information purposes only, it is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is not intended for retail customer use. Intended for 
recipient only. This message is subject to the terms at: 
www.barclays.com/emaildisclaimer.

For important disclosures, please see: 
www.barclays.com/salesandtradingdisclaimer regarding market commentary from 
Barclays Sales and/or Trading, who are active market participants; 
https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
 regarding our standard terms for the Investment Bank of Barclays where we 
trade with you in principal-to-principal wholesale markets transactions; and in 
respect of Barclays Research, including disclosures relating to specific 
issuers, please see http://publicresearch.barclays.com.”  
_
If you are incorporated or operating in Australia, please see 
https://www.home.barclays/disclosures/importantapacdisclosures.html for 
important disclosure.
_
How we use personal information  see our privacy notice 
https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html 
_

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: request for documentation update about mirrors

[Bernd Eckenfels]

Well, it’s just a file to edit.


--
http://bernd.eckenfels.net

Von: mark.yagnatin...@barclays.com.INVALID 

Gesendet: Thursday, December 9, 2021 6:22:46 AM
An: users@maven.apache.org 
Betreff: RE: request for documentation update about mirrors

> But if you insist, I heared you can remove the blocked tag in your maven/conf 
> settings.. ;)
But I can't, right?  I'd have edit the global settings file bundled with maven 
itself.
Or no?

_
?This message is for information purposes only, it is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is not intended for retail customer use. Intended for 
recipient only. This message is subject to the terms at: 
www.barclays.com/emaildisclaimer<http://www.barclays.com/emaildisclaimer>.

For important disclosures, please see: 
www.barclays.com/salesandtradingdisclaimer<http://www.barclays.com/salesandtradingdisclaimer>
 regarding market commentary from Barclays Sales and/or Trading, who are active 
market participants; 
https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
 regarding our standard terms for the Investment Bank of Barclays where we 
trade with you in principal-to-principal wholesale markets transactions; and in 
respect of Barclays Research, including disclosures relating to specific 
issuers, please see http://publicresearch.barclays.com.?
_
If you are incorporated or operating in Australia, please see 
https://www.home.barclays/disclosures/importantapacdisclosures.html for 
important disclosure.
_
How we use personal information  see our privacy notice 
https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html
_

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: request for documentation update about mirrors

[mark.yagnatinsky]

> But if you insist, I heared you can remove the blocked tag in your maven/conf 
> settings.. ;) 
But I can't, right?  I'd have edit the global settings file bundled with maven 
itself.
Or no?

_
“This message is for information purposes only, it is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is not intended for retail customer use. Intended for 
recipient only. This message is subject to the terms at: 
www.barclays.com/emaildisclaimer.

For important disclosures, please see: 
www.barclays.com/salesandtradingdisclaimer regarding market commentary from 
Barclays Sales and/or Trading, who are active market participants; 
https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
 regarding our standard terms for the Investment Bank of Barclays where we 
trade with you in principal-to-principal wholesale markets transactions; and in 
respect of Barclays Research, including disclosures relating to specific 
issuers, please see http://publicresearch.barclays.com.”  
_
If you are incorporated or operating in Australia, please see 
https://www.home.barclays/disclosures/importantapacdisclosures.html for 
important disclosure.
_
How we use personal information  see our privacy notice 
https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html 
_

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: request for documentation update about mirrors

[Bernd Eckenfels]

Hello,

I would define a single caching mirror repository (and maybe exclude all 
internal repositories which are already HTTPS). The mirror applies 
automatically to all repos, you don’t need to configure them individually.

And you should really really start on enabling HTTPS. It is imho no problem if 
some POM define a central with http, your settings.xml for that Repo-Id (and 
the mirror anyway) will have precedence.

But if you insist, I heared you can remove the blocked tag in your maven/conf 
settings.. ;) just be aware that most likely your compliance and network 
departments will love you for getting rid of a insecure intrusion vector in 
your supply chain.

Gruss
Bernd


--
http://bernd.eckenfels.net

Von: mark.yagnatin...@barclays.com.INVALID 

Gesendet: Wednesday, December 8, 2021 4:07:31 PM
An: users@maven.apache.org 
Betreff: request for documentation update about mirrors

I hope this is the right mailing list; if I not, would appreciate a redirect.
In the release notes for maven 3.8.1, here:
https://maven.apache.org/docs/3.8.1/release-notes.html
There is a helpfully titled section "How to fix when I get a HTTP repository 
blocked?"
https://maven.apache.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked
It mentions 2 options:

* Update to a newer version of the artifact you're fetching, which is 
presumably available over https

* Define a mirror in your settings, which links to this page:
https://maven.apache.org/guides/mini/guide-mirror-settings.html

The first option is not helpful, since we are using a settings.xml which lists 
many http-only repositories, including one with an id of "central".
Since these are all on our internal network, the usual concerns about security 
don't apply, or at least not in full force like they would on the public 
internet.

(We don't let maven access the public internet.  If a fellow coworker is trying 
to hijack my maven downloads, I suppose they might succeed.  We'll keep taking 
that risk for now :))

That brings us to the second option: create a mirror.  Unfortunately, the 
linked page doesn't even mention anything about blocking and unblocking.
In fact, I can't find the  tag documented anywhere, though perhaps I'm 
looking in the wrong places.

What I'd ideally like to see is a way to "undo" the mirror defined in the 
global settings in one fell swoop.
That is, I do NOT want to go through the repos listed in our repositories, and 
then tediously create a mirror for each of them, one by one, and then remember 
to keep the two lists in sync if anything changes.

So: can the documentation be updated to mention anything about unblocking, and 
is there any way to do what I want?

Thanks,
Mark.

_
?This message is for information purposes only, it is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is not intended for retail customer use. Intended for 
recipient only. This message is subject to the terms at: 
www.barclays.com/emaildisclaimer<http://www.barclays.com/emaildisclaimer>.

For important disclosures, please see: 
www.barclays.com/salesandtradingdisclaimer<http://www.barclays.com/salesandtradingdisclaimer>
 regarding market commentary from Barclays Sales and/or Trading, who are active 
market participants; 
https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
 regarding our standard terms for the Investment Bank of Barclays where we 
trade with you in principal-to-principal wholesale markets transactions; and in 
respect of Barclays Research, including disclosures relating to specific 
issuers, please see http://publicresearch.barclays.com.?
_
If you are incorporated or operating in Australia, please see 
https://www.home.barclays/disclosures/importantapacdisclosures.html for 
important disclosure.
_
How we use personal information  see our privacy notice 
https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html
_

Re: request for documentation update about mirrors

[Niranjan Rao]

It sounds like you have multiple repositories defined on same nexus 
instance. This is similar to setup we have. We have repositories for 
third party libraries we use as well as a mirror of maven central for 
the stuff we need.


Key difference between the setup you have and my setup is we have one 
(internally) public repository and other repositories are member of that 
repository. All the developers always use that public repository rather 
than adding multiple repository.


Repositories are managed by appropriate people who care about what 
contents get into repository.


If it helps I have following entries in my settings.xml

 
    
  nexus
  *
  https:///nexus/repository//
    
  

Maven channels everything through nexus and nexus serves it based on rules.

Regards,

Niranjan

On 12/8/21 4:25 PM, mark.yagnatin...@barclays.com.INVALID wrote:

Sorry for broken threading; I wasn't subscribed to the mailing list so I never 
got your reply; not sure how to fix it now.  Now I'm subscribed.

Yes, we are using nexus.  One of our nexus servers is even using HTTPS.  The 
rest are not.
As for why we have "many" ... I'm not entirely sure.  It was like that when I 
got here.
I could ask around, but I'm not sure how much it matters.  Could be

* Historical reasons

* Bureaucratic reasons

* Or maybe even very good reasons that I happen to not know.
As it happens, many of these "separate" nexus repositories are on the same 
server, but maven treats them all as if they are distinct, because they have different 
paths.  E.g. one might be
http://nexus.example.com:8080/nexus/content/groups/main/
while another might be
http://nexus.example.com:8080/nexus/content/repositories/UPLOAD-EXTERNAL-RELEASES/

Not sure if any of this answers your question.

_
“This message is for information purposes only, it is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is not intended for retail customer use. Intended for 
recipient only. This message is subject to the terms at: 
www.barclays.com/emaildisclaimer.

For important disclosures, please see: 
www.barclays.com/salesandtradingdisclaimer regarding market commentary from 
Barclays Sales and/or Trading, who are active market participants; 
https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
 regarding our standard terms for the Investment Bank of Barclays where we 
trade with you in principal-to-principal wholesale markets transactions; and in 
respect of Barclays Research, including disclosures relating to specific 
issuers, please see http://publicresearch.barclays.com.”
_
If you are incorporated or operating in Australia, please see 
https://www.home.barclays/disclosures/importantapacdisclosures.html for 
important disclosure.
_
How we use personal information  see our privacy notice 
https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html
_




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: request for documentation update about mirrors

[Greg Chabala]

I can't speak to your question about disabling the https requirement,
though my guess is that will be impossible and/or unpopular, likely by
design. If you could just turn it off, some people would just turn it off,
which defeats the purpose.

The root of my questions is that if your Nexus is configured properly,
https shouldn't be an issue to begin with.

You should get in touch with your Nexus admin, get familiar with the
historical and/or bureaucratic reasons for what exists, and get one of them
configured to meet your needs, e.g. serving over https, a group that
contains the aggregate of all the repos your settings.xml is referencing.
They are likely already familiar with the need for https access.

On Wed, Dec 8, 2021 at 6:26 PM 
wrote:

> Sorry for broken threading; I wasn't subscribed to the mailing list so I
> never got your reply; not sure how to fix it now.  Now I'm subscribed.
>
> Yes, we are using nexus.  One of our nexus servers is even using HTTPS.
> The rest are not.
> As for why we have "many" ... I'm not entirely sure.  It was like that
> when I got here.
> I could ask around, but I'm not sure how much it matters.  Could be
>
> * Historical reasons
>
> * Bureaucratic reasons
>
> * Or maybe even very good reasons that I happen to not know.
> As it happens, many of these "separate" nexus repositories are on the same
> server, but maven treats them all as if they are distinct, because they
> have different paths.  E.g. one might be
> http://nexus.example.com:8080/nexus/content/groups/main/
> while another might be
>
> http://nexus.example.com:8080/nexus/content/repositories/UPLOAD-EXTERNAL-RELEASES/
>
> Not sure if any of this answers your question.
>
>
> _
> “This message is for information purposes only, it is not a
> recommendation, advice, offer or solicitation to buy or sell a product or
> service nor an official confirmation of any transaction. It is directed at
> persons who are professionals and is not intended for retail customer use.
> Intended for recipient only. This message is subject to the terms at:
> www.barclays.com/emaildisclaimer.
>
> For important disclosures, please see:
> www.barclays.com/salesandtradingdisclaimer regarding market commentary
> from Barclays Sales and/or Trading, who are active market participants;
> https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
> regarding our standard terms for the Investment Bank of Barclays where we
> trade with you in principal-to-principal wholesale markets transactions;
> and in respect of Barclays Research, including disclosures relating to
> specific issuers, please see http://publicresearch.barclays.com.”
>
> _
> If you are incorporated or operating in Australia, please see
> https://www.home.barclays/disclosures/importantapacdisclosures.html for
> important disclosure.
>
> _
> How we use personal information  see our privacy notice
> https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html
>
> _
>

RE: request for documentation update about mirrors

[mark.yagnatinsky]

Sorry for broken threading; I wasn't subscribed to the mailing list so I never 
got your reply; not sure how to fix it now.  Now I'm subscribed.

Yes, we are using nexus.  One of our nexus servers is even using HTTPS.  The 
rest are not.
As for why we have "many" ... I'm not entirely sure.  It was like that when I 
got here.
I could ask around, but I'm not sure how much it matters.  Could be

* Historical reasons

* Bureaucratic reasons

* Or maybe even very good reasons that I happen to not know.
As it happens, many of these "separate" nexus repositories are on the same 
server, but maven treats them all as if they are distinct, because they have 
different paths.  E.g. one might be
http://nexus.example.com:8080/nexus/content/groups/main/
while another might be
http://nexus.example.com:8080/nexus/content/repositories/UPLOAD-EXTERNAL-RELEASES/

Not sure if any of this answers your question.

_
“This message is for information purposes only, it is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is not intended for retail customer use. Intended for 
recipient only. This message is subject to the terms at: 
www.barclays.com/emaildisclaimer.

For important disclosures, please see: 
www.barclays.com/salesandtradingdisclaimer regarding market commentary from 
Barclays Sales and/or Trading, who are active market participants; 
https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
 regarding our standard terms for the Investment Bank of Barclays where we 
trade with you in principal-to-principal wholesale markets transactions; and in 
respect of Barclays Research, including disclosures relating to specific 
issuers, please see http://publicresearch.barclays.com.”  
_
If you are incorporated or operating in Australia, please see 
https://www.home.barclays/disclosures/importantapacdisclosures.html for 
important disclosure.
_
How we use personal information  see our privacy notice 
https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html 
_

Re: request for documentation update about mirrors

[Greg Chabala]

>
> since we are using a settings.xml which lists many http-only repositories,
> including one with an id of "central".
> Since these are all on our internal network
>

 We don't let maven access the public internet


As your repositories are all internal, and you don't let maven connect to
the public internet, what are you using to host internal repos? Nexus,
Artifactory? Either should provide https out of the box.

Also, why 'many' repositories? Your internal repository manager ought to
cache, mirror and aggregate, and be the single repo you need to reference.

Greg Chabala

On Wed, Dec 8, 2021 at 11:39 AM 
wrote:

> I hope this is the right mailing list; if I not, would appreciate a
> redirect.
> In the release notes for maven 3.8.1, here:
> https://maven.apache.org/docs/3.8.1/release-notes.html
> There is a helpfully titled section "How to fix when I get a HTTP
> repository blocked?"
>
> https://maven.apache.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked
> It mentions 2 options:
>
> * Update to a newer version of the artifact you're fetching, which
> is presumably available over https
>
> * Define a mirror in your settings, which links to this page:
> https://maven.apache.org/guides/mini/guide-mirror-settings.html
>
> The first option is not helpful, since we are using a settings.xml which
> lists many http-only repositories, including one with an id of "central".
> Since these are all on our internal network, the usual concerns about
> security don't apply, or at least not in full force like they would on the
> public internet.
>
> (We don't let maven access the public internet.  If a fellow coworker is
> trying to hijack my maven downloads, I suppose they might succeed.  We'll
> keep taking that risk for now :))
>
> That brings us to the second option: create a mirror.  Unfortunately, the
> linked page doesn't even mention anything about blocking and unblocking.
> In fact, I can't find the  tag documented anywhere, though
> perhaps I'm looking in the wrong places.
>
> What I'd ideally like to see is a way to "undo" the mirror defined in the
> global settings in one fell swoop.
> That is, I do NOT want to go through the repos listed in our repositories,
> and then tediously create a mirror for each of them, one by one, and then
> remember to keep the two lists in sync if anything changes.
>
> So: can the documentation be updated to mention anything about unblocking,
> and is there any way to do what I want?
>
> Thanks,
> Mark.
>
>
> _
> “This message is for information purposes only, it is not a
> recommendation, advice, offer or solicitation to buy or sell a product or
> service nor an official confirmation of any transaction. It is directed at
> persons who are professionals and is not intended for retail customer use.
> Intended for recipient only. This message is subject to the terms at:
> www.barclays.com/emaildisclaimer.
>
> For important disclosures, please see:
> www.barclays.com/salesandtradingdisclaimer regarding market commentary
> from Barclays Sales and/or Trading, who are active market participants;
> https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
> regarding our standard terms for the Investment Bank of Barclays where we
> trade with you in principal-to-principal wholesale markets transactions;
> and in respect of Barclays Research, including disclosures relating to
> specific issuers, please see http://publicresearch.barclays.com.”
>
> _
> If you are incorporated or operating in Australia, please see
> https://www.home.barclays/disclosures/importantapacdisclosures.html for
> important disclosure.
>
> _
> How we use personal information  see our privacy notice
> https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html
>
> _
>

request for documentation update about mirrors

[mark.yagnatinsky]

I hope this is the right mailing list; if I not, would appreciate a redirect.
In the release notes for maven 3.8.1, here:
https://maven.apache.org/docs/3.8.1/release-notes.html
There is a helpfully titled section "How to fix when I get a HTTP repository 
blocked?"
https://maven.apache.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked
It mentions 2 options:

* Update to a newer version of the artifact you're fetching, which is 
presumably available over https

* Define a mirror in your settings, which links to this page:
https://maven.apache.org/guides/mini/guide-mirror-settings.html

The first option is not helpful, since we are using a settings.xml which lists 
many http-only repositories, including one with an id of "central".
Since these are all on our internal network, the usual concerns about security 
don't apply, or at least not in full force like they would on the public 
internet.

(We don't let maven access the public internet.  If a fellow coworker is trying 
to hijack my maven downloads, I suppose they might succeed.  We'll keep taking 
that risk for now :))

That brings us to the second option: create a mirror.  Unfortunately, the 
linked page doesn't even mention anything about blocking and unblocking.
In fact, I can't find the  tag documented anywhere, though perhaps I'm 
looking in the wrong places.

What I'd ideally like to see is a way to "undo" the mirror defined in the 
global settings in one fell swoop.
That is, I do NOT want to go through the repos listed in our repositories, and 
then tediously create a mirror for each of them, one by one, and then remember 
to keep the two lists in sync if anything changes.

So: can the documentation be updated to mention anything about unblocking, and 
is there any way to do what I want?

Thanks,
Mark.

_
“This message is for information purposes only, it is not a recommendation, 
advice, offer or solicitation to buy or sell a product or service nor an 
official confirmation of any transaction. It is directed at persons who are 
professionals and is not intended for retail customer use. Intended for 
recipient only. This message is subject to the terms at: 
www.barclays.com/emaildisclaimer.

For important disclosures, please see: 
www.barclays.com/salesandtradingdisclaimer regarding market commentary from 
Barclays Sales and/or Trading, who are active market participants; 
https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html
 regarding our standard terms for the Investment Bank of Barclays where we 
trade with you in principal-to-principal wholesale markets transactions; and in 
respect of Barclays Research, including disclosures relating to specific 
issuers, please see http://publicresearch.barclays.com.”  
_
If you are incorporated or operating in Australia, please see 
https://www.home.barclays/disclosures/importantapacdisclosures.html for 
important disclosure.
_
How we use personal information  see our privacy notice 
https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html 
_

Transitive import-scoped dependencies are not resolved using mirrors

[Christian Rösch]

Hi,

my question is related to https://issues.apache.org/jira/browse/MNG-4347 
but also to somehow to this thread 
https://lists.apache.org/thread.html/bdefb134c4b605af2e15045500af3685e4281eb3513a7b6a29ff1778@1310154622@%3Cusers.maven.apache.org%3E


Given is:

- project A has project B as dependency
- project B has project C as dependency, while C is pom-packed -> 
scope=import and also as dependency
- project A, B and C are SNAPSHOT versions
- all three POMs point the user to two repositories: repository-a 
releases-enabled=true, snapshots-enabled=false and repository-b 
releases-enabled=false, snapshots-enabled=true
- the settings file of the user points all repositories to a mirror

When $ mvn -U clean verify is run in project A

Maven gives the following error:

[ERROR] Failed to execute goal on project test.a: Could not resolve 
dependencies for project test:test.a:jar:1.0-SNAPSHOT: Failed to collect 
dependencies at test:test.b:jar:1.0-SNAPSHOT: Failed to read artifact 
descriptor for test:test.b:jar:1.0-SNAPSHOT: Could not find artifact 
test:test.c:pom:1.0-SNAPSHOT -> [Help 1]


While downloading it doesn't even try a request for dependency C at the 
mirror or one of the repositories (double checked with a proxy).

If the mirror definition gets modified to 
*,!repository-b

everything works. The SNAPSHOTs are requested (and found) and the build 
is a SUCCESS.


Error happens with Maven 3.6.0 and does not happen with 3.1.1 (3.1.1 is 
as far as I know the last version where this constellation is working).

Does multiple repositories to one mirror still work like explained in 
the question - it just replaces the URL in the repo-definitions but the 
repo-definitions remain?

Is there any other explanation for that behavior or is it just a bug?


-- Christian

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Resolver question regarding CollectRequest and mirrors

[Tamás Cservenák]

Howdy

Without deeply plunging in the problem, just figured you can look for code
examples here too

https://github.com/sonatype/sisu-maven-bridge/blob/master/bridge/src/main/java/org/sonatype/sisu/maven/bridge/support/settings/DefaultMavenSettings.java

As you may spot something your code missed.

HTH,
T

On Sat, Mar 18, 2017 at 12:08 AM Laird Nelson  wrote:

> On Fri, Mar 17, 2017 at 4:01 PM Laird Nelson  wrote:
>
> > Nevertheless, I note that when I call
> repositorySystem.resolveDependencies(repositorySystemSession,
> > dependencyRequest) (already excerpted above), the mirrors I've so
> > painstakingly installed into the session do not get used.
> >
>
> I wonder if that's what this method is for?  Hmm.
>
>
> https://maven.apache.org/resolver/apidocs/org/eclipse/aether/RepositorySystem.html#newResolutionRepositories(org.eclipse.aether.RepositorySystemSession,%20java.util.List)
>
> Best,
> Laird
>
-- 
Thanks,
~t~

Re: Maven Resolver question regarding CollectRequest and mirrors

[Laird Nelson]

On Fri, Mar 17, 2017 at 4:01 PM Laird Nelson  wrote:

> Nevertheless, I note that when I call 
> repositorySystem.resolveDependencies(repositorySystemSession,
> dependencyRequest) (already excerpted above), the mirrors I've so
> painstakingly installed into the session do not get used.
>

I wonder if that's what this method is for?  Hmm.

https://maven.apache.org/resolver/apidocs/org/eclipse/aether/RepositorySystem.html#newResolutionRepositories(org.eclipse.aether.RepositorySystemSession,%20java.util.List)

Best,
Laird

Maven Resolver question regarding CollectRequest and mirrors

[Laird Nelson]

I'm proceeding further on my journey to do damage with the maven-resolver
series of projects (https://maven.apache.org/resolver/) in a way that looks
like Maven but doesn't use Maven itself (only these dependency resolution
components).

As I mentioned in some earlier posts to this list, I'm following the
general recipes laid out by the (now obsolete, but substantially OK) Aether
demos (
https://github.com/eclipse/aether-demo/tree/master/aether-demo-snippets/src/main/java/org/eclipse/aether/examples
).

In one of those examples, you put together a CollectRequest and ask a
RepositorySystem to resolve dependencies.  It goes something like this:

  final CollectRequest collectRequest = new CollectRequest();
  collectRequest.setRoot(new Dependency(artifact, JavaScopes.COMPILE));
  collectRequest.setRepositories(Collections.singletonList(mavenCentral));
// <-- I have questions here
  final DependencyRequest dependencyRequest = new
DependencyRequest(collectRequest, classpathFilter);
  final DependencyResult dependencyResult =
repositorySystem.resolveDependencies(repositorySystemSession,
dependencyRequest);

As part of setting this whole scaffolding up, I've found the global
settings file and the user settings file, and, using the maven-settings and
maven-settings-builder projects, figured out how to get a Settings object
in my hand in the same way that Maven "proper" does it.  From there, I can
get its mirrors, and so, it seems to me, I should be able to smash them
into my repositorySystemSession:

  final Collection mirrors = settings.getMirrors();
  if (mirrors != null && !mirrors.isEmpty()) {
final DefaultMirrorSelector mirrorSelector = new
DefaultMirrorSelector();
for (final Mirror mirror : mirrors) {
  assert mirror != null;
  mirrorSelector.add(mirror.getId(), mirror.getUrl(),
mirror.getLayout(), false, mirror.getMirrorOf(),
mirror.getMirrorOfLayouts());
}
repositorySystemSession.setMirrorSelector(mirrorSelector); // <--
shouldn't this cause mirrors to be used transparently?
  }

My assumption would be that this MirrorSelector would be used transparently
somehow by the resolveDependencies() method, which, of course, has access
to the repositorySystemSession containing the MirrorSelector I built.

Nevertheless, I note that when I call
repositorySystem.resolveDependencies(repositorySystemSession,
dependencyRequest) (already excerpted above), the mirrors I've so
painstakingly installed into the session do not get used.

Am I doing something wrong?  How can I get my repository ecosystem I'm
building here to use mirrors?

Thanks,
Best,
Laird

Maven Resolver question re: local repo and mirrors

[Laird Nelson]

Hello; I'm putting together a client, I guess, of the Maven Artifact
Resolver APIs (https://maven.apache.org/resolver/maven-resolver-api/).

I am trying to make my client be as Maven-like as possible.  So I'm using,
among other things, MavenRepositorySystemUtils.  I can, of course, go into
more details if needed; this is intended to be a shorthand that says I
mostly know what I'm doing.  :-)

(Another way to put this is I am following recipes you can find here (
https://github.com/eclipse/aether-demo/tree/master/aether-demo-snippets/src/main/java/org/eclipse/aether/examples),
bearing in mind that Aether has of course become maven-resolver
<https://lairdnelson.wordpress.com/2017/03/06/maven-and-the-project-formerly-known-as-aether/>,
so obviously there are a few tweaks here and there.)

I understand most of this, but is there a component I can use that includes
the automagic usage of mirrors etc. from a Maven ~/.m2/settings.xml file?
My sense is if I just do:

final LocalRepository localRepository = new
LocalRepository("target/local-repository");
final LocalRepositoryManager localRepositoryManager =
repositorySystem.newLocalRepositoryManager(repositorySystemSession,
localRepository);
repositorySystemSession.setLocalRepositoryManager(localRepositoryManager);

…and:

final RemoteRepository mavenCentral = new
RemoteRepository.Builder("central", "default", "
http://central.maven.org/maven2/";).build();
// now use this and localRepository in a CollectRequest or the like

…I'm not getting the (useful) magic of a Maven settings.xml file.  I
wouldn't really expect to, either, since this is just usage of the
project-formerly-known-as-Aether, not some deep Maven integration.

What is the recipe to include this as well?  I had a brief look in Maven
core—think an explorer encountering a dark ominous cave with a flaming
torch running out of fuel, backing away slowly—but wasn't sure where to
look.

Best,
Laird

Re: use separate mirrors for project dendencies and plugin dependencies ??

[Anders Hammar]

>
> 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  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  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
> > >
> > >   
> > > 
> > >   product-repo
> > >   *,!plugin-central
> > >   Internal Maven Repository Manager
> > >   http://repos.xxx.com:8081/nexus/content/groups/public
> > > 
> > > 
> > >   plugin-repo
> > >   plugin-central
> > >   Internal Maven Repository Manager for plugin and its
> > transitive
> > > dependencies
> > >   
> http://repos..com:8081/nexus/content/groups/plugin-public
> > > 
> > > 
> > >   
> > >
> > >   
> > > 
> > >   redefine-default-repositories
> > >   
> > > 
> > >   
> > >   central
> > >   http://central
> > >   true
> > >   true
> > > 
> > >   
> > >  
> > > 
> > > 
> > >   plugin-central 
> > >   http://central
> > >   true
> > >   true
> > > 
> > > 
> > > 
> > >   central
> > >   http://central
> > >   true
> > >   true
> > > 
> > >   
> > > 
> > >   
> > >
> > >   
> > > redefine-default-repositories
> > >   
> > >
> > >
> > > 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 
> > wrote:
> > >
> > > > It will if you use the same id, ie 'central'.
> > > >
> > > > /Anders (mobile)
> > > > Den 24 maj 2014 09:36 skrev "Dan Tran" :
> > > >
> > > > > Anders' suggestion sounds very logical
> > > > >
> > > > > however, i found this at super pom
> > > > >
> > > > >   
> > > > > 
> > > > >   central
> > > > >   Central Repository
> > > > >   http://repo.maven.apache.org/maven2
> > > > >   default
> > > > >   
> > > > > false
> > > > >   
> > > > > 
> > > > >   
> > > > >
> > > > >   
> > > > > 
> > > > >   central
> > > > >   Central Repository
> > > > >   http://repo.maven.apache.org/maven2
> > > > >   default
> > > > >   
> > > > > false
> > > > >   
> > > > >   
> > > > > never
> > > > >   
> > > > > 
> > > > >   
> > > > >
> > > > > 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  >
> > > > wrote:
> > > > >
> > > > > > On 6 May 2014 20:23, Anders Hammar  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
> > > > 

Re: use separate mirrors for project dendencies and plugin dependencies ??

[Dan Tran]

Hi Ander

that makes sense

now i only have

 

  product-repo
  *,!plugin-central
  Internal Maven Repository Manager
  http://repos.xxx.com:8081/nexus/content/groups/public

  


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  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  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
> >
> >   
> > 
> >   product-repo
> >   *,!plugin-central
> >   Internal Maven Repository Manager
> >   http://repos.xxx.com:8081/nexus/content/groups/public
> > 
> > 
> >   plugin-repo
> >   plugin-central
> >   Internal Maven Repository Manager for plugin and its
> transitive
> > dependencies
> >   http://repos..com:8081/nexus/content/groups/plugin-public
> > 
> > 
> >   
> >
> >   
> > 
> >   redefine-default-repositories
> >   
> > 
> >   
> >   central
> >   http://central
> >   true
> >   true
> > 
> >   
> >  
> > 
> > 
> >   plugin-central 
> >   http://central
> >   true
> >   true
> > 
> > 
> > 
> >   central
> >   http://central
> >   true
> >   true
> > 
> >   
> > 
> >   
> >
> >   
> > redefine-default-repositories
> >   
> >
> >
> > 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 
> wrote:
> >
> > > It will if you use the same id, ie 'central'.
> > >
> > > /Anders (mobile)
> > > Den 24 maj 2014 09:36 skrev "Dan Tran" :
> > >
> > > > Anders' suggestion sounds very logical
> > > >
> > > > however, i found this at super pom
> > > >
> > > >   
> > > > 
> > > >   central
> > > >   Central Repository
> > > >   http://repo.maven.apache.org/maven2
> > > >   default
> > > >   
> > > > false
> > > >   
> > > > 
> > > >   
> > > >
> > > >   
> > > > 
> > > >   central
> > > >   Central Repository
> > > >   http://repo.maven.apache.org/maven2
> > > >   default
> > > >   
> > > > false
> > > >   
> > > >   
> > > > never
> > > >   
> > > > 
> > > >   
> > > >
> > > > 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 
> > > wrote:
> > > >
> > > > > On 6 May 2014 20:23, Anders Hammar  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.
> > > > > >
> > > > > > /

Re: use separate mirrors for project dendencies and plugin dependencies ??

[Anders Hammar]

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  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
>
>   
> 
>   product-repo
>   *,!plugin-central
>   Internal Maven Repository Manager
>   http://repos.xxx.com:8081/nexus/content/groups/public
> 
> 
>   plugin-repo
>   plugin-central
>   Internal Maven Repository Manager for plugin and its transitive
> dependencies
>   http://repos..com:8081/nexus/content/groups/plugin-public
> 
> 
>   
>
>   
> 
>   redefine-default-repositories
>   
> 
>   
>   central
>   http://central
>   true
>   true
> 
>   
>  
> 
> 
>   plugin-central 
>   http://central
>   true
>   true
> 
> 
> 
>   central
>   http://central
>   true
>   true
> 
>   
> 
>   
>
>   
> redefine-default-repositories
>   
>
>
> 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  wrote:
>
> > It will if you use the same id, ie 'central'.
> >
> > /Anders (mobile)
> > Den 24 maj 2014 09:36 skrev "Dan Tran" :
> >
> > > Anders' suggestion sounds very logical
> > >
> > > however, i found this at super pom
> > >
> > >   
> > > 
> > >   central
> > >   Central Repository
> > >   http://repo.maven.apache.org/maven2
> > >   default
> > >   
> > > false
> > >   
> > > 
> > >   
> > >
> > >   
> > > 
> > >   central
> > >   Central Repository
> > >   http://repo.maven.apache.org/maven2
> > >   default
> > >   
> > > false
> > >   
> > >   
> > > never
> > >   
> > > 
> > >   
> > >
> > > 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 
> > wrote:
> > >
> > > > On 6 May 2014 20:23, Anders Hammar  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 ??

[Dan Tran]

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

  

  product-repo
  *,!plugin-central
  Internal Maven Repository Manager
  http://repos.xxx.com:8081/nexus/content/groups/public


  plugin-repo
  plugin-central
  Internal Maven Repository Manager for plugin and its transitive
dependencies
  http://repos..com:8081/nexus/content/groups/plugin-public


  

  

  redefine-default-repositories
  

  
  central
  http://central
  true
  true

  
 


  plugin-central 
  http://central
  true
  true



  central
  http://central
  true
  true

  

  

  
redefine-default-repositories
  


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  wrote:

> It will if you use the same id, ie 'central'.
>
> /Anders (mobile)
> Den 24 maj 2014 09:36 skrev "Dan Tran" :
>
> > Anders' suggestion sounds very logical
> >
> > however, i found this at super pom
> >
> >   
> > 
> >   central
> >   Central Repository
> >   http://repo.maven.apache.org/maven2
> >   default
> >   
> > false
> >   
> > 
> >   
> >
> >   
> > 
> >   central
> >   Central Repository
> >   http://repo.maven.apache.org/maven2
> >   default
> >   
> > false
> >   
> >   
> > never
> >   
> > 
> >   
> >
> > 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 
> wrote:
> >
> > > On 6 May 2014 20:23, Anders Hammar  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 ??

[Anders Hammar]

It will if you use the same id, ie 'central'.

/Anders (mobile)
Den 24 maj 2014 09:36 skrev "Dan Tran" :

> Anders' suggestion sounds very logical
>
> however, i found this at super pom
>
>   
> 
>   central
>   Central Repository
>   http://repo.maven.apache.org/maven2
>   default
>   
> false
>   
> 
>   
>
>   
> 
>   central
>   Central Repository
>   http://repo.maven.apache.org/maven2
>   default
>   
> false
>   
>   
> never
>   
> 
>   
>
> 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  wrote:
>
> > On 6 May 2014 20:23, Anders Hammar  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 ??

[Dan Tran]

Anders' suggestion sounds very logical

however, i found this at super pom

  

  central
  Central Repository
  http://repo.maven.apache.org/maven2
  default
  
false
  

  

  

  central
  Central Repository
  http://repo.maven.apache.org/maven2
  default
  
false
  
  
never
  

  

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  wrote:

> On 6 May 2014 20:23, Anders Hammar  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 ??

[Barrie Treloar]

On 6 May 2014 20:23, Anders Hammar  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 ??

[Anders Hammar]

>
> 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 
>> 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 
 wrote:

   On 6 May 2014 09:21, Dan Tran  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-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: use separate mirrors for project dendencies and plugin dependencies ??

[Wolf Geldmacher]

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  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 
wrote:

  On 6 May 2014 09:21, Dan Tran  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-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: use separate mirrors for project dendencies and plugin dependencies ??

[Bernd Eckenfels]

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 :
> 
> 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  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 
>>> wrote:
>>> 
 On 6 May 2014 09:21, Dan Tran  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-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: use separate mirrors for project dendencies and plugin dependencies ??

[Dan Tran]

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  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 
>> wrote:
>>
>>  On 6 May 2014 09:21, Dan Tran  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 ??

[Christian Domsch]

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  wrote:


On 6 May 2014 09:21, Dan Tran  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 ??

[Dan Tran]

Thanks Barrie,

Will see what I can can do.


On Mon, May 5, 2014 at 5:04 PM, Barrie Treloar  wrote:

> On 6 May 2014 09:21, Dan Tran  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 ??

[Barrie Treloar]

On 6 May 2014 09:21, Dan Tran  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...

use separate mirrors for project dendencies and plugin dependencies ??

[Dan Tran]

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: settings.xml, mirrors and pluginRepositories

[Jason van Zyl]

http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html

On May 22, 2012, at 8:11 PM, Jeff wrote:

> I might be missing something simple but when I setup a mirror such as:
> 
>  
>
>  Internal
>  Maven Repository Mirror
>  http://archiva/repository/internal/
>  *
>
>  
> 
> why won't Maven attempt to resolve plugins via the mirror?
> 
> I seem to have to setup a  with a repositories/pluginRepositories
> section to get plugins that are not in the default repositories.
> 
> Is there another syntax for the  section to tell Maven to look for
> plugins as well as artifacts?
> 
> -- 
> Jeff Vincent
> predato...@gmail.com
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
> I ♥ DropBox  !!

Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
-

There's no sense in being precise when you don't even know what you're talking 
about.

 -- John von Neumann

Re: Mirrors and repositories

[Wendy Smoak]

On Fri, Jul 8, 2011 at 4:09 PM, Maven User  wrote:
> When I was building without the additional repository defined, maven (maven
> 3.0.3) was unable to find the parent pom.  Once I added this extra
> repository, boom - it all works.

It worked because you had true somewhere.

> What's extra confusing is I have * - shouldn't that say
> "this url is a mirror of EVERYTHING?

That means it'll be a mirror for any repository defined in
settings.xml or pom.xml.  If none of those repos have snapshots
enabled, Maven won't download any snapshots.

> But I'm not saying I'm mirroring JUST central, I thought I was saying "I'm
> mirroring every repository you could possibly need".
> See my comment about the *.

No, it just means, "When you go through your list of known
repositories, substitute this url instead of the original one
defined."

-- 
Wendy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors and repositories

[Maven User]

Snapshots of plugins are explicitly banned as are not specifying versions of
plugins and relying on maven's super pom (years ago, I got whacked with this
when the war plugin changed).

But I'm not saying I'm mirroring JUST central, I thought I was saying "I'm
mirroring every repository you could possibly need".

See my comment about the *.

On Fri, Jul 8, 2011 at 4:10 PM, Brian Fox  wrote:

> > One reason you might do it is to enable a repository to be searched
> > for snapshots.  By default, Maven's built-in definition of 'central'
> > only has releases enabled.  Unless you define another repository
> > somewhere that has snapshots enabled, Maven will never retrieve any
> > snapshots.
>
>
> This is exactly why ^^
>
> You need to do the same for pluginRepositories if you ever want to get
> snapshots of plugins.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Mirrors and repositories

[Brian Fox]

> One reason you might do it is to enable a repository to be searched
> for snapshots.  By default, Maven's built-in definition of 'central'
> only has releases enabled.  Unless you define another repository
> somewhere that has snapshots enabled, Maven will never retrieve any
> snapshots.


This is exactly why ^^

You need to do the same for pluginRepositories if you ever want to get
snapshots of plugins.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors and repositories

[Maven User]

Ahhh - here we go -

So I'm working on rolling out a corp pom for a company who doesn't have one
right now.

The corp pom is a completely different maven project/jenkins build and
structurally, unrelated to the other projects that list it as a parent.

The current version of this corp pom is 1.0-SNAPSHOT and it's deployed to my
snapshot repository within Nexus.

The grouped up repository in Nexus includes this snapshot.

When I was building without the additional repository defined, maven (maven
3.0.3) was unable to find the parent pom.  Once I added this extra
repository, boom - it all works.

What's extra confusing is I have * - shouldn't that say
"this url is a mirror of EVERYTHING?

I'm basing this all on this link:

http://maven.apache.org/guides/mini/guide-mirror-settings.html

(thank you Wendy!)


On Fri, Jul 8, 2011 at 3:58 PM, Wendy Smoak  wrote:

>
> What happens when you don't?  Knowing why you think you need to do it
> would help someone explain it.
>
> One reason you might do it is to enable a repository to be searched
> for snapshots.  By default, Maven's built-in definition of 'central'
> only has releases enabled.  Unless you define another repository
> somewhere that has snapshots enabled, Maven will never retrieve any
> snapshots.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Mirrors and repositories

[Wendy Smoak]

On Fri, Jul 8, 2011 at 3:50 PM, Maven User  wrote:

> I thought I had a good handle on this, but can someone help me fully
> understand the  and  settings in settings.xml?
>
> When one has a repository server running, and there are several urls grouped
> up, why isn't it enough to tell maven where to look via a single mirrors
> stanza?
>
> Why do I then also have to define an additional repository?

What happens when you don't?  Knowing why you think you need to do it
would help someone explain it.

One reason you might do it is to enable a repository to be searched
for snapshots.  By default, Maven's built-in definition of 'central'
only has releases enabled.  Unless you define another repository
somewhere that has snapshots enabled, Maven will never retrieve any
snapshots.

-- 
Wendy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Mirrors and repositories

[Maven User]

Hi all -

I thought I had a good handle on this, but can someone help me fully
understand the  and  settings in settings.xml?

When one has a repository server running, and there are several urls grouped
up, why isn't it enough to tell maven where to look via a single mirrors
stanza?

Why do I then also have to define an additional repository?

For example, if I have:



full
Public repository
http://nexus.is.awesome/nexus/content/groups/public
*



Why do I also need to do this:



default

true

  

  snapshots
  Snapshots
  
false
always
warn
  
  
true
always
fail
  
  
http://nexus.is.awesome/nexus/content/repositories/snapshots/
  default

  

..

I'd have thought that the mirror stanza above would have pointed maven to
this grouped up url for ALL artifact resolution.

Re: Mirrors

[Marc Rohlfs]

> Partially true. For my own repositories, this will work. However,
> Maven also checks the repositories defined in all dependencies and
> those I have no influence over.
I normally define a mirror that also covers those repositories (using a 
wild card and/or a thirdparty mirror definition like the one I stated in 
the other post), because it's very annoying when Maven attempts to fetch 
dependencies from each and very repository that is defined somewhere - 
sometimes those builds can take really long.
Of course, You're right that You can't differentiate between release and 
snapshot repositories. I didn't take that in account, because I don't 
rely on thirdparty snapshots ...


> Would've been great if Maven had an option to mirror types of
> repositories (release/snapshot) as well as id's.
I think that would be a good idea. Could be worth it filing a feature 
request in the Maven Jira.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Asmann, Roland]

On 23.02.2011 18:40, Marc Rohlfs wrote:
>  > I haven't tried that, but what I read from the Maven-pages, it doesn't
>  > understand wildcards like that... But I can try though...
> I thought it would work, but I am not sure - I have to admit ...
>
>  > Then again, it would only work if the repositories are actually named
>  > like that, and I can't always influence that (3rd party!)...
> You use the repository IDs in the 'mirrorOf' configuration, and those
> IDs are defined in Your pom.xmls or Your settings.xml, where You define
> the remote repositories You want to use - this means that You should be
> able to influence that.
> Or did I misunderstand Your problem?

Partially true. For my own repositories, this will work. However, Maven 
also checks the repositories defined in all dependencies and those I 
have no influence over.
>
>  > Ah well, for now I'll take the Nexus-solution[1] and explicitly add a
>  > snapshot-repository that is always active.
> OK, if You have everything in one Nexus, creating a repository group for
> all of Your repositories (even including proxy repos) is the best way,
> of course.

If it were only a single Nexus, then the normal mirrorOf * would have 
worked. Would've been great if Maven had an option to mirror types of 
repositories (release/snapshot) as well as id's.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock  T +43 1 2198790-27
Floridsdorfer Hauptstr. 1   F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at

-
 >>> business. people. technology. <<<
-

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Marc Rohlfs]

> I haven't tried that, but what I read from the Maven-pages, it doesn't
> understand wildcards like that... But I can try though...
I thought it would work, but I am not sure - I have to admit ...

> Then again, it would only work if the repositories are actually named
> like that, and I can't always influence that (3rd party!)...
You use the repository IDs in the 'mirrorOf' configuration, and those 
IDs are defined in Your pom.xmls or Your settings.xml, where You define 
the remote repositories You want to use - this means that You should be 
able to influence that.

Or did I misunderstand Your problem?

> Ah well, for now I'll take the Nexus-solution[1] and explicitly add a
> snapshot-repository that is always active.
OK, if You have everything in one Nexus, creating a repository group for 
all of Your repositories (even including proxy repos) is the best way, 
of course.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Asmann, Roland]

I haven't tried that, but what I read from the Maven-pages, it doesn't 
understand wildcards like that... But I can try though...

Then again, it would only work if the repositories are actually named 
like that, and I can't always influence that (3rd party!)...

Ah well, for now I'll take the Nexus-solution[1] and explicitly add a 
snapshot-repository that is always active.

[1] 
http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html


On 23.02.2011 13:46, Marc Rohlfs wrote:
> Did You try something like this:
> 
> 
> shapshot-mirrors
> Snapshot Mirros
> http://snapshots.mycompany.com/repo
> *-snapshots
> 
> 
> release-mirrors
> Release Mirros
> http://releases.mycompany.com/repo
> *-releases
> 
> 
> 
> 
> thirdparty-mirrors
> Thirdparty Mirros
> http://proxy.mycompany.com/repo
> !*-releases,!*-snapshots
> 
> 
>
> I didn't double-check, but I'd say this should work ...
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>

-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock  T +43 1 2198790-27
Floridsdorfer Hauptstr. 1   F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at

-
 >>> business. people. technology. <<<
-

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Marc Rohlfs]

Did You try something like this:
  

  shapshot-mirrors
  Snapshot Mirros
  http://snapshots.mycompany.com/repo
  *-snapshots


  release-mirrors
  Release Mirros
  http://releases.mycompany.com/repo
  *-releases
  


  
  thirdparty-mirrors
  Thirdparty Mirros
  http://proxy.mycompany.com/repo
  !*-releases,!*-snapshots

  

I didn't double-check, but I'd say this should work ...

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Asmann, Roland]

I know that, but I don't want to list all snapshot-repo's I have in both 
mirrors (first as exclude, in the other as include).

I was hoping there was an easier way to do this...


On 23.02.2011 13:05, Anders Hammar wrote:
> http://maven.apache.org/guides/mini/guide-mirror-settings.html
>
> See Advance Mirror Specification.
>
> /Anders
>
> On Wed, Feb 23, 2011 at 12:18, Asmann, Roland
> wrote:
>
>  > Hi all,
>  >
>  > I was wondering if it is possible in Maven 2.2.1 to setup 2 mirrors that
>  > will take all my requests. I have the first one configured to take all
>  > release-versions, the second to handle snapshots.
>  >
>  > Now, the problem is that when I tell the first one to mirror '*', the
>  > second mirror never gets called... Is there a way to solve this problem?
>  >
>  > Thanks.
>  >
>  > --
>  > Roland Asmann
>  > Senior Software Engineer
>  >
>  > adesso Austria GmbH
>  > Floridotower 26. Stock T +43 1 2198790-27
>  > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
>  > A-1210 Wien M +43 664 88657566
>  > E roland.asm...@adesso.at
>  > W www.adesso.at
>  >
>  > -
>  > >>> business. people. technology. <<<
>  > -
>  >
>  > -
>  > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>  > For additional commands, e-mail: users-h...@maven.apache.org
>  >
>  >
>

-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock  T +43 1 2198790-27
Floridsdorfer Hauptstr. 1   F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at

-
 >>> business. people. technology. <<<
-

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Anders Hammar]

http://maven.apache.org/guides/mini/guide-mirror-settings.html

See Advance Mirror Specification.

/Anders

On Wed, Feb 23, 2011 at 12:18, Asmann, Roland wrote:

> Hi all,
>
> I was wondering if it is possible in Maven 2.2.1 to setup 2 mirrors that
> will take all my requests. I have the first one configured to take all
> release-versions, the second to handle snapshots.
>
> Now, the problem is that when I tell the first one to mirror '*', the
> second mirror never gets called... Is there a way to solve this problem?
>
> Thanks.
>
> --
> Roland Asmann
> Senior Software Engineer
>
> adesso Austria GmbH
> Floridotower 26. Stock  T +43 1 2198790-27
> Floridsdorfer Hauptstr. 1   F +43 1 2198790-927
> A-1210 Wien M +43 664 88657566
>E roland.asm...@adesso.at
>W www.adesso.at
>
> -
> >>> business. people. technology. <<<
> -
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Mirrors

[Asmann, Roland]

Hi all,

I was wondering if it is possible in Maven 2.2.1 to setup 2 mirrors that 
will take all my requests. I have the first one configured to take all 
release-versions, the second to handle snapshots.

Now, the problem is that when I tell the first one to mirror '*', the 
second mirror never gets called... Is there a way to solve this problem?

Thanks.

-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock  T +43 1 2198790-27
Floridsdorfer Hauptstr. 1   F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at

-
 >>> business. people. technology. <<<
-

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: set up maven repository for all the mirrors

[Marc Rohlfs]

I should be possible, of course. I'd suggest to talk to Your company's 
network admin about Apache and DNS configuration.



On 17/01/11 19:38, anemdhana wrote:


Hello everyone,
I found this is really useful to setup internal maven repository
http://www.jfrog.org/products.php, which takes care of getting dependencies
by looking into all repositories.
A simple question, I want to setup this in an intranet environment; by
allowing ldap authentication; Right now, I am able to access in my local box
as, http://localhost:8080/artifactory with jetty-7 servelt container running
on port 8080.

is it possible to have customized url by having apache-webserver installed,
like, http://repo.mycompany.com/artifactory


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: set up maven repository for all the mirrors

[Wayne Fay]

> is it possible to have customized url by having apache-webserver installed,
> like, http://repo.mycompany.com/artifactory

Probably. But we're not experts on Artifactory here.

Why aren't you asking the Artifactory people who created the software
you are running and now have questions about?

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

set up maven repository for all the mirrors

[anemdhana]

Hello everyone,
I found this is really useful to setup internal maven repository
http://www.jfrog.org/products.php, which takes care of getting dependencies
by looking into all repositories.
A simple question, I want to setup this in an intranet environment; by
allowing ldap authentication; Right now, I am able to access in my local box
as, http://localhost:8080/artifactory with jetty-7 servelt container running
on port 8080.

is it possible to have customized url by having apache-webserver installed,
like, http://repo.mycompany.com/artifactory
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/set-up-maven-repository-for-all-the-mirrors-tp3344955p3344955.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

Re: Dumb question about mirrors and repositories

[Phillip Hellewell]

On Mon, Dec 6, 2010 at 2:06 PM, Justin Edelson  wrote:
>
> Because by default, Maven only has central configured as a repository and
> that's only configured for release artifacts, not snapshots.

Thanks!  That explains it perfectly.

Phillip

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Dumb question about mirrors and repositories

[Justin Edelson]

On Mon, Dec 6, 2010 at 3:15 PM, Phillip Hellewell  wrote:

> On Mon, Dec 6, 2010 at 12:55 PM, Hilco Wijbenga
>  wrote:
> >
> > You need to add something like the following to your settings.xml to
> > "enable" snapshots.
> >
> > ...
>
> Thanks, but if you look closely at my email you'll see I already
> figured that out.  All I'm interesting in now is gaining some more
> understanding about mirrors versus repositories to understand why
> things work the way they do.
>
> Phillip
>

Because by default, Maven only has central configured as a repository and
that's only configured for release artifacts, not snapshots.

Justin


>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Dumb question about mirrors and repositories

[Phillip Hellewell]

On Mon, Dec 6, 2010 at 12:55 PM, Hilco Wijbenga
 wrote:
>
> You need to add something like the following to your settings.xml to
> "enable" snapshots.
>
> ...

Thanks, but if you look closely at my email you'll see I already
figured that out.  All I'm interesting in now is gaining some more
understanding about mirrors versus repositories to understand why
things work the way they do.

Phillip

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Dumb question about mirrors and repositories

[Hilco Wijbenga]

On 6 December 2010 11:38, Phillip Hellewell  wrote:
> For some reason I was under the impression that if I had a mirrorOf *
> defined in my settings.xml, I didn't need to have any 
> defined.
:

:
> So now I'm really curious.  Should it actually be working with just
> the mirror, and if not, why not exactly?  Why should releases work
> with the mirror but not snapshots?  And if I need to use
>  anyways, should I get rid of the mirror?  (I'm thinking
> no, since I really want to ensure it is always used over just using
> Maven central directly).

You need to add something like the following to your settings.xml to
"enable" snapshots.


  SnapshotsOkay
  
true
  
  

  central
  http://central
  
true
  
  
true
  

  
  

  central
  http://central
  
true
  
  
true
  

  


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Dumb question about mirrors and repositories

[Phillip Hellewell]

For some reason I was under the impression that if I had a mirrorOf *
defined in my settings.xml, I didn't need to have any 
defined.

  

  all-mirror
  Mirror of Everything
  http://maven.example.com:8080/nexus/content/groups/public
  *

  

It's been working just great up until now when I tried to depend on a
snapshot that is only in the remote repo.  It wouldn't find it, but
after I added an appropriate  section, it does:

  

  default-repo
  

  adrepo-public
  http://maven.example.com:8080/nexus/content/groups/public
  true
  true

  

  
  
default-repo
  

So now I'm really curious.  Should it actually be working with just
the mirror, and if not, why not exactly?  Why should releases work
with the mirror but not snapshots?  And if I need to use
 anyways, should I get rid of the mirror?  (I'm thinking
no, since I really want to ensure it is always used over just using
Maven central directly).

Thanks,
Phillip

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Setting up mirrors

[Aleksey Didik]

Hmm,
_*!**_  looks strange.
Try to use


new-repository
http://repo.upromise.com:8080/archiva/repository/new-repo
platform-release,platform-snapshot


Aleksey.

09.03.2010 4:49, Michael Delaney пишет:

All,

Using Maven 2.2.1, I'm trying to setup (in the 
$M2_HOME/conf/settings.xml file) some mirrors. Looking at the 
documentation 
(http://maven.apache.org/guides/mini/guide-mirror-settings.html) for 
2.2.1, it says that, in the  tag, I can set repository 
includes and repository excludes but I can't seem to get it working as 
expected. Can anyone provide some help?




new-repository
http://repo.upromise.com:8080/archiva/repository/new-repo
!*,platform-release,platform-snapshot


full
http://repo.upromise.com:8080/archiva/repository/full
*,!platform-release,!platform-snapshot



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Setting up mirrors

[Michael Delaney]

All,

Using Maven 2.2.1, I'm trying to setup (in the 
$M2_HOME/conf/settings.xml file) some mirrors. Looking at the 
documentation 
(http://maven.apache.org/guides/mini/guide-mirror-settings.html) for 
2.2.1, it says that, in the  tag, I can set repository 
includes and repository excludes but I can't seem to get it working as 
expected. Can anyone provide some help?




new-repository
http://repo.upromise.com:8080/archiva/repository/new-repo
!*,platform-release,platform-snapshot


full
http://repo.upromise.com:8080/archiva/repository/full
*,!platform-release,!platform-snapshot



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Quintin Beukes]

On Sun, Oct 18, 2009 at 7:45 PM, Brian Fox  wrote:
> Maven still has these repositories configured internally even though
> you most likely have a mirror definition to redirect these to Nexus.
> The mirror definition applies at the end of the lookup processing and
> Maven doesn't currently deduplicate the repository definitions.
> Fortunately, Nexus is caching the results so subsequent checks happen
> instantly without rechecking a remote.

I did notice they go very quickly, and figured it's the cache - so
it's not a problem that it happens. Just thought if it could be
skipped it would have been a bit better.

Q

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Mirrors

[Brian Fox]

Maven still has these repositories configured internally even though
you most likely have a mirror definition to redirect these to Nexus.
The mirror definition applies at the end of the lookup processing and
Maven doesn't currently deduplicate the repository definitions.
Fortunately, Nexus is caching the results so subsequent checks happen
instantly without rechecking a remote.

On Sun, Oct 18, 2009 at 11:58 AM, Quintin Beukes  wrote:
> Hey,
>
> I have my nexus repository set up to have all requests proxy through
> it. But it still does checks like the following:
> snapshot org.apache.geronimo.plugins:connector:2.2-SNAPSHOT: checking
> for updates from central
> snapshot org.apache.geronimo.plugins:connector:2.2-SNAPSHOT: checking
> for updates from codehaus.snapshots
> snapshot org.apache.geronimo.plugins:connector:2.2-SNAPSHOT: checking
> for updates from apache.snapshots
>
> Isn't there a way for it to realize those last to checks are redundant
> and only do the first?
>
> Quintin Beukes
>
> -
> 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

Mirrors

[Quintin Beukes]

Hey,

I have my nexus repository set up to have all requests proxy through
it. But it still does checks like the following:
snapshot org.apache.geronimo.plugins:connector:2.2-SNAPSHOT: checking
for updates from central
snapshot org.apache.geronimo.plugins:connector:2.2-SNAPSHOT: checking
for updates from codehaus.snapshots
snapshot org.apache.geronimo.plugins:connector:2.2-SNAPSHOT: checking
for updates from apache.snapshots

Isn't there a way for it to realize those last to checks are redundant
and only do the first?

Quintin Beukes

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: mirrors, oh mirrors

[Brian E. Fox]

Yes, Nexus 1.3 supports true mirrors.
http://www.sonatype.com/people/2009/03/new-feature-in-nexus-13-mirror-su
pport/

-Original Message-
From: CemKoc [mailto:cem.koc.fwd+nbl...@gmail.com] 
Sent: Wednesday, April 08, 2009 7:05 AM
To: users@maven.apache.org
Subject: Re: mirrors, oh mirrors



Is there any solution about this problem?  



I'd like mirrors to provide multiple alternate locations. I put the
improvement request here: http://jira.codehaus.org/browse/MNG-3772

Cheers,
Szczepan



-- 
View this message in context:
http://n2.nabble.com/mirrors%2C-oh-mirrors-tp1125603p2604561.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

Re: mirrors, oh mirrors

[CemKoc]

Is there any solution about this problem?  



I'd like mirrors to provide multiple alternate locations. I put the
improvement request here: http://jira.codehaus.org/browse/MNG-3772

Cheers,
Szczepan



-- 
View this message in context: 
http://n2.nabble.com/mirrors%2C-oh-mirrors-tp1125603p2604561.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

Re: Any maven repo mirrors in China?

[Juven Xu]

Yeah, Nexus should be a good solution for you!

Currently there's no central mirror in China, the bandwidth in China is very
expensive. And since universities here use their own "education network", we
are not able to ask for help form them.

Finding a sponsor is not a easy thing :), but we will try.

On Wed, Mar 4, 2009 at 11:34 AM, Jason van Zyl  wrote:

> Juven might have a better idea, but you can definitely use Nexus to cache
> the artifacts on site so that once the artifacts were retrieved the local
> cache will be used. That will save a lot of bandwidth and time.
>
> http://nexus.sonatype.org
>
>
> On 3-Mar-09, at 4:02 PM, Raymond Feng wrote:
>
>  Hi,
>>
>> Do we have any maven repo mirrors in China? Our (Apache Tuscany project)
>> Chinese users always complain that their connections to repo1.maven.orgare 
>> very slow and it takes hours to run a build. Most of the time it fails
>> in the middle due to download issues.
>>
>> Thanks,
>> Raymond
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> --
>
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more examples
> you look at, the more general your framework will be.
>
>  -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
- juven

Re: Any maven repo mirrors in China?

[Jason van Zyl]

Juven might have a better idea, but you can definitely use Nexus to  
cache the artifacts on site so that once the artifacts were retrieved  
the local cache will be used. That will save a lot of bandwidth and  
time.


http://nexus.sonatype.org

On 3-Mar-09, at 4:02 PM, Raymond Feng wrote:


Hi,

Do we have any maven repo mirrors in China? Our (Apache Tuscany  
project) Chinese users always complain that their connections to  
repo1.maven.org are very slow and it takes hours to run a build.  
Most of the time it fails in the middle due to download issues.


Thanks,
Raymond

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
--

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more  
examples

you look at, the more general your framework will be.

  -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Any maven repo mirrors in China?

[Raymond Feng]

Hi,

Do we have any maven repo mirrors in China? Our (Apache Tuscany project) 
Chinese users always complain that their connections to repo1.maven.org are 
very slow and it takes hours to run a build. Most of the time it fails in 
the middle due to download issues.


Thanks,
Raymond 



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

http://mirrors.ibiblio.org/pub/mirrors/maven2 availability

[EJ Ciramella]

Is this mirror down?
 
(and is this the place to ask?)

Re: Repo1 Mirrors not Updated

[Brett Porter]

I've updated that page to indicate which mirrors are synced directly  
from central and should therefore be more up to date.


- Brett

On 03/12/2008, at 7:28 PM, Reinhard Nägele wrote:


I just checked all mirrors listed here:

http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories


I guess I had bad luck because I picked exactly the problematic ones:

http://mirrors.dotsrc.org/maven2/org/apache/wicket/wicket-archetype-quickstart/

http://mirrors.sunsite.dk/maven2/org/apache/wicket/wicket-archetype-quickstart/

http://maven2.mirrors.skynet.be/pub/maven2/org/apache/wicket/wicket-archetype-quickstart/


The other mirrors look fine.

Reinhard


-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2008 8:32 PM
To: Maven Users List
Subject: RE: Repo1 Mirrors not Updated

We push daily to a few mirrors, other mirrors are pulling from some  
other locations. Which mirror are you trying to use?


-Original Message-
From: Reinhard Nägele [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2008 2:56 AM
To: users@maven.apache.org
Subject: Repo1 Mirrors not Updated

Hi,

I was just trying to set up a new Wicket application using wicket- 
archetype-quickstart. I tried versions 1.3.5 and 1.4-rc1. Both  
failed. I then checked repo1 and did find the archetype artifacts.  
Then I figured we were using a repo1 mirror. I checked there and  
noticed that both, 1.3.5 and 1.4-rc1, did not make it to the mirror.  
I then checked several other public mirrors. None of them had the  
artifacts.


So, my question is why the mirrors were not updated. I thought  
mirrors were updated daily.


Reinhard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Repo1 Mirrors not Updated

[Reinhard Nägele]

I just checked all mirrors listed here:

http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories


I guess I had bad luck because I picked exactly the problematic ones:

http://mirrors.dotsrc.org/maven2/org/apache/wicket/wicket-archetype-quickstart/

http://mirrors.sunsite.dk/maven2/org/apache/wicket/wicket-archetype-quickstart/

http://maven2.mirrors.skynet.be/pub/maven2/org/apache/wicket/wicket-archetype-quickstart/


The other mirrors look fine.

Reinhard


-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 02, 2008 8:32 PM
To: Maven Users List
Subject: RE: Repo1 Mirrors not Updated

We push daily to a few mirrors, other mirrors are pulling from some other 
locations. Which mirror are you trying to use?

-Original Message-
From: Reinhard Nägele [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 02, 2008 2:56 AM
To: users@maven.apache.org
Subject: Repo1 Mirrors not Updated

Hi,

I was just trying to set up a new Wicket application using 
wicket-archetype-quickstart. I tried versions 1.3.5 and 1.4-rc1. Both failed. I 
then checked repo1 and did find the archetype artifacts. Then I figured we were 
using a repo1 mirror. I checked there and noticed that both, 1.3.5 and 1.4-rc1, 
did not make it to the mirror. I then checked several other public mirrors. 
None of them had the artifacts.

So, my question is why the mirrors were not updated. I thought mirrors were 
updated daily.

Reinhard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Repo1 Mirrors not Updated

[Brian E. Fox]

We push daily to a few mirrors, other mirrors are pulling from some other 
locations. Which mirror are you trying to use?

-Original Message-
From: Reinhard Nägele [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 02, 2008 2:56 AM
To: users@maven.apache.org
Subject: Repo1 Mirrors not Updated

Hi,

I was just trying to set up a new Wicket application using 
wicket-archetype-quickstart. I tried versions 1.3.5 and 1.4-rc1. Both failed. I 
then checked repo1 and did find the archetype artifacts. Then I figured we were 
using a repo1 mirror. I checked there and noticed that both, 1.3.5 and 1.4-rc1, 
did not make it to the mirror. I then checked several other public mirrors. 
None of them had the artifacts.

So, my question is why the mirrors were not updated. I thought mirrors were 
updated daily.

Reinhard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Repo1 Mirrors not Updated

[Carlos Sanchez]

can you send the exact urls you were looking for?

On Tue, Dec 2, 2008 at 2:56 AM, Reinhard Nägele
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was just trying to set up a new Wicket application using 
> wicket-archetype-quickstart. I tried versions 1.3.5 and 1.4-rc1. Both failed. 
> I then checked repo1 and did find the archetype artifacts. Then I figured we 
> were using a repo1 mirror. I checked there and noticed that both, 1.3.5 and 
> 1.4-rc1, did not make it to the mirror. I then checked several other public 
> mirrors. None of them had the artifacts.
>
> So, my question is why the mirrors were not updated. I thought mirrors were 
> updated daily.
>
> Reinhard
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Repo1 Mirrors not Updated

[Reinhard Nägele]

Hi,

I was just trying to set up a new Wicket application using 
wicket-archetype-quickstart. I tried versions 1.3.5 and 1.4-rc1. Both failed. I 
then checked repo1 and did find the archetype artifacts. Then I figured we were 
using a repo1 mirror. I checked there and noticed that both, 1.3.5 and 1.4-rc1, 
did not make it to the mirror. I then checked several other public mirrors. 
None of them had the artifacts.

So, my question is why the mirrors were not updated. I thought mirrors were 
updated daily.

Reinhard


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Public service announcement] mirrors of Central and considerate repo use

[Alex Athanasopoulos]

Thanks.  This sheds some light to my darkness, and may explain why my
home-made maven mirror wasn't working properly.
Alex


On Sat, Nov 29, 2008 at 4:33 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:

> On Sat, Nov 29, 2008 at 5:16 AM, Alex Athanasopoulos
> <[EMAIL PROTECTED]> wrote:
>
> > One of the most annoying problems I ran into with maven was when I setup
> a
> > central mirror containing my old local repository, deleted my local
> > repository, and then tried to rebuild it by doing a build.
>
> A local repo can't be used as a remote repo... while the directory
> structure looks the same, the metadata files are different.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [Public service announcement] mirrors of Central and considerate repo use

[Wim Deblauwe]

+1 for that

2008/11/29 Paul Benedict <[EMAIL PROTECTED]>

> I think Maven should download and configure itself with a list of
> mirrors on first execution. Why leave this up to the users? I bet most
> will likely not care to change.
>
> Paul
>
> On Sat, Nov 29, 2008 at 8:33 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > On Sat, Nov 29, 2008 at 5:16 AM, Alex Athanasopoulos
> > <[EMAIL PROTECTED]> wrote:
> >
> >> One of the most annoying problems I ran into with maven was when I setup
> a
> >> central mirror containing my old local repository, deleted my local
> >> repository, and then tried to rebuild it by doing a build.
> >
> > A local repo can't be used as a remote repo... while the directory
> > structure looks the same, the metadata files are different.
> >
> > --
> > Wendy
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [Public service announcement] mirrors of Central and considerate repo use

[Paul Benedict]

I think Maven should download and configure itself with a list of
mirrors on first execution. Why leave this up to the users? I bet most
will likely not care to change.

Paul

On Sat, Nov 29, 2008 at 8:33 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 29, 2008 at 5:16 AM, Alex Athanasopoulos
> <[EMAIL PROTECTED]> wrote:
>
>> One of the most annoying problems I ran into with maven was when I setup a
>> central mirror containing my old local repository, deleted my local
>> repository, and then tried to rebuild it by doing a build.
>
> A local repo can't be used as a remote repo... while the directory
> structure looks the same, the metadata files are different.
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Public service announcement] mirrors of Central and considerate repo use

[Wendy Smoak]

On Sat, Nov 29, 2008 at 5:16 AM, Alex Athanasopoulos
<[EMAIL PROTECTED]> wrote:

> One of the most annoying problems I ran into with maven was when I setup a
> central mirror containing my old local repository, deleted my local
> repository, and then tried to rebuild it by doing a build.

A local repo can't be used as a remote repo... while the directory
structure looks the same, the metadata files are different.

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Public service announcement] mirrors of Central and considerate repo use

[Wendy Smoak]

On Sat, Nov 29, 2008 at 6:48 AM, Torsten Werner
<[EMAIL PROTECTED]> wrote:

> me too! ;-) And I like to have a minimal zip file: just one version of
> every core plugin and one version every direct or indirect dependency
> - not 4 versions of commons-collections, 4 versions of
> commons-logging, 3 versions of maven-plugin-plugin, etc.

You could get pretty close with the Assembly plugin's ability to build
a repository [1].  However, the problem I always run into is that,
like all Maven builds, it chooses *one* version of each dependency.
That means if you try to create a download with all the core plugins,
and the site plugin wants foo-1.0.jar, but the resources plugin wants
foo-2.0.jar, the resulting repository won't be complete.  You'd have
to build a repository for each plugin, and merge them all together.

[1] 
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Public service announcement] mirrors of Central and considerate repo use

[Torsten Werner]

Hi,

On Sat, Nov 29, 2008 at 1:16 PM, Alex Athanasopoulos
<[EMAIL PROTECTED]> wrote:
> I wish that I could download a zip file containing the subset of central
> containing maven's core plugins and their dependencies.

me too! ;-) And I like to have a minimal zip file: just one version of
every core plugin and one version every direct or indirect dependency
- not 4 versions of commons-collections, 4 versions of
commons-logging, 3 versions of maven-plugin-plugin, etc.

Cheers,
Torsten

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Public service announcement] mirrors of Central and considerate repo use

[Alex Athanasopoulos]

This touches on my pet peeve about maven.

I wish that I could download a zip file containing the subset of central
containing maven's core plugins and their dependencies.  I would then gladly
use it as my central mirror and work productively on my projects without
having to worry about central.

I also wish that Maven did not access a central online repository by
default, so I wouldn't have to go through the extra effort of preventing it
from doing so.  When Maven is installed "out of the box", it could be
configured to use its own self-contained repository that came with the
installation.  If I want non-core plugins or other things, then I could tell
maven to use an online repository.

In other words, I want an integration-tested self-contained maven release.
 Is that a lot to ask for from a dependency management tool?  I don't have
that now, so I have to do my own version managemnet of all maven plugins
that I use.  When I try to use a plugin or a plugin feature that I haven't
used before, I have to go through a sometimes painful process of figuring
out which is the version of the plugin that works and is consistent with all
my existing projects and plugins.  I've more than once used a plugin version
mentioned in the documentation,  only to find out that it's buggy or
obsolete and I need to use a newer version (or sometimes even a completely
different groupId/artifactId).

Can maven, the tool, be separated from central, the grand repository of java
libraries?  I don't want central.  If I want library X for my projects, I
can go to library X's website, download X, and add it to my repository.  If
library X wants to be maven-friendly, it can include a script that lets me
add all its jar files to my repository easily, so I don't have to add them
one by one manually.

Wouldn't this reduce traffic to maven central?

But maven doesn't come in a box.  Instead, it lets its plugins download
whatever dependencies they want from central.  It seems that it even gives
them the freedom to specify a range of versions, or any random version they
find, so that what a build does is unpredictable and dependent on the
vagaries of a moving target central repository.  It's amazing that it works
most of the time, but it fails too often for me.

One of the most annoying problems I ran into with maven was when I setup a
central mirror containing my old local repository, deleted my local
repository, and then tried to rebuild it by doing a build.  mvn went on to
happily copy things from my central mirror, until it couldn't resolve a
dependency.  It has something to do with a "RELEASE" version of a plugin not
being found.  I have aparently gotten a central artifact at some point in
time that has an integration problem with other artifacts and ends up using
an artifact version that it doesn't explicitly ask for.  I believe it's
related to the site plugin, which I have since stopped trying to use.  In
the end, I went back to copying my central mirror to my local repository
(something easily done with svn, which I use as my repository manager).

-Alex

On Tue, Nov 25, 2008 at 5:27 PM, Brian E. Fox <[EMAIL PROTECTED]>wrote:

> The central repo has been undergoing significant load lately, most
> likely the result of people crawling and attempting to download all 70GB
> of it. I'd like to point out the availability of additional mirrors that
> you can use to increase your download performance and reduce the load on
> central. These mirrors are updated daily right after central pulls in
> all the new artifacts, so they are as fresh as central. Find the list of
> mirrors here[1].
>
>
>
> Also, for those of you with multiple developers in a single location not
> using a repo manager, what are you waiting for? There are plenty to
> choose from and numerous reasons to do so, particularly the ability to
> isolate yourself from transitive network outages or slowdowns. You can
> read more about why and the existing repo managers at [2],[3] and a
> comparison grid here at [4]
>
>
>
> Also, if you are using a repo manager, make sure to correctly configure
> it to not make requests to public repositories for your internal
> artifacts. Otherwise you are making a ton of requests for things that
> will never be found, increasing the bandwidth usage on your side and
> ours. Also it gives away potentially sensitive information as someone
> could scrape the logs and figure out what you're up to internally based
> on these requests. Nexus lets you configure routing rules so you could
> exclude com.yourcompany.* from central. Archiva has similar
> functionality, I'm not sure about Artifactory.
>
>
>
> Please be a polite repository user. These repos and mirrors are provided
> free of charge but there is a real cost behind providing this bandwid

RE: [Public service announcement] mirrors of Central and considerate repo use

[Brian E. Fox]

This is an interesting concept we'd have to persue. If you want to know,
email me directly and I can look you up and let you know what I see.

We will probably start publishing a list of abusers in a hall of shame
;-)

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baptiste
MATHUS
Sent: Tuesday, November 25, 2008 1:54 PM
To: Maven Users List
Subject: Re: [Public service announcement] mirrors of Central and
considerate repo use

2008/11/25 Brian E. Fox <[EMAIL PROTECTED]>

> The central repo has been undergoing significant load lately,



> Also, if you are using a repo manager, make sure to correctly
configure
> it to not make requests to public repositories for your internal
> artifacts. Otherwise you are making a ton of requests for things that
> will never be found, increasing the bandwidth usage on your side and
> ours. Also it gives away potentially sensitive information as someone
> could scrape the logs and figure out what you're up to internally
based
> on these requests. Nexus lets you configure routing rules so you could
> exclude com.yourcompany.* from central. Archiva has similar
> functionality, I'm not sure about Artifactory.
>

Hi Brian,

We've configured an internal maven repository manager some months ago
for
now. So, our requests should not be too high on the repo1.maven.org. But
as
we might have missed something in the configuration, wouldn't be
possible to
access logs from central in some way?

I mean, I know there would some privacy/security problems to do that
without
any restrictions. But maybe those logs could be filtered by the
requesting
(public) IP? This way, it would be possible for us to know if our hit
count
is acceptable or not according to say some typical/acceptable value you
would provide?

I know you all already have enough work with maven not to look for new
tasks
:-). Just wanting to detect my potential MRM leakages :-) (or inside
developers that would directly hit central without going through our
internal repo/proxy...).

Cheers.

-- 
Baptiste  MATHUS - http://batmat.net
Save a tree,
Eat a beaver!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Public service announcement] mirrors of Central and considerate repo use

[Baptiste MATHUS]

2008/11/25 Brian E. Fox <[EMAIL PROTECTED]>

> The central repo has been undergoing significant load lately,



> Also, if you are using a repo manager, make sure to correctly configure
> it to not make requests to public repositories for your internal
> artifacts. Otherwise you are making a ton of requests for things that
> will never be found, increasing the bandwidth usage on your side and
> ours. Also it gives away potentially sensitive information as someone
> could scrape the logs and figure out what you're up to internally based
> on these requests. Nexus lets you configure routing rules so you could
> exclude com.yourcompany.* from central. Archiva has similar
> functionality, I'm not sure about Artifactory.
>

Hi Brian,

We've configured an internal maven repository manager some months ago for
now. So, our requests should not be too high on the repo1.maven.org. But as
we might have missed something in the configuration, wouldn't be possible to
access logs from central in some way?

I mean, I know there would some privacy/security problems to do that without
any restrictions. But maybe those logs could be filtered by the requesting
(public) IP? This way, it would be possible for us to know if our hit count
is acceptable or not according to say some typical/acceptable value you
would provide?

I know you all already have enough work with maven not to look for new tasks
:-). Just wanting to detect my potential MRM leakages :-) (or inside
developers that would directly hit central without going through our
internal repo/proxy...).

Cheers.

-- 
Baptiste  MATHUS - http://batmat.net
Save a tree,
Eat a beaver!

[Public service announcement] mirrors of Central and considerate repo use

[Brian E. Fox]

The central repo has been undergoing significant load lately, most
likely the result of people crawling and attempting to download all 70GB
of it. I'd like to point out the availability of additional mirrors that
you can use to increase your download performance and reduce the load on
central. These mirrors are updated daily right after central pulls in
all the new artifacts, so they are as fresh as central. Find the list of
mirrors here[1]. 

 

Also, for those of you with multiple developers in a single location not
using a repo manager, what are you waiting for? There are plenty to
choose from and numerous reasons to do so, particularly the ability to
isolate yourself from transitive network outages or slowdowns. You can
read more about why and the existing repo managers at [2],[3] and a
comparison grid here at [4]

 

Also, if you are using a repo manager, make sure to correctly configure
it to not make requests to public repositories for your internal
artifacts. Otherwise you are making a ton of requests for things that
will never be found, increasing the bandwidth usage on your side and
ours. Also it gives away potentially sensitive information as someone
could scrape the logs and figure out what you're up to internally based
on these requests. Nexus lets you configure routing rules so you could
exclude com.yourcompany.* from central. Archiva has similar
functionality, I'm not sure about Artifactory.  

 

Please be a polite repository user. These repos and mirrors are provided
free of charge but there is a real cost behind providing this bandwidth.
Scraping the entire repository starves other users and increases the
cost of providing these repositories to the community. If the mirrors
start getting abused then we may find less geographical redundancy as a
result. There is never a reason to download the world if you have a
repository manager that is caching everything you need locally.

 

[1] http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories

[2] http://maven.apache.org/repository-management.html

[3]
http://books.sonatype.com/maven-book/reference/repository-manager.html

[4]
http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feat
ure+Matrix

 

Brian Fox

Apache Maven PMC

http://blogs.sonatype.com/people/brian

 

 

Re: mirrors, oh mirrors

[szczepiq]

>The point of mirrors is to provide an alternate location for the content.

I'd like mirrors to provide multiple alternate locations. I put the
improvement request here: http://jira.codehaus.org/browse/MNG-3772

Cheers,
Szczepan

On Mon, Sep 29, 2008 at 1:41 PM, Jörg Schaible
<[EMAIL PROTECTED]> wrote:
> szczepiq wrote:
>> Hi all,
>>
>> Mirrors are giving me headache recently. See this:
>>
>>   
>> 
>>   corporate-repo
>>   corporate-repo-backup
>>   ...
>>   *
>> 
>> 
>>   corporate-repo-backup
>>   corporate-repo-backup
>>   ...
>>   *
>> 
>>   
>>
>> Above configuration is a dead simple fail-over system. If
>> corporate-repo is down, I want the corporate-repo-backup to mirror
>> everything. Unfortunately it doesn't work :( It seems only last mirror
>> is active when "mirrorOf" property is the same. Is this how it suppose
>> to work? After all, the point of mirrors is to provide multiple
>> locations for the same content, isn't it? Any input?
>
> The point of mirrors is to provide an alternate location for the content. 
> This does not imply fallback. You can use for quite some OS organizations 
> mirrors of their content (Apache, SF,net, ...), however, if you select a 
> mirror and it is not available or out of date and your file is not found, 
> you're also not automagically redirected to a different one, that is 
> available and in sync.
>
> - Jörg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: mirrors, oh mirrors

[Jörg Schaible]

szczepiq wrote:
> Hi all,
> 
> Mirrors are giving me headache recently. See this:
> 
>   
> 
>   corporate-repo
>   corporate-repo-backup
>   ...
>   *
> 
> 
>   corporate-repo-backup
>   corporate-repo-backup
>   ...
>   *
> 
>   
> 
> Above configuration is a dead simple fail-over system. If
> corporate-repo is down, I want the corporate-repo-backup to mirror
> everything. Unfortunately it doesn't work :( It seems only last mirror
> is active when "mirrorOf" property is the same. Is this how it suppose
> to work? After all, the point of mirrors is to provide multiple
> locations for the same content, isn't it? Any input?

The point of mirrors is to provide an alternate location for the content. This 
does not imply fallback. You can use for quite some OS organizations mirrors of 
their content (Apache, SF,net, ...), however, if you select a mirror and it is 
not available or out of date and your file is not found, you're also not 
automagically redirected to a different one, that is available and in sync.

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

mirrors, oh mirrors

[szczepiq]

Hi all,

Mirrors are giving me headache recently. See this:

  

  corporate-repo
  corporate-repo-backup
  ...
  *


  corporate-repo-backup
  corporate-repo-backup
  ...
  *

  

Above configuration is a dead simple fail-over system. If
corporate-repo is down, I want the corporate-repo-backup to mirror
everything. Unfortunately it doesn't work :( It seems only last mirror
is active when "mirrorOf" property is the same. Is this how it suppose
to work? After all, the point of mirrors is to provide multiple
locations for the same content, isn't it? Any input?

Cheers,
Szczepan Faber

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Basic HTTP Auth support for Mirrors

[Jason van Zyl]

Please use [EMAIL PROTECTED] for Nexus questions. We're happy to  
answer your questions there!


On 27-Aug-08, at 10:31 AM, Timothy James Pinet wrote:

I have a Nexus repository setup up to act as a mirror (for both  
internal corp and remote access). However, to restrict access I have  
enabled Basic HTTP Auth via my Apache HTTPD. Is there a tag within  
the settings.xml  that I can add username and password to  
get past the authentication? I only see 
and  in http://maven.apache.org/ref/2.0.8/maven-settings/settings.html 
.


Also, does the mirror support HTTPS?

Thanks,
Tim Pinet


Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
--

believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.

 -- Buddha


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Basic HTTP Auth support for Mirrors

[Timothy James Pinet]

I have a Nexus repository setup up to act as a mirror (for both internal corp 
and remote access). However, to restrict access I have enabled Basic HTTP Auth 
via my Apache HTTPD. Is there a tag within the settings.xml  that I can 
add username and password to get past the authentication? I only see 
   and  in 
http://maven.apache.org/ref/2.0.8/maven-settings/settings.html.

Also, does the mirror support HTTPS?

Thanks,
Tim Pinet

mirrors in settings.xml [Virus checked]

[Wolfgang . Schrecker]

Hi experts,

I run an archiva proxy, which takes care of 'internal' as well as
'snapshots'.
when I configure my mirror in settings, I use


  deployment.webdav
  http://MYSERVERLOCATION/archiva/repository/internal
  *


what is the configuration to use also SNAPSHOTS and internal ?

any pointers ?



mit freundlichen Grüßen/best regards

Wolfgang Schrecker

"Der Inhalt eines Begriffs nimmt ab, wenn sein Umfang zunimmt; wird dieser
allumfassend, so muß der Inhalt ganz verloren gehen."
from G. Frege: Die Grundlagen der Arithmetik S. 40



 --
--

Atos Worldline Processing GmbH
Hahnstrasse 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
mailto:[EMAIL PROTECTED]
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417
 
--

Atos Worldline Processing GmbH
Hahnstraße 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax :
mailto: [EMAIL PROTECTED]
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


* * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *
This e-mail is destined for the above mentioned recipient. In case you
received this e-mail by accident, we would appreciate it if you could
contact the sender and delete all copies stored on your computer.
Please be aware that the security and confidentiality of electronic data
transmitted by e-mail is not completely guaranteed and that data may be seen,
copied, downloaded or changed by third persons during transmission.
Atos Origin accepts no liability for the security and confidentiality of
data and documents sent by e-mail. Please make sure that all important
messages will be confirmed in writing by means of a telefax or a letter.
* * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *

Choosing ids for mirrors and repositories

[Wendy Smoak]

When defining mirrors, do you prefer to use a different id, or are
there any problems with reusing the id for the repo being mirrored?

In other words, would you do this:

  
m-internal <-- different id
internal
...
  

or this

  
internal
internal
...
  

?

Background:  In order to use mirrorOf=*, I find that I have to define
a mirror for all of the repositories I want to allow access to, and
then choose one of those as mirrorOf=* to catch any unwanted extras.
(I don't have a single repo that has everything in it.)

Thanks,
-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: A question about using Mirrors for Repositories

[Thomas Chang]

Hi,
   
  I've installed the Archiba both in office and at home. When I run at home, 
everything is OK. When I do the same in office, I still have problem by 
downloading the 
"http://sap-dev:8080/archiva/repository/internal/org/apache/maven/archetype/maven-archetype/1.0-alpha-7/maven-archetype-1.0-alpha-7.pom";
 though I can access this file with the browser. 
   
  The mirror in my "settings.xml" looks as follow:
  ...
  
  MyMirrorId
  *
  Dependencies for DKV Projects
  http://sap-dev:8080/archiva/repository/internal
  
  ...
   
  Here is the error message:
   
  E:\Projekte>mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=Test
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
Downloading: 
http://sap-dev:8080/archiva/repository/internal/org/apache/maven/archetype/maven-archetype/1.0-alpha-7/maven-archetype-1.0-alpha-7.pom
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.
  GroupId: org.apache.maven.archetype
ArtifactId: maven-archetype
Version: 1.0-alpha-7
  Reason: Unable to download the artifact from any repository
org.apache.maven.archetype:maven-archetype:pom:1.0-alpha-7
  from the specified remote repositories:
  central (http://repo1.maven.org/maven2)
  
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Wed Jan 09 13:05:50 CET 2008
[INFO] Final Memory: 1M/2M
[INFO] 
  E:\Projekte>
   
   
   
   
   
   
  **
   
  How did the artifacts get at your remote repository. (Your server). Do
you use a maven mirror/proxy, like archiva or artifactory or are you
using a local repository on the server. (Which is populated by running
mvn commands on the server)

If you use the second, it is not a real remote repository and then you
notice things like this. (Also not updating of snapshots on your own
local repository).

Please take a look at archiva or artifactory for your remote
repository. It is much easier in use then a remote "local repository".

Hth,

Nick Stolwijk


-Original Message-
From: Thomas Chang [mailto:[EMAIL PROTECTED]
Sent: Fri 1/4/2008 2:50 PM
To: users@maven.apache.org
Subject: Re: A question about using Mirrors for Repositories

The mirror is the repository on the remote server machine. What
metadata files should I use? 
   
  From this mirror I can download all the jars except those of
"org\apache\maven\plugins".
   
   
   
  
  Looks like you are missing some metadata files in the mirror. How did
you populate the mirror?

   
  > Hi all,
>
>   I have a mirror in my "settings.xml" as follow:
>
>   ...
>   
> MyMirrorId
> *
> Dependencies for DKV Projects
> file:sap-dev/CVSREPO/CvsMaven
> 
> ...
>
>   I do so because I want to download the dependencies from the
repository on the server machine. And this runs in most case OK. But
in
somecase it doesn't work. For example when I run "mvn clean", I got
error as
follow. But the Jar "maven-archetype-quickstart-1.0.jar" is on the
repository on the server machine. I have copy this jar into the local
repository. After that the "mvn clean" process can go on, i.e., the
other
jars can be downloaded from the server repository.
>
>   Such a problem happends when I run "mvn eclipse:eclipse". I have to
copy the "maven-eclipse-plugin-2.4.jar" into the local repository.
>
>   Somebody knows why?
>
>   Regards
>
>   Thomas
>
>   
>   [ERROR] BUILD ERROR
> [INFO]


> [INFO] Failed to resolve artifact.
>   GroupId: org.apache.maven.archetypes
> ArtifactId: maven-archetype-quickstart
> Version: RELEASE
>   Reason: Unable to determine the release version
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archetypes
-DartifactId=
> maven-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the
file there:
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.archetypes
-DartifactId=mave
> n-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
>  -Durl=[url] -DrepositoryId=[id]
>
>   org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE
>
>   [INFO]


   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

RE: A question about using Mirrors for Repositories

[Thomas Chang]

Hi,
   
  I've installed the Archiba both in office and at home. When I run at home, 
everything is OK. When I do the same in office, I still have problem by 
downloading the 
"http://sap-dev:8080/archiva/repository/internal/org/apache/maven/archetype/maven-archetype/1.0-alpha-7/maven-archetype-1.0-alpha-7.pom";
 though I can access this file with the browser. 
   
  The mirror in my "settings.xml" looks as follow:
  ...
  
  MyMirrorId
  *
  Dependencies for DKV Projects
  http://sap-dev:8080/archiva/repository/internal
  
  ...
   
  Here is the error message:
   
  E:\Projekte>mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=Test
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
Downloading: 
http://sap-dev:8080/archiva/repository/internal/org/apache/maven/archetype/maven-archetype/1.0-alpha-7/maven-archetype-1.0-alpha-7.pom
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.
  GroupId: org.apache.maven.archetype
ArtifactId: maven-archetype
Version: 1.0-alpha-7
  Reason: Unable to download the artifact from any repository
org.apache.maven.archetype:maven-archetype:pom:1.0-alpha-7
  from the specified remote repositories:
  central (http://repo1.maven.org/maven2)
  
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Wed Jan 09 13:05:50 CET 2008
[INFO] Final Memory: 1M/2M
[INFO] 
  E:\Projekte>
   
   
   
   
   
   
  **
   
  How did the artifacts get at your remote repository. (Your server). Do
 you use a maven mirror/proxy, like archiva or artifactory or are you
 using a local repository on the server. (Which is populated by running
 mvn commands on the server)

If you use the second, it is not a real remote repository and then you
 notice things like this. (Also not updating of snapshots on your own
 local repository).

Please take a look at archiva or artifactory for your remote
 repository. It is much easier in use then a remote "local repository".

Hth,

Nick Stolwijk


-Original Message-
From: Thomas Chang [mailto:[EMAIL PROTECTED]
Sent: Fri 1/4/2008 2:50 PM
To: users@maven.apache.org
Subject: Re: A question about using Mirrors for Repositories
 
The mirror is the repository on the remote server machine. What
 metadata files should I use? 
   
  From this mirror I can download all the jars except those of
 "org\apache\maven\plugins".
   
   
   
  
  Looks like you are missing some metadata files in the mirror. How did
you populate the mirror?

   
  > Hi all,
>
>   I have a mirror in my "settings.xml" as follow:
>
>   ...
>   
> MyMirrorId
> *
> Dependencies for DKV Projects
> file:sap-dev/CVSREPO/CvsMaven
> 
> ...
>
>   I do so because I want to download the dependencies from the
 repository on the server machine. And this runs in most case OK. But
 in
 somecase it doesn't work. For example when I run "mvn clean", I got
 error as
 follow. But the Jar "maven-archetype-quickstart-1.0.jar" is on the
 repository on the server machine. I have copy this jar into the local
 repository. After that the "mvn clean" process can go on, i.e., the
 other
 jars can be downloaded from the server repository.
>
>   Such a problem happends when I run "mvn eclipse:eclipse". I have to
 copy the "maven-eclipse-plugin-2.4.jar" into the local repository.
>
>   Somebody knows why?
>
>   Regards
>
>   Thomas
>
>   
>   [ERROR] BUILD ERROR
> [INFO]

 
> [INFO] Failed to resolve artifact.
>   GroupId: org.apache.maven.archetypes
> ArtifactId: maven-archetype-quickstart
> Version: RELEASE
>   Reason: Unable to determine the release version
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=
> maven-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the
 file there:
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=mave
> n-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
>  -Durl=[url] -DrepositoryId=[id]
>
>   org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE
>
>   [INFO]


   
-
Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. 

Re: A question about using Mirrors for Repositories

[Wendy Smoak]

On Jan 5, 2008 2:46 AM, Thomas Chang <[EMAIL PROTECTED]> wrote:

> I am going to use the archiva. But the archiva 1.0 needs jdk 1.5. That means 
> I have to set the JAVA_HOME to point to the jdk 1.5. But many of my programms 
> use jdk 1.4 and I can't change the JAVA_HOME to point to the jdk 1.4
>
>   Any sujestion?

Archiva has separate mailing lists, please come join us if you have
more questions... http://maven.apache.org/archiva/mail-lists.html

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: A question about using Mirrors for Repositories

[Heinrich Nirschl]

On Jan 5, 2008 10:46 AM, Thomas Chang <[EMAIL PROTECTED]> wrote:
> I am going to use the archiva. But the archiva 1.0 needs jdk 1.5. That means 
> I have to set the JAVA_HOME to point to the jdk 1.5. But many of my programms 
> use jdk 1.4 and I can't change the JAVA_HOME to point to the jdk 1.4
>
>   Any sujestion?
>

I do not really see the problem. You will have one archiva instance
for the whole team that runs under a different account on the server.
Its easy to setup JAVA_HOME differently on the server and on the
developer machines. Even if you share a machine, the environment
variables can be set up per account or a little shell wrapper can do
the trick.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: A question about using Mirrors for Repositories

[Thomas Chang]

How did the artifacts get at your remote repository. (Your server). Do
 you use a maven mirror/proxy, like archiva or artifactory or are you
 using a local repository on the server. (Which is populated by running
 mvn commands on the server)

If you use the second, it is not a real remote repository and then you
 notice things like this. (Also not updating of snapshots on your own
 local repository).

Please take a look at archiva or artifactory for your remote
 repository. It is much easier in use then a remote "local repository".

Hth,

Nick Stolwijk

I am going to use the archiva. But the archiva 1.0 needs jdk 1.5. That means I 
have to set the JAVA_HOME to point to the jdk 1.5. But many of my programms use 
jdk 1.4 and I can't change the JAVA_HOME to point to the jdk 1.4
   
  Any sujestion?
   
  *
-Original Message-
From: Thomas Chang [mailto:[EMAIL PROTECTED]
Sent: Fri 1/4/2008 2:50 PM
To: users@maven.apache.org
Subject: Re: A question about using Mirrors for Repositories
 
The mirror is the repository on the remote server machine. What
 metadata files should I use? 
   
  From this mirror I can download all the jars except those of
 "org\apache\maven\plugins".


   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

RE: A question about using Mirrors for Repositories

[nicklist]

Afaik, that is because with "normal" artifacts you are looking for 
com.example:example:1.0 from which a complete url to the pom and jar files can 
be created. With plugins you are looking for 
org.apache.maven.plugins:maven-example-plugin:LATEST for which there should be 
some checking in the metadata.xml on the remote server, which you don't have.

To have a quick solution (and it is always best practice), create a 
pluginmanagement in your pom file and version each plugin you use. It is also 
better for reproducible builds. You don't want a tag to break because one of 
the plugins the build uses is updated.

Hth,

Nick Stolwijk


-Original Message-
From: Thomas Chang [mailto:[EMAIL PROTECTED]
Sent: Fri 1/4/2008 4:03 PM
To: Maven Users List
Subject: RE: A question about using Mirrors for Repositories
 
You are right. I use the local repository on the server machine as a remote 
repository to my local client.
   
  But I wonder why the other jars can be downloaded except those of
"org\apache\maven\plugins"?

   
  
   
  How did the artifacts get at your remote repository. (Your server). Do
 you use a maven mirror/proxy, like archiva or artifactory or are you
 using a local repository on the server. (Which is populated by running
 mvn commands on the server)

If you use the second, it is not a real remote repository and then you
 notice things like this. (Also not updating of snapshots on your own
 local repository).

Please take a look at archiva or artifactory for your remote
 repository. It is much easier in use then a remote "local repository".

Hth,

Nick Stolwijk


-Original Message-
From: Thomas Chang [mailto:[EMAIL PROTECTED]
Sent: Fri 1/4/2008 2:50 PM
To: users@maven.apache.org
Subject: Re: A question about using Mirrors for Repositories
 
The mirror is the repository on the remote server machine. What
 metadata files should I use? 
   
  From this mirror I can download all the jars except those of
 "org\apache\maven\plugins".
   
   
   
  
  Looks like you are missing some metadata files in the mirror. How did
you populate the mirror?

   
  > Hi all,
>
>   I have a mirror in my "settings.xml" as follow:
>
>   ...
>   
> MyMirrorId
> *
> Dependencies for DKV Projects
> file:sap-dev/CVSREPO/CvsMaven
> 
> ...
>
>   I do so because I want to download the dependencies from the
 repository on the server machine. And this runs in most case OK. But
 in
 somecase it doesn't work. For example when I run "mvn clean", I got
 error as
 follow. But the Jar "maven-archetype-quickstart-1.0.jar" is on the
 repository on the server machine. I have copy this jar into the local
 repository. After that the "mvn clean" process can go on, i.e., the
 other
 jars can be downloaded from the server repository.
>
>   Such a problem happends when I run "mvn eclipse:eclipse". I have to
 copy the "maven-eclipse-plugin-2.4.jar" into the local repository.
>
>   Somebody knows why?
>
>   Regards
>
>   Thomas
>
>   
>   [ERROR] BUILD ERROR
> [INFO]

 
> [INFO] Failed to resolve artifact.
>   GroupId: org.apache.maven.archetypes
> ArtifactId: maven-archetype-quickstart
> Version: RELEASE
>   Reason: Unable to determine the release version
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=
> maven-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the
 file there:
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=mave
> n-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
>  -Durl=[url] -DrepositoryId=[id]
>
>   org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE
>
>   [INFO]

 
> [INFO] For more information, run Maven with the -e switch
> [INFO]

 
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Jan 04 11:03:38 CET 2008
> [INFO] Final Memory: 4M/8M
> [INFO]

 


   
-
Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. 

Re: A question about using Mirrors for Repositories

[Heinrich Nirschl]

In some situations maven needs additional information for resolving
artifacts. This info is stored in the metadata files in the
repository. Since the filenames of these metadata files are different
in local and remote repositories it does not work to misuse a local
repository as a remote one.

It is mere luck, that sometimes the download works in spite of that.

As Nick already suggested, consider to install a repository manager.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: A question about using Mirrors for Repositories

[Thomas Chang]

You are right. I use the local repository on the server machine as a remote 
repository to my local client.
   
  But I wonder why the other jars can be downloaded except those of
"org\apache\maven\plugins"?

   
  
   
  How did the artifacts get at your remote repository. (Your server). Do
 you use a maven mirror/proxy, like archiva or artifactory or are you
 using a local repository on the server. (Which is populated by running
 mvn commands on the server)

If you use the second, it is not a real remote repository and then you
 notice things like this. (Also not updating of snapshots on your own
 local repository).

Please take a look at archiva or artifactory for your remote
 repository. It is much easier in use then a remote "local repository".

Hth,

Nick Stolwijk


-Original Message-
From: Thomas Chang [mailto:[EMAIL PROTECTED]
Sent: Fri 1/4/2008 2:50 PM
To: users@maven.apache.org
Subject: Re: A question about using Mirrors for Repositories
 
The mirror is the repository on the remote server machine. What
 metadata files should I use? 
   
  From this mirror I can download all the jars except those of
 "org\apache\maven\plugins".
   
   
   
  
  Looks like you are missing some metadata files in the mirror. How did
you populate the mirror?

   
  > Hi all,
>
>   I have a mirror in my "settings.xml" as follow:
>
>   ...
>   
> MyMirrorId
> *
> Dependencies for DKV Projects
> file:sap-dev/CVSREPO/CvsMaven
> 
> ...
>
>   I do so because I want to download the dependencies from the
 repository on the server machine. And this runs in most case OK. But
 in
 somecase it doesn't work. For example when I run "mvn clean", I got
 error as
 follow. But the Jar "maven-archetype-quickstart-1.0.jar" is on the
 repository on the server machine. I have copy this jar into the local
 repository. After that the "mvn clean" process can go on, i.e., the
 other
 jars can be downloaded from the server repository.
>
>   Such a problem happends when I run "mvn eclipse:eclipse". I have to
 copy the "maven-eclipse-plugin-2.4.jar" into the local repository.
>
>   Somebody knows why?
>
>   Regards
>
>   Thomas
>
>   
>   [ERROR] BUILD ERROR
> [INFO]

 
> [INFO] Failed to resolve artifact.
>   GroupId: org.apache.maven.archetypes
> ArtifactId: maven-archetype-quickstart
> Version: RELEASE
>   Reason: Unable to determine the release version
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=
> maven-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the
 file there:
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=mave
> n-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
>  -Durl=[url] -DrepositoryId=[id]
>
>   org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE
>
>   [INFO]

 
> [INFO] For more information, run Maven with the -e switch
> [INFO]

 
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Jan 04 11:03:38 CET 2008
> [INFO] Final Memory: 4M/8M
> [INFO]

 


   
-
Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. 

RE: A question about using Mirrors for Repositories

[nicklist]

How did the artifacts get at your remote repository. (Your server). Do you use 
a maven mirror/proxy, like archiva or artifactory or are you using a local 
repository on the server. (Which is populated by running mvn commands on the 
server)

If you use the second, it is not a real remote repository and then you notice 
things like this. (Also not updating of snapshots on your own local repository).

Please take a look at archiva or artifactory for your remote repository. It is 
much easier in use then a remote "local repository".

Hth,

Nick Stolwijk


-Original Message-
From: Thomas Chang [mailto:[EMAIL PROTECTED]
Sent: Fri 1/4/2008 2:50 PM
To: users@maven.apache.org
Subject: Re: A question about using Mirrors for Repositories
 
The mirror is the repository on the remote server machine. What metadata files 
should I use? 
   
  From this mirror I can download all the jars except those of 
"org\apache\maven\plugins".
   
   
   
  
  Looks like you are missing some metadata files in the mirror. How did
you populate the mirror?

   
  > Hi all,
>
>   I have a mirror in my "settings.xml" as follow:
>
>   ...
>   
> MyMirrorId
> *
> Dependencies for DKV Projects
> file:sap-dev/CVSREPO/CvsMaven
> 
> ...
>
>   I do so because I want to download the dependencies from the
 repository on the server machine. And this runs in most case OK. But in
 somecase it doesn't work. For example when I run "mvn clean", I got error as
 follow. But the Jar "maven-archetype-quickstart-1.0.jar" is on the
 repository on the server machine. I have copy this jar into the local
 repository. After that the "mvn clean" process can go on, i.e., the other
 jars can be downloaded from the server repository.
>
>   Such a problem happends when I run "mvn eclipse:eclipse". I have to
 copy the "maven-eclipse-plugin-2.4.jar" into the local repository.
>
>   Somebody knows why?
>
>   Regards
>
>   Thomas
>
>   
>   [ERROR] BUILD ERROR
> [INFO]
 
> [INFO] Failed to resolve artifact.
>   GroupId: org.apache.maven.archetypes
> ArtifactId: maven-archetype-quickstart
> Version: RELEASE
>   Reason: Unable to determine the release version
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=
> maven-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the
 file there:
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=mave
> n-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
>  -Durl=[url] -DrepositoryId=[id]
>
>   org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE
>
>   [INFO]
 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
 
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Jan 04 11:03:38 CET 2008
> [INFO] Final Memory: 4M/8M
> [INFO]
 
>
>
>
>
> -
> Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern.



   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

Re: A question about using Mirrors for Repositories

[Thomas Chang]

The mirror is the repository on the remote server machine. What metadata files 
should I use? 
   
  From this mirror I can download all the jars except those of 
"org\apache\maven\plugins".
   
   
   
  
  Looks like you are missing some metadata files in the mirror. How did
you populate the mirror?

   
  > Hi all,
>
>   I have a mirror in my "settings.xml" as follow:
>
>   ...
>   
> MyMirrorId
> *
> Dependencies for DKV Projects
> file:sap-dev/CVSREPO/CvsMaven
> 
> ...
>
>   I do so because I want to download the dependencies from the
 repository on the server machine. And this runs in most case OK. But in
 somecase it doesn't work. For example when I run "mvn clean", I got error as
 follow. But the Jar "maven-archetype-quickstart-1.0.jar" is on the
 repository on the server machine. I have copy this jar into the local
 repository. After that the "mvn clean" process can go on, i.e., the other
 jars can be downloaded from the server repository.
>
>   Such a problem happends when I run "mvn eclipse:eclipse". I have to
 copy the "maven-eclipse-plugin-2.4.jar" into the local repository.
>
>   Somebody knows why?
>
>   Regards
>
>   Thomas
>
>   
>   [ERROR] BUILD ERROR
> [INFO]
 
> [INFO] Failed to resolve artifact.
>   GroupId: org.apache.maven.archetypes
> ArtifactId: maven-archetype-quickstart
> Version: RELEASE
>   Reason: Unable to determine the release version
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=
> maven-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the
 file there:
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.archetypes
 -DartifactId=mave
> n-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
>  -Durl=[url] -DrepositoryId=[id]
>
>   org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE
>
>   [INFO]
 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
 
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Jan 04 11:03:38 CET 2008
> [INFO] Final Memory: 4M/8M
> [INFO]
 
>
>
>
>
> -
> Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern.



   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

Re: A question about using Mirrors for Repositories

[Heinrich Nirschl]

On Jan 4, 2008 11:42 AM, Thomas Chang <[EMAIL PROTECTED]> wrote:
> Hi all,
>
>   I have a mirror in my "settings.xml" as follow:
>
>   ...
>   
> MyMirrorId
> *
> Dependencies for DKV Projects
> file:sap-dev/CVSREPO/CvsMaven
> 
> ...
>
>   I do so because I want to download the dependencies from the repository on 
> the server machine. And this runs in most case OK. But in somecase it doesn't 
> work. For example when I run "mvn clean", I got error as follow. But the Jar 
> "maven-archetype-quickstart-1.0.jar" is on the repository on the server 
> machine. I have copy this jar into the local repository. After that the "mvn 
> clean" process can go on, i.e., the other jars can be downloaded from the 
> server repository.
>
>   Such a problem happends when I run "mvn eclipse:eclipse". I have to copy 
> the "maven-eclipse-plugin-2.4.jar" into the local repository.
>
>   Somebody knows why?
>
>   Regards
>
>   Thomas
>
>   
>   [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Failed to resolve artifact.
>   GroupId: org.apache.maven.archetypes
> ArtifactId: maven-archetype-quickstart
> Version: RELEASE
>   Reason: Unable to determine the release version
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.archetypes 
> -DartifactId=
> maven-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
>   mvn deploy:deploy-file -DgroupId=org.apache.maven.archetypes 
> -DartifactId=mave
> n-archetype-quickstart \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
>  -Durl=[url] -DrepositoryId=[id]
>
>   org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE
>
>   [INFO] 
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> 
> [INFO] Total time: 1 second
> [INFO] Finished at: Fri Jan 04 11:03:38 CET 2008
> [INFO] Final Memory: 4M/8M
> [INFO] 
> 
>
>
>
>
> -
> Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern.

Looks like you are missing some metadata files in the mirror. How did
you populate the mirror?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]