You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Tom DeWire (JIRA)" <ji...@codehaus.org> on 2008/12/10 23:32:19 UTC
[jira] Created: (MRM-1035) Remote, legacy (Maven 1) repositories
appear to be consulted for all artifacts, even if no appropriate proxy
connector has been defined.
Remote, legacy (Maven 1) repositories appear to be consulted for all artifacts, even if no appropriate proxy connector has been defined.
-----------------------------------------------------------------------------------------------------------------------------------------
Key: MRM-1035
URL: http://jira.codehaus.org/browse/MRM-1035
Project: Archiva
Issue Type: Bug
Components: remote proxy
Affects Versions: 1.1.3
Environment: Linux, Standard archiva installation.
Reporter: Tom DeWire
Priority: Minor
- We have a number of remote repositories configured, including one legacy (maven 1) repository (https://maven-repository.dev.java.net/nonav/repository).
- We have two managed repositories configured, one for external artifacts, one for internally produced artifacts.
- We have a proxy connector that links each of the external repositories into the managed repository for external artifacts. The proxy connector explicitly excludes our group prefix (e.g. org/foo/**). We have configured the proxy connectors to cache-errors.
While tailing the logs, I have noticed that *every* request seems to be proxied through to the legacy maven 1 repository, even requests for artifacts that come from our managed repository for internally produced artifacts (note that there is *no* proxy defined for this repository). These fail (of course), and eventually show up in the logs as such:
2008-12-10 22:14:11,043 [btpool0-52] INFO org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not attempted on https://maven-repository.dev.java.net/nonav/repository/com.ea.nucleus/poms/profanity-1.1.2.pom : NO to fetch, check-failures detected previous failure on url: https://maven-repository.dev.java.net/nonav/repository/org.foo/poms/profanity-1.1.2.pom
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-1035) Remote, legacy (Maven 1) repositories
appear to be consulted for all artifacts, even if no appropriate proxy
connector has been defined.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-1035.
-----------------------------
Resolution: Duplicate
Fix Version/s: (was: 1.4)
Assignee: Brett Porter
> Remote, legacy (Maven 1) repositories appear to be consulted for all artifacts, even if no appropriate proxy connector has been defined.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1035
> URL: http://jira.codehaus.org/browse/MRM-1035
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.3
> Environment: Linux, Standard archiva installation.
> Reporter: Tom DeWire
> Assignee: Brett Porter
> Priority: Minor
>
> - We have a number of remote repositories configured, including one legacy (maven 1) repository (https://maven-repository.dev.java.net/nonav/repository).
> - We have two managed repositories configured, one for external artifacts, one for internally produced artifacts.
> - We have a proxy connector that links each of the external repositories into the managed repository for external artifacts. The proxy connector explicitly excludes our group prefix (e.g. org/foo/**). We have configured the proxy connectors to cache-errors.
> While tailing the logs, I have noticed that *every* request seems to be proxied through to the legacy maven 1 repository, even requests for artifacts that come from our managed repository for internally produced artifacts (note that there is *no* proxy defined for this repository). These fail (of course), and eventually show up in the logs as such:
> 2008-12-10 22:14:11,043 [btpool0-52] INFO org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not attempted on https://maven-repository.dev.java.net/nonav/repository/com.ea.nucleus/poms/profanity-1.1.2.pom : NO to fetch, check-failures detected previous failure on url: https://maven-repository.dev.java.net/nonav/repository/org.foo/poms/profanity-1.1.2.pom
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1035) Remote, legacy (Maven 1) repositories
appear to be consulted for all artifacts, even if no appropriate proxy
connector has been defined.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1035:
------------------------------
Fix Version/s: (was: Backlog)
1.4
for testing
> Remote, legacy (Maven 1) repositories appear to be consulted for all artifacts, even if no appropriate proxy connector has been defined.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1035
> URL: http://jira.codehaus.org/browse/MRM-1035
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.3
> Environment: Linux, Standard archiva installation.
> Reporter: Tom DeWire
> Priority: Minor
> Fix For: 1.4
>
>
> - We have a number of remote repositories configured, including one legacy (maven 1) repository (https://maven-repository.dev.java.net/nonav/repository).
> - We have two managed repositories configured, one for external artifacts, one for internally produced artifacts.
> - We have a proxy connector that links each of the external repositories into the managed repository for external artifacts. The proxy connector explicitly excludes our group prefix (e.g. org/foo/**). We have configured the proxy connectors to cache-errors.
> While tailing the logs, I have noticed that *every* request seems to be proxied through to the legacy maven 1 repository, even requests for artifacts that come from our managed repository for internally produced artifacts (note that there is *no* proxy defined for this repository). These fail (of course), and eventually show up in the logs as such:
> 2008-12-10 22:14:11,043 [btpool0-52] INFO org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not attempted on https://maven-repository.dev.java.net/nonav/repository/com.ea.nucleus/poms/profanity-1.1.2.pom : NO to fetch, check-failures detected previous failure on url: https://maven-repository.dev.java.net/nonav/repository/org.foo/poms/profanity-1.1.2.pom
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1035) Remote, legacy (Maven 1) repositories
appear to be consulted for all artifacts, even if no appropriate proxy
connector has been defined.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1035:
------------------------------
Fix Version/s: 1.x
> Remote, legacy (Maven 1) repositories appear to be consulted for all artifacts, even if no appropriate proxy connector has been defined.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1035
> URL: http://jira.codehaus.org/browse/MRM-1035
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.3
> Environment: Linux, Standard archiva installation.
> Reporter: Tom DeWire
> Priority: Minor
> Fix For: 1.x
>
>
> - We have a number of remote repositories configured, including one legacy (maven 1) repository (https://maven-repository.dev.java.net/nonav/repository).
> - We have two managed repositories configured, one for external artifacts, one for internally produced artifacts.
> - We have a proxy connector that links each of the external repositories into the managed repository for external artifacts. The proxy connector explicitly excludes our group prefix (e.g. org/foo/**). We have configured the proxy connectors to cache-errors.
> While tailing the logs, I have noticed that *every* request seems to be proxied through to the legacy maven 1 repository, even requests for artifacts that come from our managed repository for internally produced artifacts (note that there is *no* proxy defined for this repository). These fail (of course), and eventually show up in the logs as such:
> 2008-12-10 22:14:11,043 [btpool0-52] INFO org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not attempted on https://maven-repository.dev.java.net/nonav/repository/com.ea.nucleus/poms/profanity-1.1.2.pom : NO to fetch, check-failures detected previous failure on url: https://maven-repository.dev.java.net/nonav/repository/org.foo/poms/profanity-1.1.2.pom
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira