bugger...

i'm slightly reluctant to rename all my properties. It would also break the convention that maven currently uses as it's properties also use periods. That's really what i find surprising, if it can work for maven it must be possible for pom properties too?

Cam

Sean Hennessy wrote:
Yes.  I've seen this behavior in ant build.xml constructs as well so am
reluctant to point the finger at Maven.
My guess is somewhere in the works  there is confusion as to whether one
is referring to a package.class or property.name even though the
definitions originate in a .properties file!
I've learned to use property_name convention.

Regards,
Sean

-----Original Message-----
From: Cam [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 7:35 AM
To: users@maven.apache.org
Subject: Filtering Site Documents With Periods in Property Names -
Suspect Bug


Hi ml,

I've been trying to get property filtering to work over the site documents as specified in http://maven.apache.org/plugins/maven-site-plugin/usage.html by appending the '.vm' extension to the appropriate files. The problem is that the property filtering doesn't seem to work when the property names

contain periods for breaking up the context words, for example:

The works:
${currentVersion}

This doesn't:
${current.version}

For some reason the default maven properties which are always available DO work even if they have periods, for example this is resolved
correctly:

${project.version}

Seems like some strange behavior and it took me a while to nutt it out. Anyone else seen this, is it a valid bug for the component?

Thanks,
Cam


---------------------------------------------------------------------
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to