I'm just guessing here, but since only string properties are passed you need
to define a string property which is based on the non-string property.
Perhaps you could define:
outDir=${project.build.outputDirectory}
Perhaps you could define this in a profile, or in project.properties or
dan tran wrote:
${basedir}/target could be the work around
-D
I did not try this, but by replacing ${project.build.outputDirectory} with
${basedir}/target we end up shifting the problem of evaluating
${project.build.outputDirectory} with one of evaluating ${basedir} rt?
Also, using File
I think you got stucked with this, just like me.
File a jira againt surefire plugin to support Map as additional
configuration
( beside Properties) , that will solve all the problems.
-D
On 11/13/06, Binil Thomas [EMAIL PROTECTED] wrote:
dan tran wrote:
${basedir}/target could be the
Hi all,
The Surefire plugin documentation
(http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html)
mentions:
[snip]
Take note that String valued properties can only be passed as system
properties. Any attempt to pass any other maven variable type (i.e. List or
a
${basedir}/target could be the work around
-D
On 11/9/06, Binil Thomas [EMAIL PROTECTED] wrote:
Hi all,
The Surefire plugin documentation
(
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
)
mentions:
[snip]
Take note that String valued properties can
