Re: relativePath in m3 release notes

Thanks for the small rewrite done, Benjamin. Cheers 2010/9/16 Jeff MAURY > I agree with Baptiste that the explanation is ambiguous. I understand the > same thing. > > Regards > Jeff MAURY > > On Thu, Sep 16, 2010 at 11:30 AM, Benjamin Bentmann < > benjamin.bentm...@udo.edu> wrote: > > > Baptist

Re: relativePath in m3 release notes

I agree with Baptiste that the explanation is ambiguous. I understand the same thing. Regards Jeff MAURY On Thu, Sep 16, 2010 at 11:30 AM, Benjamin Bentmann < benjamin.bentm...@udo.edu> wrote: > Baptiste MATHUS wrote: > > Does it mean that must now be put *even if* the parent pom >> is >> in t

Re: relativePath in m3 release notes

Baptiste MATHUS wrote: Does it mean that must now be put *even if* the parent pom is in the default path? No, it means the effective value for should be correct, whether that value is given by the user or using the implicit default. Benjamin -

relativePath in m3 release notes

Hi all, Just read the link provided in the previous mail about m3-rc1. About this parent pom resolution, I was aware Maven3 would now not resolve in the project if parent project is not found in the default relative path : ../pom.xml. But the comment here https://cwiki.apache.org/confluence/displ