That wasn't supposed to be a Maven property, but a local property. The use of the <local> task above establishes a scoped property that will shadow any preexisting value of the property "parent", but I can choose a different name to avoid this confusion. Thanks for getting involved.
Matt On Tue, Feb 18, 2014 at 7:16 PM, <s...@apache.org> wrote: > Author: sebb > Date: Wed Feb 19 01:16:54 2014 > New Revision: 1569584 > > URL: http://svn.apache.org/r1569584 > Log: > ${parent} is deprecated, use ${project.parent} instead > > Modified: > commons/proper/weaver/trunk/pom.xml > > Modified: commons/proper/weaver/trunk/pom.xml > URL: > http://svn.apache.org/viewvc/commons/proper/weaver/trunk/pom.xml?rev=1569584&r1=1569583&r2=1569584&view=diff > > ============================================================================== > --- commons/proper/weaver/trunk/pom.xml (original) > +++ commons/proper/weaver/trunk/pom.xml Wed Feb 19 01:16:54 2014 > @@ -430,7 +430,7 @@ under the License. > <sequential unless:true="${exists}"> > <local name="parent" /> > <dirname property="parent" file="@{dir}" /> > - <step dir="${parent}" name="@{name}" > addto="@{addto}" ws="@{ws}" /> > + <step dir="${project.parent}" name="@{name}" > addto="@{addto}" ws="@{ws}" /> > </sequential> > </sequential> > </sequential> > > >
