[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-ant-dev] AntSecurityManager
|
Title: Message
Darin,
thanks
for the fast answer.
Actually all my builds launch a separate VM since the <java>
task fork argument is set to true.
The
exception occurs although Tomcat, launched by the first build, has already
been shutdown by the second build. I can see that the Tomcat VM has terminated
with Windows task manager. Then I close the Eclipse self-hosting instance, and I
get the exception.
Now do
you see a workaround to this problem, and is this a bug
?
Julien
The AntSecurityManager exists so that it is not
possible for an Ant build within Eclipse to cause the Eclipse VM to exit since
currently all Ant builds occur within the same VM that launched
Eclipse.
Can you log a bug report
against platform ant...it looks like we are effectively not allowing any other
Java process to exit / be shutdown (in some cases) as well...but I will have
to investigate. Build files that reproduce the problem (simpler the better :-)
) would be greatly appreciated.
My
current workaround for you: have your plugin, on Eclipse shutdown, execute the
stop Tomcat build file.
Thanks
Darins
|
| "Julien Ruaux"
<jruaux@xxxxxxxx>
Sent
by: platform-ant-dev-admin@xxxxxxxxxxx
01/22/03 10:01 AM
Please respond to platform-ant-dev
|
To:
<platform-ant-dev@xxxxxxxxxxx>
cc:
Subject: [platform-ant-dev]
AntSecurityManager
|
Hi,
I am using AntRunner in a
plugin I am writing.
The Ant scripts it's running
are mainly :
- a script to start Tomcat 4.0
with <java jvm='javaw' classname="org.apache.catalina.startup.Bootstrap"...
/>
- another one to stop Tomcat, which
puts an end to the previous script's java task.
An
exception occurs when closing down Eclipse or the Eclipse instance in
self-hosting.
This is thrown by the
checkExit(int) method of AntSecurityManager.
Thanks
for your help,
Julein
