DO NOT REPLY [Bug 25856] - GCJ version of Javac task wrongly checks for destdir errors

2004-01-30 Thread bugzilla
/show_bug.cgi?id=25856 GCJ version of Javac task wrongly checks for destdir errors [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 26559] New: - New 'tempdir' javac attribute is ignored by 1.6.0 and 1.6.1

2004-01-30 Thread bugzilla
/show_bug.cgi?id=26559 New 'tempdir' javac attribute is ignored by 1.6.0 and 1.6.1 Summary: New 'tempdir' javac attribute is ignored by 1.6.0 and 1.6.1 Product: Ant Version: 1.6.0 Platform: All OS/Version: All Status: NEW

DO NOT REPLY [Bug 26559] - New 'tempdir' javac attribute is ignored by 1.6.0 and 1.6.1

2004-01-30 Thread bugzilla
/show_bug.cgi?id=26559 New 'tempdir' javac attribute is ignored by 1.6.0 and 1.6.1 --- Additional Comments From [EMAIL PROTECTED] 2004-01-30 22:52 --- Created an attachment (id=10166) Javac task patch to enable tempdir attribute

Re: What about a per directory javac compiler

2004-01-28 Thread Ernst de Haan
are in different subdirectories but in same package. The particular javac task is to be used to compile the generated jsp files by a modified version of jspc task which puts all classes in org.apache.jsp package. This is a bug with Tomcat 4.1 implementation if no servlet mappings are used.(It seems

RE: What about a per directory javac compiler

2004-01-28 Thread Dominique Devienne
From: Ernst de Haan [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 2:30 AM To: Ant Developers List; Antony Paul Subject: Re: What about a per directory javac compiler Wouldn't it be a solution to copy all the files that should be in one package to a single directory (e.g

DO NOT REPLY [Bug 25982] New: - empty include task inside javac causes NullPointerException

2004-01-08 Thread bugzilla
/show_bug.cgi?id=25982 empty include task inside javac causes NullPointerException Summary: empty include task inside javac causes NullPointerException Product: Ant Version: unspecified Platform: PC OS/Version: All Status

DO NOT REPLY [Bug 25982] - empty include task inside javac causes NullPointerException

2004-01-08 Thread bugzilla
/show_bug.cgi?id=25982 empty include task inside javac causes NullPointerException [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 25982] - empty include task inside javac causes NullPointerException

2004-01-08 Thread bugzilla
/show_bug.cgi?id=25982 empty include task inside javac causes NullPointerException --- Additional Comments From [EMAIL PROTECTED] 2004-01-08 14:44 --- I'm not sure to silently ignore the include/ is the best approach. Shouldn't the build barf instead, complaining about the incomplete

DO NOT REPLY [Bug 25982] - empty include task inside javac causes NullPointerException

2004-01-08 Thread bugzilla
/show_bug.cgi?id=25982 empty include task inside javac causes NullPointerException --- Additional Comments From [EMAIL PROTECTED] 2004-01-08 16:52 --- I agree with Dominique on this. name is a mandatory attribute of include, hence one should throw a BuildException in such a case

DO NOT REPLY [Bug 25982] - empty include task inside javac causes NullPointerException

2004-01-08 Thread bugzilla
/show_bug.cgi?id=25982 empty include task inside javac causes NullPointerException --- Additional Comments From [EMAIL PROTECTED] 2004-01-08 17:06 --- This is true, but it is a question of finding where in the code this should be tested

DO NOT REPLY [Bug 25982] - empty include task inside javac causes NullPointerException

2004-01-08 Thread bugzilla
/show_bug.cgi?id=25982 empty include task inside javac causes NullPointerException --- Additional Comments From [EMAIL PROTECTED] 2004-01-08 17:14 --- It should be checked in whatever is the equivalent of the execute() of tasks for PatternSets or whatever. Looking at the code you modfied

Re: Default setting of the javac includeAntRuntime attribute?

2004-01-07 Thread Stefan Bodewig
On Mon, 5 Jan 2004, Kenneth Olving [EMAIL PROTECTED] wrote: But, I expect this simply has to do with backwards compatibility. You are correct (that's been my motivation back then). Is this correct, and there is just no way this will change? Ant 1.6.0 and presetdef is your friend. Stefan

Re: Default setting of the javac includeAntRuntime attribute?

2004-01-05 Thread Erik Hatcher
On Jan 4, 2004, at 6:04 PM, Kenneth Olving wrote: The default setting of 'true' for this attribute has always bothered me - from a CM perspective it is a bit of a nightmare when you get things in your cp that you didn't intend to be there. From a CM perspective, why not put Ant under control as

Re: Default setting of the javac includeAntRuntime attribute?

2004-01-05 Thread Steve Loughran
to be there. Perusing the archives a bit, I find a patch proposal from Jay Glanville in late 2000, concerning a revised architecture for the javac task and there he notes his opinion on the subject (default = false). The patch overall seems to later have been committed by Stefan Bodewig

RE: Default setting of the javac includeAntRuntime attribute?

2004-01-05 Thread Jose Alberto Fernandez
From: Kenneth Olving [mailto:[EMAIL PROTECTED] Maybe I'm just hitting on a long and already closed discussion...I apologize if that's the case. The default setting of 'true' for this attribute has always bothered me - from a CM perspective it is a bit of a nightmare when you get

RE: Default setting of the javac includeAntRuntime attribute?

2004-01-05 Thread Kenneth Olving
On a more cheerfully note, take a look at: presetdef/ (in 1.6) With this task you can define your own defaults for whichever task you want to use and even use the same name as the original IIRC. This may be the solution to the battle of the defaults. Aha! Still on 1.4, so it's definitively

RE: Default setting of the javac includeAntRuntime attribute?

2004-01-05 Thread Kenneth Olving
There are lots of things that are inconsistent due to backwards compatibility. No, we dont want to change them. Fair enough, I can relate to that. And as Mr Fernandez points out, there may be a better solution anyway in this particular case. do you want to field every bug report that

RE: Default setting of the javac includeAntRuntime attribute?

2004-01-05 Thread Kenneth Olving
Steve, thank you for a comment in depth. version, but changing a default is the kind of subtle change that doesn't appear to break things, but changes the expected results. People really hate it when we do that. Yes - again, I can definitively relate to that. The bottom reason I desired

RE: Default setting of the javac includeAntRuntime attribute?

2004-01-05 Thread Jose Alberto Fernandez
From: Steve Loughran [mailto:[EMAIL PROTECTED] Like Erik said; put a custom Ant distro in SCM for the team to use. If you give it a different name e.g. 'WANT' and modify the batch/script files to look for WANT_HOME it will coexist with any other ant distros. this lets you lock

Default setting of the javac includeAntRuntime attribute?

2004-01-04 Thread Kenneth Olving
to be there. Perusing the archives a bit, I find a patch proposal from Jay Glanville in late 2000, concerning a revised architecture for the javac task and there he notes his opinion on the subject (default = false). The patch overall seems to later have been committed by Stefan Bodewig, but with the default value

DO NOT REPLY [Bug 25868] New: - JAVAC debug=off attribute is inconsistent among jikes and javac compiler

2004-01-02 Thread bugzilla
/show_bug.cgi?id=25868 JAVAC debug=off attribute is inconsistent among jikes and javac compiler Summary: JAVAC debug=off attribute is inconsistent among jikes and javac compiler Product: Ant Version: 1.6.0 Platform: All OS/Version: All

DO NOT REPLY [Bug 25868] - JAVAC debug=off attribute is inconsistent among jikes and javac compiler

2004-01-02 Thread bugzilla
/show_bug.cgi?id=25868 JAVAC debug=off attribute is inconsistent among jikes and javac compiler --- Additional Comments From [EMAIL PROTECTED] 2004-01-02 19:31 --- Created an attachment (id=9774) Contains a build file and a java file to display the problem

DO NOT REPLY [Bug 25868] - JAVAC debug=off attribute is inconsistent among jikes and javac compiler

2004-01-02 Thread bugzilla
/show_bug.cgi?id=25868 JAVAC debug=off attribute is inconsistent among jikes and javac compiler --- Additional Comments From [EMAIL PROTECTED] 2004-01-02 19:37 --- Created an attachment (id=9775) Show the modification to Jikes.java

DO NOT REPLY [Bug 25856] New: - GCJ version of Javac task wrongly checks for destdir errors

2004-01-01 Thread bugzilla
/show_bug.cgi?id=25856 GCJ version of Javac task wrongly checks for destdir errors Summary: GCJ version of Javac task wrongly checks for destdir errors Product: Ant Version: 1.6.0 Platform: All OS/Version: All Status: NEW

DO NOT REPLY [Bug 24411] - odd presetdef behavior with additive task parameters like javac srcdir

2003-12-18 Thread bugzilla
/show_bug.cgi?id=24411 odd presetdef behavior with additive task parameters like javac srcdir [EMAIL PROTECTED] changed: What|Removed |Added Version|1.6Beta

DO NOT REPLY [Bug 23889] - preservelastmodified for javac task

2003-12-18 Thread bugzilla
/show_bug.cgi?id=23889 preservelastmodified for javac task [EMAIL PROTECTED] changed: What|Removed |Added Version|1.6Beta |1.6.0

DO NOT REPLY [Bug 19224] - The javac task should accept the 'dependcache' and 'dependcacheref' attributes

2003-12-18 Thread bugzilla
/show_bug.cgi?id=19224 The javac task should accept the 'dependcache' and 'dependcacheref' attributes [EMAIL PROTECTED] changed: What|Removed |Added Version|2.0 spec

DO NOT REPLY [Bug 1011] - javac debug='false' does not disable debug info generation

2003-12-13 Thread bugzilla
/show_bug.cgi?id=1011 javac debug='false' does not disable debug info generation [EMAIL PROTECTED] changed: What|Removed |Added Summary|javac debug=false does |javac debug='false

DO NOT REPLY [Bug 24411] - odd presetdef behavior with additive task parameters like javac srcdir

2003-11-06 Thread bugzilla
/show_bug.cgi?id=24411 odd presetdef behavior with additive task parameters like javac srcdir [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 24411] - odd presetdef behavior with additive task parameters like javac srcdir

2003-11-05 Thread bugzilla
/show_bug.cgi?id=24411 odd presetdef behavior with additive task parameters like javac srcdir --- Additional Comments From [EMAIL PROTECTED] 2003-11-05 14:48 --- Created an attachment (id=8945) Patch to modify behaviour of presetdef

DO NOT REPLY [Bug 24411] - odd presetdef behavior with additive task parameters like javac srcdir

2003-11-05 Thread bugzilla
/show_bug.cgi?id=24411 odd presetdef behavior with additive task parameters like javac srcdir --- Additional Comments From [EMAIL PROTECTED] 2003-11-05 14:57 --- I made a patch to preset to correct the odd behaviour It involves changes to a number of core ant classes (UnknownElement

DO NOT REPLY [Bug 24411] New: - odd presetdef behavior with additive task parameters like javac srcdir

2003-11-04 Thread bugzilla
/show_bug.cgi?id=24411 odd presetdef behavior with additive task parameters like javac srcdir Summary: odd presetdef behavior with additive task parameters like javac srcdir Product: Ant Version: 1.6Beta Platform: PC OS/Version: Windows

ant javac task fails with kaffe + build.compiler=extJavac

2003-10-31 Thread Juan Antonio Martinez
Environment: Linux RedHat 9 kaffe-1.1.2 ant-1.5.4 Take a look at this item: target name=compile depends=init description=Compile the java code javac srcdir=${src} destdir=${build} compiler=kjc classpath refid=project.class.path/ /javac /target . When using

Re: ant javac task fails with kaffe + build.compiler=extJavac

2003-10-31 Thread Stefan Bodewig
On Fri, 31 Oct 2003, Juan Antonio Martinez [EMAIL PROTECTED] wrote: [javac] Kjc: invalid option -- : Attached comes output on ant -v -debug Well, wherever the -- comes from, it is not from Ant (as your debug trace shows). What is /opt/usr/java/kaffe-1.1.2/bin/javac? A shell script passing

Re: ant javac task fails with kaffe + build.compiler=extJavac

2003-10-31 Thread Steve Loughran
Juan Antonio Martinez wrote: Environment: Linux RedHat 9 kaffe-1.1.2 ant-1.5.4 Take a look at this item: target name=compile depends=init description=Compile the java code javac srcdir=${src} destdir=${build} compiler=kjc classpath refid=project.class.path/ /javac

DO NOT REPLY [Bug 23889] - preservelastmodified for javac task

2003-10-22 Thread bugzilla
/show_bug.cgi?id=23889 preservelastmodified for javac task [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 23889] New: - preservelastmodified for javac task

2003-10-17 Thread bugzilla
/show_bug.cgi?id=23889 preservelastmodified for javac task Summary: preservelastmodified for javac task Product: Ant Version: 1.6Beta Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other

DO NOT REPLY [Bug 17512] - Quitting javac task with CTRL-C can leave temporary files

2003-10-14 Thread bugzilla
/show_bug.cgi?id=17512 Quitting javac task with CTRL-C can leave temporary files [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED

DO NOT REPLY [Bug 23508] - JAVAC ignores excludes

2003-09-30 Thread bugzilla
/show_bug.cgi?id=23508 JAVAC ignores excludes [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 23401] New: - javac fails with fork=true and spaces in the source directory name

2003-09-25 Thread bugzilla
/show_bug.cgi?id=23401 javac fails with fork=true and spaces in the source directory name Summary: javac fails with fork=true and spaces in the source directory name Product: Ant Version: 1.5.3 Platform: PC URL: http

DO NOT REPLY [Bug 23401] - javac fails with fork=true and spaces in the source directory name

2003-09-25 Thread bugzilla
/show_bug.cgi?id=23401 javac fails with fork=true and spaces in the source directory name [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 3198] - The javac task doesn't work properly with multi-element sourceparh

2003-09-25 Thread bugzilla
/show_bug.cgi?id=3198 The javac task doesn't work properly with multi-element sourceparh [EMAIL PROTECTED] changed: What|Removed |Added Severity|Major

DO NOT REPLY [Bug 20202] - javac deprecation tag doesn't show deprecation's

2003-09-12 Thread bugzilla
/show_bug.cgi?id=20202 javac deprecation tag doesn't show deprecation's [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 20202] - javac deprecation tag doesn't show deprecation's

2003-09-12 Thread bugzilla
/show_bug.cgi?id=20202 javac deprecation tag doesn't show deprecation's --- Additional Comments From [EMAIL PROTECTED] 2003-09-12 09:51 --- Created an attachment (id=8183) Zipped example - To unsubscribe, e-mail: [EMAIL

DO NOT REPLY [Bug 23035] - javac always recompiles when multiple src paths are given

2003-09-10 Thread bugzilla
/show_bug.cgi?id=23035 javac always recompiles when multiple src paths are given --- Additional Comments From [EMAIL PROTECTED] 2003-09-10 16:57 --- this bug is similar to http://issues.apache.org/bugzilla/show_bug.cgi?id=3198

DO NOT REPLY [Bug 23035] - javac always recompiles when multiple src paths are given

2003-09-10 Thread bugzilla
/show_bug.cgi?id=23035 javac always recompiles when multiple src paths are given --- Additional Comments From [EMAIL PROTECTED] 2003-09-10 17:09 --- Yes, packone and packtwo are package names. Say ClassA lives in packone and ClassB in packtwo. ClassB extends ClassA. I want to exlude

DO NOT REPLY [Bug 23035] - javac always recompiles when multiple src paths are given

2003-09-10 Thread bugzilla
/show_bug.cgi?id=23035 javac always recompiles when multiple src paths are given --- Additional Comments From [EMAIL PROTECTED] 2003-09-10 17:45 --- it sounds like you should not use several src paths but rather src path=${srcdir}/ include name=packone/**/ include name=packtwo/**/ except

DO NOT REPLY [Bug 23035] - javac always recompiles when multiple src paths are given

2003-09-10 Thread bugzilla
/show_bug.cgi?id=23035 javac always recompiles when multiple src paths are given --- Additional Comments From [EMAIL PROTECTED] 2003-09-10 18:05 --- You mean like this javac srcdir=${src.dir} destdir=${build.dir} exclude name=packone/** / include name

DO NOT REPLY [Bug 23035] - javac always recompiles when multiple src paths are given

2003-09-10 Thread bugzilla
/show_bug.cgi?id=23035 javac always recompiles when multiple src paths are given [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 23035] - javac always recompiles when multiple src paths are given

2003-09-10 Thread bugzilla
/show_bug.cgi?id=23035 javac always recompiles when multiple src paths are given --- Additional Comments From [EMAIL PROTECTED] 2003-09-10 18:36 --- Search for a recent thread/bug where one can specify sourcepath= exlicitly (to empty) to avoid having Javac find dependent classes

DO NOT REPLY [Bug 23035] New: - javac always recompiles when multiple src paths are given

2003-09-09 Thread bugzilla
/show_bug.cgi?id=23035 javac always recompiles when multiple src paths are given Summary: javac always recompiles when multiple src paths are given Product: Ant Version: 1.5.4 Platform: PC OS/Version: Other Status: NEW

RE: javac-task and mapper

2003-08-26 Thread Ulf Caspers
On Mon, 18 Aug 2003, didge [EMAIL PROTECTED] wrote: How about this? path id=sources dirset dir=src include name=team*/ /dirset /path javac ... src refid=sources

Re: trying to get access to fileset from new task to javac task

2003-08-25 Thread Stefan Bodewig
On Sun, 24 Aug 2003, Dean Hiller [EMAIL PROTECTED] wrote: I am writing a new task that happens to wrap javac and call it a few times. Is there any way to clear the FileSet? javac doesn't use a FileSet at all, or it uses a fresh FileSet for all src and srcdir entries - depends on how you look

Re: trying to get access to fileset from new task to javac task

2003-08-25 Thread Dean Hiller
I am compiling the same src directory every time, but with different patterns. Javac uses the FileSet in MatchingTask. I currently have a hack into MatchingTask adding public void putNewFileSet(FileSet set) { fileset = set; } because I am not sure how to change out the FileSet

RE: trying to get access to fileset from new task to javac task

2003-08-25 Thread didge
Dean, vppjavac (vpp.sourceforge.net, source available) wraps javac too perform file preprocessing on the source path before invoking javac. The intent was that vppjavac be a 'drop-in' replacement for javac. Originally, I'd hope to simply extend Javac, however, because of the protected

trying to get access to fileset from new task to javac task

2003-08-24 Thread Dean Hiller
I am writing a new task that happens to wrap javac and call it a few times. Is there any way to clear the FileSet? or possibly retrieve the FileSet from Javac's superclass(MatchingTask)? The getImplicitFileset() was protected and there doesn't seem to be a clear function on the MatchingTask

RE: javac-task and mapper

2003-08-22 Thread Ulf Caspers
On Mon, 18 Aug 2003, didge [EMAIL PROTECTED] wrote: How about this? path id=sources dirset dir=src include name=team*/ /dirset /path javac ... src refid=sources

RE: javac-task and mapper

2003-08-20 Thread Ulf Caspers
On Mon, 18 Aug 2003, Dominique Devienne [EMAIL PROTECTED] wrote: All you need to do is: javac destdir=build src path=src/team1 / src path=src/team2 / /javac No need for a mapper. Works like a charm ;-) --DD This is true - as long as you know the names and the number of the teams. My

RE: javac-task and mapper

2003-08-20 Thread Dominique Devienne
Have you tried it? I haven't, but somehow I doubt it will work... That's just a guess though. --DD -Original Message- From: didge [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 19, 2003 7:14 PM To: Ant Developers List Subject: RE: javac-task and mapper How about

RE: javac-task and mapper

2003-08-20 Thread didge
=javac.sourcepath pathelement location=${builtTargets.javac.src.dir}/ pathelement path=${builtTargets.extended.javac.sourcepath}/ /path /target target name=compile depends=buildTargets.init javac ... src refid=buildTargets.javac.sourcepath/ /javac /target And here

Re: javac-task and mapper

2003-08-19 Thread Ulf Caspers
On Mon, 18 Aug 2003, Stefan Bodewig [EMAIL PROTECTED] wrote: java or javac? javac! What would the mapper in javac be supposed to do? There is a GlobPatternMapper in the javac-taskdef which is fixed to map *.java-files to corresponding *.class-files. This is the reason why the source directory

RE: javac-task and mapper

2003-08-19 Thread Dominique Devienne
All you need to do is: javac destdir=build src path=src/team1 / src path=src/team2 / /javac No need for a mapper. Works like a charm ;-) --DD -Original Message- From: Ulf Caspers [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 4:35 PM To: [EMAIL PROTECTED] Subject: Re

Re: javac-task and mapper

2003-08-18 Thread Stefan Bodewig
On Sat, 16 Aug 2003, Ulf Caspers [EMAIL PROTECTED] wrote: My question is: Are there any concerns about a mapper element in a java task? java or javac? What would the mapper in javac be supposed to do? Stefan

javac-task and mapper

2003-08-17 Thread Ulf Caspers
Hello, on 2002-02-09 there was a suggestion by Vadim Zaliva to add the mapper element to the javac task. I'm quite new to ant but I searched through the mailinglist archives and could not find a reason for not following his solution. My question is: Are there any concerns about a mapper element

DO NOT REPLY [Bug 22427] - javac ability to disable search for sources not documented

2003-08-15 Thread bugzilla
/show_bug.cgi?id=22427 javac ability to disable search for sources not documented [EMAIL PROTECTED] changed: What|Removed |Added Severity|Enhancement |Normal

DO NOT REPLY [Bug 22427] New: - javac task to compile files independently

2003-08-14 Thread bugzilla
/show_bug.cgi?id=22427 javac task to compile files independently Summary: javac task to compile files independently Product: Ant Version: 1.5.3 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other

DO NOT REPLY [Bug 22427] - javac task to compile files independently

2003-08-14 Thread bugzilla
/show_bug.cgi?id=22427 javac task to compile files independently --- Additional Comments From [EMAIL PROTECTED] 2003-08-14 15:54 --- Whaooo, I *strongly* support this request!!! I never realized one could actually *not* specify the sourcepath. I developped a complex XSL based system

DO NOT REPLY [Bug 22427] - javac task to compile files independently

2003-08-14 Thread bugzilla
/show_bug.cgi?id=22427 javac task to compile files independently [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 5268] - Should allow execution of javac with no sourcepath set

2003-08-14 Thread bugzilla
/show_bug.cgi?id=5268 Should allow execution of javac with no sourcepath set [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED

DO NOT REPLY [Bug 18055] - javac task includes java rt.jar in classpath when using jvc compiler

2003-08-08 Thread bugzilla
/show_bug.cgi?id=18055 javac task includes java rt.jar in classpath when using jvc compiler [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 18055] - javac task includes java rt.jar in classpath when using jvc compiler

2003-08-07 Thread bugzilla
/show_bug.cgi?id=18055 javac task includes java rt.jar in classpath when using jvc compiler [EMAIL PROTECTED] changed: What|Removed |Added Status|CLOSED

DO NOT REPLY [Bug 21868] New: - javac task fails if there are space in the Absolute Path of the srcdir

2003-07-25 Thread bugzilla
/show_bug.cgi?id=21868 javac task fails if there are space in the Absolute Path of the srcdir Summary: javac task fails if there are space in the Absolute Path of the srcdir Product: Ant Version: 1.5.3 Platform: All OS/Version: All

DO NOT REPLY [Bug 21868] - javac task fails if there are space in the Absolute Path of the srcdir

2003-07-25 Thread bugzilla
/show_bug.cgi?id=21868 javac task fails if there are space in the Absolute Path of the srcdir [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 21785] New: - need away to set javac comiler JAVA_HOME outside build script

2003-07-21 Thread bugzilla
/show_bug.cgi?id=21785 need away to set javac comiler JAVA_HOME outside build script Summary: need away to set javac comiler JAVA_HOME outside build script Product: Ant Version: 1.5.3 Platform: Other OS/Version: Other Status

DO NOT REPLY [Bug 21497] New: - javac succeeds when it should fail

2003-07-11 Thread bugzilla
/show_bug.cgi?id=21497 javac succeeds when it should fail Summary: javac succeeds when it should fail Product: Ant Version: 1.5.2 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component

DO NOT REPLY [Bug 21497] - javac succeeds when it should fail

2003-07-11 Thread bugzilla
/show_bug.cgi?id=21497 javac succeeds when it should fail [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 20580] - javac target not working if build.compiler property set to jikes

2003-06-23 Thread bugzilla
/show_bug.cgi?id=20580 javac target not working if build.compiler property set to jikes [EMAIL PROTECTED] changed: What|Removed |Added Status|VERIFIED|CLOSED

DO NOT REPLY [Bug 21011] New: - Javac task's debug behaviour ignores compilerarg

2003-06-23 Thread bugzilla
/show_bug.cgi?id=21011 Javac task's debug behaviour ignores compilerarg Summary: Javac task's debug behaviour ignores compilerarg Product: Ant Version: 1.5.3 Platform: All OS/Version: Other Status: NEW Severity: Normal

FileSet reference in Javac ..

2003-06-20 Thread Harsha Kalidindi
Hi: I looked through the mail archives to see if anyone had the same issue with not being able to reference FileSets in Javac. I saw a query but no responses. fileset id=sources1 ... /fileset javac destdir=.. fileset refid=sources1

Re: FileSet reference in Javac ..

2003-06-20 Thread Conor MacNeill
On Fri, 20 Jun 2003 02:59 am, Harsha Kalidindi wrote: Hi: I looked through the mail archives to see if anyone had the same issue with not being able to reference FileSets in Javac. I saw a query but no responses. fileset id=sources1 ... /fileset

DO NOT REPLY [Bug 18053] - Incorrect javac task documentation

2003-06-17 Thread bugzilla
/show_bug.cgi?id=18053 Incorrect javac task documentation [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Additional Comments

DO NOT REPLY [Bug 20580] - javac target not working if build.compiler property set to jikes

2003-06-10 Thread bugzilla
/show_bug.cgi?id=20580 javac target not working if build.compiler property set to jikes [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 17683] - javac task fails if path for java file contains space and if using external compiler

2003-06-03 Thread bugzilla
/show_bug.cgi?id=17683 javac task fails if path for java file contains space and if using external compiler --- Additional Comments From [EMAIL PROTECTED] 2003-06-03 22:03 --- Anne, I believe I have solved this bug together with the bug 10499. However, I did not put this if ( i==0

DO NOT REPLY [Bug 20408] New: - Allow passing arguments to javac globally

2003-06-02 Thread bugzilla
/show_bug.cgi?id=20408 Allow passing arguments to javac globally Summary: Allow passing arguments to javac globally Product: Ant Version: 1.5.3 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority

DO NOT REPLY [Bug 20408] - Allow passing arguments to javac globally

2003-06-02 Thread bugzilla
/show_bug.cgi?id=20408 Allow passing arguments to javac globally --- Additional Comments From [EMAIL PROTECTED] 2003-06-02 09:06 --- Created an attachment (id=6594) Compiler Adapter

DO NOT REPLY [Bug 20202] - javac deprecation tag doesn't show deprecation's

2003-05-30 Thread bugzilla
/show_bug.cgi?id=20202 javac deprecation tag doesn't show deprecation's --- Additional Comments From [EMAIL PROTECTED] 2003-05-30 08:01 --- ant -verbose should also show you whether -deprecation gets passed to the compiler. Does it? In my experience you'll always get deprecation warnings

DO NOT REPLY [Bug 20202] - javac deprecation tag doesn't show deprecation's

2003-05-27 Thread bugzilla
/show_bug.cgi?id=20202 javac deprecation tag doesn't show deprecation's --- Additional Comments From [EMAIL PROTECTED] 2003-05-27 07:35 --- Are you sure the file that calls the deprecated method gets compiled at all? See ant -verbose for a listing of all files that get compiled.

DO NOT REPLY [Bug 20202] - javac deprecation tag doesn't show deprecation's

2003-05-27 Thread bugzilla
/show_bug.cgi?id=20202 javac deprecation tag doesn't show deprecation's --- Additional Comments From [EMAIL PROTECTED] 2003-05-27 14:37 --- yeah, the files get compiled. and correctly. they just don't show depercation warnings.

DO NOT REPLY [Bug 11143] - Javac should load build.compiler class from a defined classloader

2003-05-14 Thread bugzilla
/show_bug.cgi?id=11143 Javac should load build.compiler class from a defined classloader [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL

DO NOT REPLY [Bug 3198] - The javac task doesn't work properly with multi-element sourceparh

2003-04-26 Thread bugzilla
/show_bug.cgi?id=3198 The javac task doesn't work properly with multi-element sourceparh --- Additional Comments From [EMAIL PROTECTED] 2003-04-26 11:14 --- when compiling multiple elements, why does javac exits saying BUILD FAILED rather than writing the classes of sucessful compilation. Im

DO NOT REPLY [Bug 19285] - Invalid path when using javac with fork=true

2003-04-25 Thread bugzilla
/show_bug.cgi?id=19285 Invalid path when using javac with fork=true --- Additional Comments From [EMAIL PROTECTED] 2003-04-25 06:41 --- Could you give us a complete output (of the javac task, you can snip the rest) from ant -debug please?

DO NOT REPLY [Bug 19285] - Invalid path when using javac with fork=true

2003-04-25 Thread bugzilla
/show_bug.cgi?id=19285 Invalid path when using javac with fork=true --- Additional Comments From [EMAIL PROTECTED] 2003-04-25 09:38 --- Created an attachment (id=6007) ant -debug output for javac

DO NOT REPLY [Bug 19285] - Invalid path when using javac with fork=true

2003-04-24 Thread bugzilla
/show_bug.cgi?id=19285 Invalid path when using javac with fork=true --- Additional Comments From [EMAIL PROTECTED] 2003-04-24 19:35 --- Sounds like a bug... Could you try with a nested src instead of 'srcdir', just in case. Thanks, --DD

DO NOT REPLY [Bug 17512] - Quitting javac task with CTRL-C can leave temporary files

2003-04-15 Thread bugzilla
/show_bug.cgi?id=17512 Quitting javac task with CTRL-C can leave temporary files [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED

DO NOT REPLY [Bug 18950] New: - Enable Javac to update jar file

2003-04-11 Thread bugzilla
/show_bug.cgi?id=18950 Enable Javac to update jar file Summary: Enable Javac to update jar file Product: Ant Version: 1.5.3 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other

DO NOT REPLY [Bug 18950] - Enable Javac to update jar file

2003-04-11 Thread bugzilla
/show_bug.cgi?id=18950 Enable Javac to update jar file --- Additional Comments From [EMAIL PROTECTED] 2003-04-11 13:29 --- If the jar is on the classpath (and it is probably going to end up there, at least for javac), you won't be able to alter its content on Windows - it will be locked

DO NOT REPLY [Bug 18055] - javac task includes java rt.jar in classpath when using jvc compiler

2003-03-20 Thread bugzilla
/show_bug.cgi?id=18055 javac task includes java rt.jar in classpath when using jvc compiler [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 18055] - javac task includes java rt.jar in classpath when using jvc compiler

2003-03-20 Thread bugzilla
/show_bug.cgi?id=18055 javac task includes java rt.jar in classpath when using jvc compiler [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED

DO NOT REPLY [Bug 18055] - javac task includes java rt.jar in classpath when using jvc compiler

2003-03-19 Thread bugzilla
/show_bug.cgi?id=18055 javac task includes java rt.jar in classpath when using jvc compiler --- Additional Comments From [EMAIL PROTECTED] 2003-03-19 10:24 --- The codesnippet actually is for the case where you are running Ant in a VM by Microsoft, not necessarily for running jvc. I'm

DO NOT REPLY [Bug 18055] - javac task includes java rt.jar in classpath when using jvc compiler

2003-03-19 Thread bugzilla
/show_bug.cgi?id=18055 javac task includes java rt.jar in classpath when using jvc compiler --- Additional Comments From [EMAIL PROTECTED] 2003-03-19 22:26 --- From http://ant.apache.org/manual/index.html: Note: The Microsoft JVM/JDK is not adequate on its own, although the MS compiler

<    1   2   3   4   5   6   >