It works well, pom.name deprecation is reported as warning too; I believe it didn't initially because of parent POM resolution<http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolution>issue project had.
Regards, Stevo. On Sat, Dec 19, 2009 at 12:37 PM, Anders Hammar <[email protected]> wrote: > Stevo, I think it would be great if you could file a jira for the > pom.nameproperty to be deprecated in Maven 3.0! > > /Anders > > On Sat, Dec 19, 2009 at 05:26, Brian Fox <[email protected]> wrote: > > > Yes, a long time ago. > > > > On Fri, Dec 18, 2009 at 5:39 PM, Paul Benedict <[email protected]> > > wrote: > > > Stevo, I thought all pom.* properties were gone. Weren't they replaced > > > by project.* ? > > > > > > On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić <[email protected]> > wrote: > > >> Hello Maven users, > > >> > > >> When building project with Maven 3.0-alpha-5, warnings appear that > > >> "pom.version" and "pom.artifactId" properties have been deprecated in > > favor > > >> of their project.* variants. Is it same with pom.name property? I'm > > asking > > >> this because pom.name is not being reported as deprecated, but I > expect > > it > > >> to be for consistency reason. Wish this deprecated stuff was listed in > > Maven > > >> 3 compatibility > > >> notes<http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html > > > > >> . > > >> > > >> Regards, > > >> Stevo. > > >> > > > > > > --------------------------------------------------------------------- > > > 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] > > > > >
