Hi David,
Thanks for responding.
Looks like "escaping" works only in filtering resources, not in the
pom.xml.
One workaround is to create the manifest file in src/main/resources and
use filtering to filter the entries.
Other alternatives?
Thanks,
Jane
David C. Hicks wrote:
Hi Jane,
I just happened to be looking for other information about "escaping"
when I saw your question. Looks like you can use:
\${foobar}
To cause the literal to be used. Here's a link to the page where I found
this: http://maven.apache.org/shared/maven-filtering/
Dave
Jane Young wrote:
Hi Maven Gurus,
Is there a way to treat the literal value of ${foobar} instead of a
property?
For example I want to be able to put an entry in the manifest using
the Maven jar plugin. The entry contains the value ${installRoot} but
since there is no property associated with this, Maven converts it to
"null". In other words, is there a way that I can escape the
expression ${..}?
Thanks in advance!
Jane
---------------------------------------------------------------------
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]
