Thanks for the clarification, I assumed that because
${user.home}/.m2/repository
is the default local repo that it searched in .m2. Now I understand that
regardless of where your local repository exists, it will look in ${
user.home}/.m2
Thanks,
Evan
On 8/13/07, Shane Isbell <[EMAIL PROTECTED]> wrote:
>
> I checked the current code and could not find what could be causing it.
> Back
> in early June, there were a number of changes to fix the paths and finding
> the local repository. If you look in the registry-config.xml, you will see
> that NMaven uses ${user.home}/.m2/nmaven-settings.xml to find the
> nmaven-settings.xml file. The latest versions of the SolutionGeneratorMojo
> (both Java and .NET match up with generating it in the same location). It
> should not be using the localRepository. If you change the local
> repository,
> then it will still look in the .m2 directory (at least with the latest
> code).
>
> On 8/13/07, Evan Worley <[EMAIL PROTECTED]> wrote:
> > I think this might be more than just the settings file, I am having
> problems
> > resolving plugins in NMaven when I change my localRepository.
> >
> > Also for reference, I am using NMaven as it was roughly 1 to 1.5 months
> > ago. This might have been fixed.
> >
> > On 8/13/07, Evan Worley <[EMAIL PROTECTED]> wrote:
> > >
> > > Does anyone know where NMaven attemps to find nmaven-settings.xml? I
> > > changed my local m2 repo from the default, and it NMaven can't find
> the
> > > nmaven-settings.xml. I dropped the settings back into the default
> > > location and everything was fine.
> > >
> > > Any ideas?
> > > Evan
> > >
> >
>
