Ok....in lieu of not getting this fix, is there a way to accomplish
mirroring and username/password storing without using settings.xml?
Brad
Kathryn Huxtable wrote:
The problem isn't with the plugin, but with the embedder, which the plugin
uses. If the embedder would get fixed, then we'd have support for
settings.xml, or such is my understanding.
--
Kathryn Huxtable
Middleware Architect
Core Middleware
Information Technology, a division of Information Services
The University of Kansas
On 3/5/06 4:19 PM, "Barrie Treloar" <[EMAIL PROTECTED]> wrote:
On 3/6/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
I have run into a problem -- at least I think its a problem, in using
maven2, the eclipse plugin, and maven-proxy. I have maven-proxy
configured and proxying external repositories (ibiblio and codehaus) for
dependencies, and I am bypassing local checking of these external
repositories by configuring my proxy as a mirror in settings.xml. It
works great with a command-line maven client.
Enter the eclipse plugin. The plugin does not support settings.xml, so
all settings presently have to exist in the pom.xml. This has created
the following problems:
This is a problem with the eclipse plugin and not Maven.
I believe the eclipse plugin people are working on supporting settings.xml
But having search the JIRA for the issue I can't find any.
Getting the eclipse plugin fixed would be the correct answer to this problem.
(or just use the command line version)
---------------------------------------------------------------------
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]
