Thanks for the feedback, Brian. I was actually just coming to that
realization minutes ago. I guess I was being a bit on the blonde side
before. It finally dawned on me that there are some definite advantages
to setting the mirror up outside the scope of the project.
Dave
Brian E. Fox wrote:
The only way to configure a mirror is with the settings.xml. But you can
rest assured that once you get all the developers to update their
settings, you won't need to have them do it again since you'll be able
to add repositories directly to Nexus and they won't have to do anything
on their side.
-----Original Message-----
From: David C. Hicks [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 02, 2008 5:45 PM
To: Maven Users
Subject: Nexus and my project pom.xml.
Hi folks,
I'm setting up Nexus. No issues there. That's all been very easy and
straightforward. However, I have learned tonight that to make good use
of it, I really need to configure my Maven installation to think of it
as a mirror. This involves editing the ~/.m2/settings.xml file. That's
all well and good, but isn't there a way to get a project pom.xml to do
the same thing? I can already hear the grumbling of developers when I
tell them that they all have to make a change to their settings.xml. It
would be much easier if I can just configure the project.
Am I just out of luck on this point?
Thanks,
Dave
---------------------------------------------------------------------
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]
