[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ant-dev] New Ant Support available in today's integration build (20020409)
|
When you run using build.compiler=modern you should be getting sun's javac
and not eclipse's compiler. If you can reproduce the problem, please enter
a bug report.
About the Ant console I agree that it can be useful to have a non modal way
of running scripts. Ant runs in the same VM as Eclipse (as opposed to what
the debugger does) so it makes sense to lock Eclipse because in that
context it is just a long-running operation.
Running on a separate VM would lose some Eclipse-specific tasks (e.g.
eclipse.refreshLocal) that rely on instances of Eclipse objects.
I've entered a feature request for that (
http://bugs.eclipse.org/bugs/show_bug.cgi?id=13275 ) but it is uncertain
that we can implement that for the 2.0 release.
Rodrigo
Binyan
<binyan357@xxxxxxxxx> To: platform-ant-dev@xxxxxxxxxxx
Sent by: cc:
platform-ant-dev-admin@ Subject: Re: [platform-ant-dev] New Ant Support available in today's
eclipse.org integration build (20020409)
04/09/2002 09:57 PM
Please respond to
platform-ant-dev
The new support looks great and solves the rmic task
issue. However if I set build.compiler=modern in my
build.xml, am I getting sun's javac compiler or
eclipse's in the current setup? I ask because I have
a build.xml file that works from the command line fine
with build.compiler set to modern or jikes, but fails
with compile errors when run from eclipse with
build.compiler=modern (it does compile from within
eclipse with build.compiler=jikes).
I will try and create a project that can reproduce
this error, but the error messages are as follows:
D:\view\binyan_view\common\servlets\ConnectionManager.java:44:
'.' expected
import Extensions;
^
D:\view\binyan_view\common\servlets\ConnectionManager.java:45:
'.' expected
import XalanExtensions;
^
D:\view\binyan_view\common\servlets\ConnectionManager.java:407:
cannot resolve symbol
symbol : variable Extensions
location: class ConnectionManager
Extensions.setProductContextPath(contextPath_);
^
D:\view\binyan_view\common\servlets\ConnectionManager.java:408:
cannot resolve symbol
symbol : variable XalanExtensions
location: class ConnectionManager
XalanExtensions.setProductContextPath(contextPath_);
^
Note: Some input files use or override a deprecated
API.
Note: Recompile with -deprecation for details.
4 errors
On the UI front the Ant Console should IMHO be used
more like the debug console. By that I mean the
current behavior is to throw up a modal dialog and
lock the UI while an ant build is executing. For me
at least this can lock eclipse for 2+ minutes for a
full build. It would be better to kick of the build
and have the Ant Console have a red "Terminate" square
the same as the debug console to stop the current ant
build process. Users still get the ability to cancel
and the UI remains responsive through out.
Binyan
--- Rodrigo_Peretti@xxxxxxx wrote:
> The new Eclipse Ant support will be available in
> today's (20020409)
> integration build. Please report any bugs to
> http://bugs.eclipse.org/bugs/
> and comments to the platform-ant-dev@xxxxxxxxxxx
> mailing list.
>
> Rodrigo
>
> _______________________________________________
> platform-ant-dev mailing list
> platform-ant-dev@xxxxxxxxxxx
>
http://dev.eclipse.org/mailman/listinfo/platform-ant-dev
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
_______________________________________________
platform-ant-dev mailing list
platform-ant-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ant-dev
