That's mine mistake, will fix it ASAP. It should use "jbosstools.test.jboss.home.4.2" environment variable, but something went wrong.

Max Rydahl Andersen wrote: > Hi, > > Anyone know why our unittests leaves the workspace with about 50 "JBoss Application Server 4.2" servers and runtimes defined ? > And even more funny it creates it with C:\java\jboss-4.2.2.GA/server/default/deploy which makes zero sense since: > > 1) I don't have any dir like that > 2) I'm on Linux > > /max > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >

I went trough test results on WinXP and several of them failed because of Runtime was missing. So I tried to fix it quick and not so good :(

Max Rydahl Andersen wrote: > On Mon, 04 Feb 2008 16:36:49 +0100, Denis Golovin <dgolovin(a)exadel.com&gt; wrote: > > >> That's mine mistake, will fix it ASAP. It should use >> "jbosstools.test.jboss.home.4.2" environment variable, but something >> went wrong. >> > > yeah I saw that initial commit in VPETest, right ? Why does the vpetests need that runtime anyway ? > > /max > > >> Max Rydahl Andersen wrote: >> >>> Hi, >>> >>> Anyone know why our unittests leaves the workspace with about 50 "JBoss Application Server 4.2" servers and runtimes defined ? >>> And even more funny it creates it with C:\java\jboss-4.2.2.GA/server/default/deploy which makes zero sense since: >>> >>> 1) I don't have any dir like that >>> 2) I'm on Linux >>> >>> /max >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >> > > > >