Antwort: RE: Antwort: RE: Antwort: RE: Proxy settings
Mohni, Daniel [EMAIL PROTECTED] schrieb am 05.12.2006 07:28:36: - Generic proxy (so the POMs can't mess with your mirror settings). from my point of view this has nothing to do with archiva, this is a maven problem. I don't know if you can setup a generic proxy in your settings.xml as I didn't find anyhing in the documentation, but maybe there is a hidden option ;-) checkout http://maven.apache.org/settings.html The setting is called proxy. This allows to inject a proxy server which could filter all HTTP requests sent out by maven. Regards, -- Aaron Digulla
RE: Proxy settings
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 05, 2006 9:43 AM To: archiva-users@maven.apache.org Subject: Antwort: RE: Antwort: RE: Antwort: RE: Proxy settings Mohni, Daniel [EMAIL PROTECTED] schrieb am 05.12.2006 07:28:36: - Generic proxy (so the POMs can't mess with your mirror settings). from my point of view this has nothing to do with archiva, this is a maven problem. I don't know if you can setup a generic proxy in your settings.xml as I didn't find anyhing in the documentation, but maybe there is a hidden option ;-) checkout http://maven.apache.org/settings.html The setting is called proxy. This allows to inject a proxy server which could filter all HTTP requests sent out by maven. never tried this one :-( , do you get any artefacts from archiva using only the proxy setup ? there was a problem with the proxy servlet, as soon as you have more than one proxied repo's the access without 'repo-id' didn't work, maybe this is fixed now I don't think that the proxy servlet is implemented the way you want to use it, but I may be wrong... check org.apache.maven.archiva.proxy.DefaultProxyManager org.apache.maven.archiva.proxy.DefaultProxyRequestHandler maybe you can provide a patch Regards Daniel
Re: Antwort: RE: Antwort: RE: Proxy settings
On 12/4/06, Mohni, Daniel [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] My position is that the POMs which come from the main sites can (and will) contain anything (even illegal XML, broken checksums, etc). The proxy has to handle all these case gracefully or at least to support the admin in doing so. I'm missing these functions in archiva: - Generic proxy (so the POMs can't mess with your mirror settings). from my point of view this has nothing to do with archiva, this is a maven problem. I don't know if you can setup a generic proxy in your settings.xml as I didn't find anyhing in the documentation, but maybe there is a hidden option ;-) checkout http://maven.apache.org/settings.html You can use * as mirror id to mactch all servers since maven 2.0.5 (not yet released) or Maestro 1.1 that you can get from http://www.mergere.com/ - Regenerate checksum (for all downloads which I needed to fix) As far as I know this is one of the features that will be implemented into archiva, maybe it's already in the daily builds but I didn't tested them the last few days... - Lock down file (so Archiva will not try to download it again even if the remote site says but I have new version or the user says get the newest, hottest snapshots!). this can be done be done on user site with the usePluginRegistry property set to true, but this is not realy nice as you will have to confirm every plugin version... loking files in the proxy is only usefull if this is used for all users, is this realy what you want ? What will you do if another team use another version I can live without the last two but the first one is a must, IMHO. - fill an issue on the maven project, maybe it's already in jira... just my two cents Daniel -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
RE: Proxy settings
You can use * as mirror id to mactch all servers since maven 2.0.5 (not yet released) or Maestro 1.1 that you can get from http://www.mergere.com/ 1. How can I get maven 2.0.5? Or maven 2.1? Should I checkout from Subversion or is there a download? 2. Which proxy supports this? In Archiva, I have to specify exactly which URL should be mirrored (additionally to the mirrors in settings.xml). Does it work with Proxmitiy? Or maven-proxy? Regards, -- Aaron Digulla
RE: Antwort: RE: Antwort: RE: Proxy settings
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] My position is that the POMs which come from the main sites can (and will) contain anything (even illegal XML, broken checksums, etc). The proxy has to handle all these case gracefully or at least to support the admin in doing so. I'm missing these functions in archiva: - Generic proxy (so the POMs can't mess with your mirror settings). from my point of view this has nothing to do with archiva, this is a maven problem. I don't know if you can setup a generic proxy in your settings.xml as I didn't find anyhing in the documentation, but maybe there is a hidden option ;-) checkout http://maven.apache.org/settings.html - Regenerate checksum (for all downloads which I needed to fix) As far as I know this is one of the features that will be implemented into archiva, maybe it's already in the daily builds but I didn't tested them the last few days... - Lock down file (so Archiva will not try to download it again even if the remote site says but I have new version or the user says get the newest, hottest snapshots!). this can be done be done on user site with the usePluginRegistry property set to true, but this is not realy nice as you will have to confirm every plugin version... loking files in the proxy is only usefull if this is used for all users, is this realy what you want ? What will you do if another team use another version I can live without the last two but the first one is a must, IMHO. - fill an issue on the maven project, maybe it's already in jira... just my two cents Daniel
RE: Proxy settings
Hello Aaron this can be done setting the mirror in settings.xml mirrors mirror idproxy.central/id mirrorOfcentral/mirrorOf nameInternal Mirror of central./name urlhttp://archiva/proxy/maven_release/url /mirror /mirrors - if you use proxy in the url then archiva will try to download missing artefacts from the proxied repo setup in archiva http://archiva/proxy/maven_release - if you use repository in the url then archiva will only be a cache provider for your already downloaded artefacts http://archiva/repository/maven_release maven_release is our internal proxy repository... I don't know if this is still like this in the current daily build as I didn't tried it... hth Daniel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 11:19 AM To: archiva-users@maven.apache.org Subject: Proxy settings Hello, We're using maven for internal development. Since the internet as a whole and our connection to it especially are not always reliable (for example, a new version of a virus checker sometimes starts to block out maven downloads), we wanted to use Archiva as a local cache of the central maven repositories. As it is right now, I have to configure each repository individually. What we would prefer is a setting which makes Archiva the default proxy for maven so all external connections are made over it. This would allow us to keep local copies of all artefacts so internet outages wouldn't affect us anymore. Also, we could fix broken packages locally. Ideally, there should be two caches: One with stable version for development and one which can update itself with the current versions from the internet. Is this possible? Regards, -- Aaron Digulla
Antwort: RE: Proxy settings
Hi Daniel, What do I do if POM.xml of a plugin says this: repositories repository idapache-snapshots/id nameSnapshot repository/name urlhttp://people.apache.org/maven-snapshot-repository//url /repository /repositories but the plugin cannot be found in this repository? Like in the JSP compiler maven plugin from codehaus. My problem is the id. Every project defines their own id. For some, it's codehaus, for others it's codehaus.org. For another group, codehaus is for releases, while codehaus.org is for snapshots. This means the id *cannot* be used to map mirrors to URLs. Therefore, I need a solution in archiva which I can feed with arbitrary URLs and which either goes to a stable inhouse repository or downloads the resource from the URL and caches it. Having users define proxied repositories manually and map them to managed repositories is not the solution, it's another layer of problems. Archia should support a generic proxy/cache which just stores a resource under an URL. So when I ask for apache.org/.../plugin-1.3.pom and for codehaus.org/.../plugin-1.3.pom, I should get two different files if they are different on the respective servers. On disk, you can just use the hostname as the first item in the path to distinguish between the different artefacts. In the webapp, it should be possible to freeze certain URLs (for example, if the files on the web are broken or I'm using a patched version inhouse). With this solution, I could use the Maven proxy settings (instead of the broken mirror stuff) to download artefacts for my development team *once*. Regards, -- Aaron Digulla Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 11:31:28: Hello Aaron this can be done setting the mirror in settings.xml mirrors mirror idproxy.central/id mirrorOfcentral/mirrorOf nameInternal Mirror of central./name urlhttp://archiva/proxy/maven_release/url /mirror /mirrors - if you use proxy in the url then archiva will try to download missing artefacts from the proxied repo setup in archiva http://archiva/proxy/maven_release - if you use repository in the url then archiva will only be a cache provider for your already downloaded artefacts http://archiva/repository/maven_release maven_release is our internal proxy repository... I don't know if this is still like this in the current daily build as I didn't tried it... hth Daniel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 11:19 AM To: archiva-users@maven.apache.org Subject: Proxy settings Hello, We're using maven for internal development. Since the internet as a whole and our connection to it especially are not always reliable (for example, a new version of a virus checker sometimes starts to block out maven downloads), we wanted to use Archiva as a local cache of the central maven repositories. As it is right now, I have to configure each repository individually. What we would prefer is a setting which makes Archiva the default proxy for maven so all external connections are made over it. This would allow us to keep local copies of all artefacts so internet outages wouldn't affect us anymore. Also, we could fix broken packages locally. Ideally, there should be two caches: One with stable version for development and one which can update itself with the current versions from the internet. Is this possible? Regards, -- Aaron Digulla
RE: Antwort: RE: Proxy settings
Hello again all I can say about this is that a lot of the current maven2 plugins are still in development and not in release state. this is also why they have this snapshot repositories in their pom... but they are going to be stable quite soon, hopefully... using snapshot dependency that you can not control is a mess, in a customer project. If you realy need a snapshot version for your project, then the workaround is to build the plugin from source with your custom artifactId and deploy it to your repository. it's not very nice but in this case you have control over the used version in your project until the plugin is stable. A released plugin should not have a repository entry in his pom.xml !!! that's my opinion, but maybe it's wrong... Maybe someone else can help you out sorry Daniel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 2:51 PM To: archiva-users@maven.apache.org Subject: Antwort: RE: Proxy settings Hi Daniel, What do I do if POM.xml of a plugin says this: repositories repository idapache-snapshots/id nameSnapshot repository/name urlhttp://people.apache.org/maven-snapshot-repository//url /repository /repositories but the plugin cannot be found in this repository? Like in the JSP compiler maven plugin from codehaus. My problem is the id. Every project defines their own id. For some, it's codehaus, for others it's codehaus.org. For another group, codehaus is for releases, while codehaus.org is for snapshots. This means the id *cannot* be used to map mirrors to URLs. Therefore, I need a solution in archiva which I can feed with arbitrary URLs and which either goes to a stable inhouse repository or downloads the resource from the URL and caches it. Having users define proxied repositories manually and map them to managed repositories is not the solution, it's another layer of problems. Archia should support a generic proxy/cache which just stores a resource under an URL. So when I ask for apache.org/.../plugin-1.3.pom and for codehaus.org/.../plugin-1.3.pom, I should get two different files if they are different on the respective servers. On disk, you can just use the hostname as the first item in the path to distinguish between the different artefacts. In the webapp, it should be possible to freeze certain URLs (for example, if the files on the web are broken or I'm using a patched version inhouse). With this solution, I could use the Maven proxy settings (instead of the broken mirror stuff) to download artefacts for my development team *once*. Regards, -- Aaron Digulla Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 11:31:28: Hello Aaron this can be done setting the mirror in settings.xml mirrors mirror idproxy.central/id mirrorOfcentral/mirrorOf nameInternal Mirror of central./name urlhttp://archiva/proxy/maven_release/url /mirror /mirrors - if you use proxy in the url then archiva will try to download missing artefacts from the proxied repo setup in archiva http://archiva/proxy/maven_release - if you use repository in the url then archiva will only be a cache provider for your already downloaded artefacts http://archiva/repository/maven_release maven_release is our internal proxy repository... I don't know if this is still like this in the current daily build as I didn't tried it... hth Daniel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 11:19 AM To: archiva-users@maven.apache.org Subject: Proxy settings Hello, We're using maven for internal development. Since the internet as a whole and our connection to it especially are not always reliable (for example, a new version of a virus checker sometimes starts to block out maven downloads), we wanted to use Archiva as a local cache of the central maven repositories. As it is right now, I have to configure each repository individually. What we would prefer is a setting which makes Archiva the default proxy for maven so all external connections are made over it. This would allow us to keep local copies of all artefacts so internet outages wouldn't affect us anymore. Also, we could fix broken packages locally. Ideally, there should be two caches: One with stable version for development and one which can update itself with the current versions from the internet. Is this possible? Regards, -- Aaron Digulla
RE: Antwort: RE: Proxy settings
I completely agree with both statements: 1) snapshot dependency that you can not control is a mess, in a customer project ... build the plugin from source with your custom artifactId and deploy it to your repository and 2) A released plugin should not have a repository entry in his pom.xml I ran into this recently when people.apache.org was down during a data center move. I was just setting up my repository the day before so I got caught in the maelstrom before I could take corrective action. However, a fair number of released plugins had references to people.apache.org that should not have been there. This tends to be a real problem with codehaus projects. At the very least, snapshot and release repositories should be properly labeled as such if they are going to be included. sw -Original Message- From: Mohni, Daniel [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 9:15 AM To: archiva-users@maven.apache.org Subject: RE: Antwort: RE: Proxy settings Hello again all I can say about this is that a lot of the current maven2 plugins are still in development and not in release state. this is also why they have this snapshot repositories in their pom... but they are going to be stable quite soon, hopefully... using snapshot dependency that you can not control is a mess, in a customer project. If you realy need a snapshot version for your project, then the workaround is to build the plugin from source with your custom artifactId and deploy it to your repository. it's not very nice but in this case you have control over the used version in your project until the plugin is stable. A released plugin should not have a repository entry in his pom.xml !!! that's my opinion, but maybe it's wrong... Maybe someone else can help you out sorry Daniel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 2:51 PM To: archiva-users@maven.apache.org Subject: Antwort: RE: Proxy settings Hi Daniel, What do I do if POM.xml of a plugin says this: repositories repository idapache-snapshots/id nameSnapshot repository/name urlhttp://people.apache.org/maven-snapshot-repository//url /repository /repositories but the plugin cannot be found in this repository? Like in the JSP compiler maven plugin from codehaus. My problem is the id. Every project defines their own id. For some, it's codehaus, for others it's codehaus.org. For another group, codehaus is for releases, while codehaus.org is for snapshots. This means the id *cannot* be used to map mirrors to URLs. Therefore, I need a solution in archiva which I can feed with arbitrary URLs and which either goes to a stable inhouse repository or downloads the resource from the URL and caches it. Having users define proxied repositories manually and map them to managed repositories is not the solution, it's another layer of problems. Archia should support a generic proxy/cache which just stores a resource under an URL. So when I ask for apache.org/.../plugin-1.3.pom and for codehaus.org/.../plugin-1.3.pom, I should get two different files if they are different on the respective servers. On disk, you can just use the hostname as the first item in the path to distinguish between the different artefacts. In the webapp, it should be possible to freeze certain URLs (for example, if the files on the web are broken or I'm using a patched version inhouse). With this solution, I could use the Maven proxy settings (instead of the broken mirror stuff) to download artefacts for my development team *once*. Regards, -- Aaron Digulla Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 11:31:28: Hello Aaron this can be done setting the mirror in settings.xml mirrors mirror idproxy.central/id mirrorOfcentral/mirrorOf nameInternal Mirror of central./name urlhttp://archiva/proxy/maven_release/url /mirror /mirrors - if you use proxy in the url then archiva will try to download missing artefacts from the proxied repo setup in archiva http://archiva/proxy/maven_release - if you use repository in the url then archiva will only be a cache provider for your already downloaded artefacts http://archiva/repository/maven_release maven_release is our internal proxy repository... I don't know if this is still like this in the current daily build as I didn't tried it... hth Daniel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 11:19 AM To: archiva-users@maven.apache.org Subject: Proxy settings Hello, We're using maven for internal development. Since the internet as a whole and our connection to it especially are not always reliable (for example, a new version
Antwort: RE: Antwort: RE: Proxy settings
Mohni, Daniel [EMAIL PROTECTED] schrieb am 04.12.2006 15:15:13: A released plugin should not have a repository entry in his pom.xml !!! that's my opinion, but maybe it's wrong... My position is that the POMs which come from the main sites can (and will) contain anything (even illegal XML, broken checksums, etc). The proxy has to handle all these case gracefully or at least to support the admin in doing so. I'm missing these functions in archiva: - Generic proxy (so the POMs can't mess with your mirror settings). - Regenerate checksum (for all downloads which I needed to fix) - Lock down file (so Archiva will not try to download it again even if the remote site says but I have new version or the user says get the newest, hottest snapshots!). I can live without the last two but the first one is a must, IMHO. Regards, -- Aaron Digulla
RE: Proxy settings
Sam Wilson [EMAIL PROTECTED] schrieb am 04.12.2006 16:27:59: At the very least, snapshot and release repositories should be properly labeled as such if they are going to be included. No matter how hard you wish, there will always be a broken POM out there and there should be a reliable, understandable, simple way to make my build work again (and that of my 15 colleagues who depend on my work on the proxy). Regards, -- Aaron Digulla
Re: Proxy settings
On Tuesday 02 May 2006 9:47 am, Alexandre Poitras wrote: Hi, I was wondering how laptops users were dealing with proxy settings in Maven 2. For my part, since profiles can't enable/disable proxy, I disable it manually whenever I work at home. It's a little bit annoying and so I was wondering if anyone had found a workaround. Any suggestions? Thank! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Have you tried two profiles? One with proxy, the other without? Then use the appropriate profile depending on where you are. HTH, Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proxy settings
I agree with you Alexandre. Sounds like a good JIRA Enhancement request for 2.1. Wayne On 5/4/06, Alexandre Poitras [EMAIL PROTECTED] wrote: You can't change the proxy settings using a profile. I think they forgot about laptop. On 5/4/06, Henry S. Isidro [EMAIL PROTECTED] wrote: On Tuesday 02 May 2006 9:47 am, Alexandre Poitras wrote: Hi, I was wondering how laptops users were dealing with proxy settings in Maven 2. For my part, since profiles can't enable/disable proxy, I disable it manually whenever I work at home. It's a little bit annoying and so I was wondering if anyone had found a workaround. Any suggestions? Thank! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Have you tried two profiles? One with proxy, the other without? Then use the appropriate profile depending on where you are. HTH, Henry - 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: Proxy settings question
.pac files aren't supported yet. You must download and edit your .pac file. Your proxy host/port is defined in it. Emmanuel Dave Hoffer a écrit : I understand that if I need to run maven2 from behind a proxy I need to configure the following section in my settings.xml file: proxy activetrue/active protocolhttp/protocol hostproxy.somewhere.com/host port8080/port usernameproxyuser/username passwordsomepassword/password nonProxyHostswww.google.com|*.somewhere.com/nonProxyHosts /proxy I am not clear what I need to use for the host tag, in browsers we need to use firewall.xrite.com/proxy.pac, how should I configure this for maven2? -dh - 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: Proxy settings question
Open your proxy.pac . It goes through some rules - probably depending on IPs - and eventually returns the proxy host and port, e.g. ' return PROXY 20.140.15.83:3128; ' -- host = 20.140.15.83 ; port = 3128 - Yann 2006/2/22, Dave Hoffer [EMAIL PROTECTED]: I understand that if I need to run maven2 from behind a proxy I need to configure the following section in my settings.xml file: proxy activetrue/active protocolhttp/protocol hostproxy.somewhere.com/host port8080/port usernameproxyuser/username passwordsomepassword/password nonProxyHostswww.google.com|*.somewhere.com/nonProxyHosts /proxy I am not clear what I need to use for the host tag, in browsers we need to use firewall.xrite.com/proxy.pac, how should I configure this for maven2? -dh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proxy settings and different remote repos
Unfortunately no. Maven 1.1 does accept proxy exclusions, but not 1.0.2. You can see if httpclient will pick them up via the standard java system property: -Dproxy.nonProxyHosts=*.mycompany.com Another alternative is to set up maven-proxy on your company repo - all your clients can connect to that, and it will fallback to ibiblio when not saved locally. - Brett On Apr 11, 2005 9:42 PM, Guillaume Laforge [EMAIL PROTECTED] wrote: Hello, I want to use two different repositories: a company-wide repository, and in second place to fall through to ibiblio if I can't find an artifact in the company repository. The problem comes in when I have to specify my proxy settings: to access my company repo, I don't need to specify my proxy settings, but to access ibiblio, that's mandatory. So the question is: is there a solution to that dilema? How can I specify two remote repositories requiring different proxy settings (or no settings at all to be clear)? Does Maven provide some magic parameters for that? Thanks in advance, -- Guillaume Laforge http://glaforge.free.fr/weblog/?catid=2 - 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]
