Have you tried to set an escaped value for your variable in case you don't
have a concrete value for it?
Something along the lines of: <foo.context.root>\${foo.context.root
}</foo.context.root>
Might just work..
Cheers
Jo
On 5/29/07, ertnutler <[EMAIL PROTECTED]> wrote:
i'm using the maven-ear-plugin to generate my application.xml. the
problem i
have is that i would like to use a profile property as the value for the
webModule/contextRoot element. the catch is that sometimes i have a value
for this context root, sometimes i don't. for example, when we build to
production we don't know the value of the context root, so i want to pass
through the token unresolved in the generated application.xml file for
later
expansion by a secondary process at the client site. like this:
<modules>
<webModule>
<groupId>foo.bar.baz</groupId>
<artifactId>foo-web</artifactId>
<contextRoot>${foo.context.root}</contextRoot>
</webModule>
</modules>
however, when the WebModule writes out its portion of the application.xml
file, its context root is always null (instead of ${foo.context.root}),
which results in the artifactId of the web artifact being used for the
context root.
is there a workaround other than using a separate application.xml file?
does anyone know why this value comes through as null instead of as
unexpanded -- ${foo.context.root} -- like when used with the resources
plugin?
just for grins, i ran mvn:help-effectivePom with a profile that doesn't
define a value for foo.context.root and the effective pom showed the
literal
un-interpolated value. this is what i would expect to get passed through
to
the ear plugin.
--
View this message in context:
http://www.nabble.com/-m2--ear-plugin%3A-web-module-context-root-problem-tf3834579s177.html#a10856083
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
