Henning Sudbrock wrote:

[email protected] schrieb am 28.10.05 03:16:12:

Ross Gardler wrote:

Henning Sudbrock wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I just tried to get the Forrest Eclipse Plugin running and got into some
trouble. While solving it I realized that when seeding a new Forrest
Project with the plugin, the plugin calls the forrest.bat batch file in
$FORREST_HOME$\bin through a Java-Process-Object, creating some strange
errors, due to the following problem:

Running forrest.bat under Windows in C:\ (i.e. in the root dir) will
fail (at least on my computer), but running forrest.bat in some
subdirectory like C:\TEST causes no problem at all.

Why would you be running forrest.bat in the root?


To resolve that particular problem with the Eclipse plugin, and besides
that to get rid of OS dependency, I would suggest to run ant from
Eclipse directly, not via the forrest.bat batch file (resp. the forrest
Shell Script under Linux). I think that one can use Eclipse's Ant-Plugin
to do that.

If there are no objections and if you'd like to get some assistance with
the Forrest Eclipse Plugin, I could try my best, starting with this
problem :)

When I wrote the original Eclipse plugin I did it this way because Forrest was using a newer version of Ant than was shipped in Eclipse. If this is no longer the case then I agree with your proposal.

Forrest uses its own packaged version of Ant so
that we have a known version and so that our users
don't need to install it. Our version needs to be updated.

If people don't use Forrest's Ant, then they need to
be aware of the issues mentioned at:
http://forrest.apache.org/docs_0_80/howto/howto-buildPlugin.html#ant
and maybe other issues too.


One could just use Forrest's ant jar packages from within Eclipse, that seems 
better than the batch file / shell script.

+1

Ross