[
http://jira.codehaus.org/browse/MRM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154548#action_154548
]
bvj edited comment on MRM-1005 at 11/17/08 11:44 PM:
-------------------------------------------------------
The asterisks in the filter expressions got chewed up in the Jira post. Maybe
an administrator can fix the whiltelist patterns in the post.
Here's an attempt to correctly display the filter expressions by tricking Jira
(through self-escaping the asterisks)
Remedy/Work-around
-------------------------------
Added the following entry to the whitelist filter set:
/***/**
SLASH-ASTERISK-ASTERISK-SLASH-ASTERISK
Remember to click "Save Proxy Connector" after defining the extra pattern/filter
The connector whitelist now has the following entries
***/**
/***/**
was (Author: bvj):
The asterisks in the filter expressions got chewed up in the Jira post.
Here's an attempt to correctly display the filter expressions by tricking Jira
(through self-escaping the asterisks)
Remedy/Work-around
-------------------------------
Added the following entry to the whitelist filter set:
/***/**
Remember to click "Save Proxy Connector" after defining the extra pattern/filter
The connector whitelist now has the following entries
***/**
/***/**
> Certain remote Maven2 artifacts require special leading slash in whitelist
> filter
> ----------------------------------------------------------------------------------
>
> Key: MRM-1005
> URL: http://jira.codehaus.org/browse/MRM-1005
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2-M1
> Environment: Server
> ---------
> Linux apollo 2.6.5-7.201-default #1 Thu Aug 25 06:20:45 UTC 2005 i686 i686
> i386 GNU/Linux
> SUSE LINUX Enterprise Server 9 (i586)
> VERSION = 9
> PATCHLEVEL = 2
> JRE 1.6.0_10
> Self contained Archiva bundle (not using other app server or DB)
> Client
> --------
> Maven2 client: 2.0.9
> Java version: 1.5.0_14
> OS: XP x86
> settings.xml (only 1 mirror entry)
> ---------------------------------------------
> <mirror>
> <id>archiva.default</id>
> <url>http://my-server:8080/archiva/repository/internal/</url>
> <mirrorOf>*</mirrorOf>
> </mirror>
>
> Reporter: b v j
>
> Problem
> -------------------
> Unable to initialize/setup m2 repository with archiva as the default mirror
> Debug observation
> -----------------------------
> With log4j debug settings enabled (./apps/archiva/WEB-INF/classes/log4j.xml),
> hints about the problem surfaced. I did not look any further into the code to
> determine the exact cause of the problem.
> Here's the archiva log entry:
> -------------------------------
> 2008-11-17 23:47:30,144 [btpool0-4] DEBUG
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Path
> [/org/apache/maven/plugins/maven-metadata.xml] is not part of defined
> whitelist (skipping transfer from repository [Central Repository]).
> Remedy/Work-around
> -------------------------------
> Added the following to the whitelist filter set:
> /**/*
> Steps to reproduce (DO NOT FOLLOW unless you're willing to lose local &
> archiva m2 data!)
> -------------------------------------------------------------------------------------------------------------
> 1) move/hide client .m2/repository to temporary location
> 2) move/hide server [archiva]/data/repositories/internal/* files and
> subdirectories to temporary locaton
> 3) Rescan "Archiva Managed Internal Repository" - should show zero entries
> 4) "Update Database Now"
> 5) Make sure the "Central Repository" proxy connector whitelist only contains
> the default fiter: **/*
> 6) To initialize local m2, run from client: mvn -X -e -U -up
> archetype:create -DgroupId=com.mycompany.app -DartifactId=my-appp
> The client throws the following:
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
> 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid
> version could be found
> Remedy/Work-around
> -------------------------------
> Added the following entry to the whitelist filter set:
> /**/*
> Remember to click "Save Proxy Connector" after defining the extra
> pattern/filter
> The connector whitelist now has the following entries
> **/*
> /**/*
>
> Rerun step #6 above and the local m2 repo should build properly.
--
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
