Consider how value interpolation usually works; the periods indicate a path of 
dereferencing to get a final value. In your case, the period is part of the 
value key, not a path separator. 

Chas

> On Oct 16, 2017, at 5:22 PM, Alex O'Ree <[email protected]> wrote:
> 
> I have some pom defined properties that I'm trying to inject into a maven
> site markdown file. The file is named "test.md.vm" and it's referenced in
> the site descriptor.
> 
> <properties>
>>        <testProject.property>This property is used to test PDF .vm
>> project injection. If you can read this in the PDF output, it's
>> working.</testProject.property>
>>        <testProjectProperty>This property is used to test PDF .vm project
>> injection. If you can read this in the PDF output, it's
>> working.</testProjectProperty>
>>    </properties>
> 
> 
> And in the test markdown file has this
> 
> ### User defined properties in the parent pom
>> testProject.property = ${testProject.property}
>> testProjectProperty = ${testProjectProperty}
> 
> 
> I've noticed that pom defined properties containing a period do not resolve
> for some reason. Properties without the dot work just fine.
> 
> 
> Output:
> 
> testProject.property = ${testProject.property}
>> testProjectProperty = This property is used to test PDF .vm project
>> injection. If you can read this in the PDF output, it’s working.
> 
> 
> 
> Am I missing something or this is a plexus configuration injection related
> thing? This also affects the pdf plugin too


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to