An example is that the Maven site build did not pick up the contents of the index.apt.
My colleagues may have other examples. Regards Nathan ------ Nathan Sowatskey ([email protected]) - Technical Leader, NMTG, XMP Architecture - +34-638-083-675 -----Original Message----- From: Matt Brown [mailto:[email protected]] Sent: Saturday, June 06, 2009 02:33 PM Central Europe Standard Time To: Maven Users List Subject: RE: Just shoot me now and get it over with Can you provide some details on why you need to use an external install with m2eclipse and not the embedded one? ________________________________________ From: Nathan Sowatskey (nsowatsk) [[email protected]] Sent: Saturday, June 06, 2009 6:18 AM To: Maven Users List; Maven Users List Subject: Re: Just shoot me now and get it over with The m2eclipse plugin works well. But you need to configure it to use an external Maven install *not* the embedded one. Regards Nathan ------ Nathan Sowatskey ([email protected]) - Technical Leader, NMTG, XMP Architecture - +34-638-083-675 -----Original Message----- From: Sebastian Hoß [mailto:[email protected]] Sent: Saturday, June 06, 2009 11:51 AM Central Europe Standard Time To: Maven Users List Subject: Re: Just shoot me now and get it over with Steve Cohen wrote: > I am working in a sort of bastardized Eclipse-maven world for months now. > I have had for months a M2_REPO variable in Eclipse pointing to a local > Maven repository. I know this is not the approved Maven way, but it has > worked for me for months without difficulty. As i'm doing the same here ever since - what is the approved Maven way? --------------------------------------------------------------------- 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]
