This came up not three weeks ago. What most of us do to get around this is to use something else to modify the pom.xml content before running maven.
Personally, I use ant and xmltask. Why is it happening in an 'official' pom? Because almost EVERY user has a problem with this and we're all suffering, so I'm not surprised that someone 'official' ran into it as well. So I can see at least two possibilities: 1 - maven really IS expanding properties in the parent, for some version of maven as used by the derby developers 2 - the "unmodified" pom got published with derby, rather than the one that had been modified before maven was run. Either way, in my opinion it's definitely the single most annoying thing with maven: the "<version>" field is interpreted in different ways for every instance (sometimes it allows variables, sometimes it doesn't: sometimes it allows ranges, sometimes it doesn't, etc.) Dana Lacoste -----Original Message----- From: Albert Kurucz [mailto:[email protected]] Sent: Thursday, September 24, 2009 9:58 AM To: Maven Users List Subject: Re: Pom Parent Version Properties Is property substitution really forbidden in /project/parent/(groupId|artifactId|version)? If yes, how is it possible to see that on this Maven Central project? http://repo2.maven.org/maven2/org/apache/derby/derby/10.5.3.0/derby-10.5.3.0.pom Is property substitution really forbidden in /project/(groupId|artifactId|version)? If yes, how is it possible to see that on this Maven Central project? http://repo2.maven.org/maven2/org/apache/derby/derby-project/10.5.3.0/derby-project-10.5.3.0.pom Project's POM files may not getting verified for this criteria by the maintainer of Maven Central? Too bad!
