Just thought of a sneaky workaround for the first alpha - can you try:
${project.file.parent} ?
(maybe project.file.parentFile.absolutePath). I don't know if these work
with the current code either - worth a shot.
- Brett
Brett Porter wrote:
>Ideally configuration would be declared as a file, in which case it is
>resolved to the basedir. But that's obviously not possible with generic
>types like properties.
>
>It seems that we need to amalgamate the expression handling the model
>interpolator, and the expression hangling in the plugin expression
>evaluator, and make sure both will substitute "basedir" when found. At
>the moment, only ${project.*} variables are being interpolated.
>
>- Brett
>
>Vincent Massol wrote:
>
>
>
>>Hi,
>>
>>I have modified the surefire plugin to accept system properties.
>>
>>However when I use the new configuration in my project it works if I use
>>http://rafb.net/paste/results/qVjiw978.html works but fails with
>>http://rafb.net/paste/results/LuSmSw40.html (the difference is that in the
>>second URL I use ${basedir}).
>>
>>I've printed the propery value that gets set in the surefire plugin and I
>>can see that ${basedir} is not expanded before it is handed over to the
>>plugin. Is that normal behavior?
>>
>>Note that the reason I wanted to use ${basedir} is because without it my
>>module builds fine but it fails when built by the parent project (because
>>the resources dir is not correctly set).
>>
>>Any idea?
>>
>>Thanks
>>-Vincent
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>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]
