> Brett,
> Thank you for your answer.
>
> I use beta-10.
Can you try RC1, and remove the use of FileUtil? Pom.build.sourceDirectory
should be absolute already, and you can use the maven:makeAbsolutePath tag
to do this otherwise.
> >Can you confirm that calling <ant /> changes ${basedir}
> itself? If so,
> >file
> a bug in JIRA - my guess is if this is happening, that they
> both use a system property and ant scrogs maven's value.
>
> that's the point, ${basedir} is not changed, but the CWD
> (current working
> dir) of jvm is changed, so that when
> in org.apache.velocity.texen.util.FileUtil creates new file
> with relative
> path:
> new File(relativePath);, the file is created not in the
> ${basedir}, but in the dir from where the ant was invoked.
I don't see how the JVM CWD can be changed, unless user.dir is being
modified. But this only affects things that use user.dir, not the actual CWD
which is a real nuisance. This sounds as if it is a problem in ant though
and beyond what Maven can fix. Happy to be told otherwise if I am wrong
here.
Can you output ${systemScope.getVariable('user.dir')} before and after to
confirm it changes?
Cheers,
Brett
