slobokot commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-545595029
Reproduced issue using following build.xml
lipnitsk commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-545576894
This change likely broke the usage of command-line argument files, see
https://bz.apache.org/bugzilla/show_bug.cgi?id
Kruithof wrote:
This still leaves an issue,
If ant is run using java 8 and an external compiler java 11 is used,
the correct compiler version is not determined, this is also the case
in the ant 1.10.6 release.
Do you mean using the "executable" attribute of the javac task to point
to a
this is also the case
> in the ant 1.10.6 release.
Do you mean using the "executable" attribute of the javac task to point
to an external compiler?
-Jaikiran
>
> On 25-08-19 11:44, j...@apache.org wrote:
>> This is an automated email from the ASF dual-hosted git repository
-16
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.3+7)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.3+7, mixed mode)
jkf@zelfbouwasuscm:~/testje$ ~/git-ant/ant/dist/bin/ant
Buildfile: /home/jkf/testje/build.xml
build:
[javac] /home/jkf/testje/build.xml:4: warning: 'includeantruntime
build no longer honours the source, target and
>> release attributes of the javac task for versions of javac that support
>> it. For example when building with Java 11 our "compile" target in
>> build.xml although has the correct attribute values, those values never
>> get
attributes of the javac task for versions of javac that support
it. For example when building with Java 11 our "compile" target in
build.xml although has the correct attribute values, those values never
get passed to the underlying javac call. As a result, the compiled
classes use an incor
Hello Martijn,
I was in the process of running some tests to decide if we are in a
state to do a release of Ant project. While doing so, I ran into an
issue where our project build no longer honours the source, target and
release attributes of the javac task for versions of javac that support
jmkf merged pull request #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98
This is an automated message from the Apache Git Service.
To respond
jmkf commented on issue #98: Use commandline argument file for all options, but
-J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-502364041
I was wondering why the java 11 checks would not apply to java 12 as the
first ones, howerver these are indeed referring
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-502349133
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-502349123
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ant
bodewig commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-502348318
this is OK to test
This is an automated message from
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-501923947
Can one of the admins verify this patch
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-501923948
Can one of the admins verify this patch
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-501923943
Can one of the admins verify this patch
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-501923940
Can one of the admins verify this patch
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-501923945
Can one of the admins verify this patch
asfgit commented on issue #98: Use commandline argument file for all options,
but -J, for case javac…
URL: https://github.com/apache/ant/pull/98#issuecomment-501923944
Can one of the admins verify this patch
slobokot opened a new pull request #98: Use commandline argument file for all
options, but -J, for case javac…
URL: https://github.com/apache/ant/pull/98
Currently only java files are passed using commandline argument file for
javac.
There are times when classpath is longer than 8000
On 2016-07-01, John Argentieri wrote:
> This page has a note which I think may be causing some confusion. Is
> the javac "debug" tag for ant really supposed to be "off"/"true"? or
> is it really supposed to be "on"/"off"? If so, th
Dear Ant Devs,
This page has a note which I think may be causing some confusion. Is the javac
"debug" tag for ant really supposed to be "off"/"true"? or is it really
supposed to be "on"/"off"? If so, the last sentence is incorrect...:
http
Github user tzezula commented on a diff in the pull request:
https://github.com/apache/ant/pull/16#discussion_r58201438
--- Diff: src/tests/junit/org/apache/tools/ant/taskdefs/JavacTest.java ---
@@ -244,4 +248,85 @@ public void testTargetOverridesDefault() {
Github user bodewig commented on a diff in the pull request:
https://github.com/apache/ant/pull/16#discussion_r58160809
--- Diff: src/tests/junit/org/apache/tools/ant/taskdefs/JavacTest.java ---
@@ -244,4 +248,85 @@ public void testTargetOverridesDefault() {
Github user silviu-burcea commented on a diff in the pull request:
https://github.com/apache/ant/pull/16#discussion_r58038934
--- Diff: src/tests/junit/org/apache/tools/ant/taskdefs/JavacTest.java ---
@@ -244,4 +248,85 @@ public void testTargetOverridesDefault() {
Github user bodewig commented on the pull request:
https://github.com/apache/ant/pull/16#issuecomment-200354466
Many thanks for the explanation.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user tzezula commented on the pull request:
https://github.com/apache/ant/pull/16#issuecomment-199305236
Yes. Unfortunately the javac `-modulesourcepath` option for the multi
module compilation is more complex than existing path arguments. It's described
in [JEP 261: Module
Github user bodewig commented on the pull request:
https://github.com/apache/ant/pull/16#issuecomment-199231853
This looks a bit more complex than I would have naively expected, I've
probably been underestimating the impact of modules.
Many thanks!
---
If your project is
Github user asfgit closed the pull request at:
https://github.com/apache/ant/pull/16
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
GitHub user tzezula opened a pull request:
https://github.com/apache/ant/pull/16
The JDK 9 module system support for the Javac Task
Added a support for jigsaw modulepath, upgrademodulepath and
modulesourcepath to Javac task. Both single module and multi module compilation
Hi,
I'm using Ant 1.7.0 with JDK1.6.
While trying to create build I'm using below tag of javac with nowarn attribure
on:
javac fork=yes source=1.6 debuglevel=${debug.level} nowarn=on
encoding=iso-8859-1
But still I m getting javac warning under this target.
Please help
Thanks and Best
In the world of internet and pressure to reuse as much as possible, there is
a need for able to copy only the files which were used to generate the class
files.
In a declarations like this
javac destdir=${build.deploy.classes}
source=${source}
debug=${debug
Hi,
Is there a way to bind the javac tag to compile whith JDKS 1.5 java
version.
thanks
--
View this message in context:
http://www.nabble.com/JDK-version-in-javac-tag-tp23761074p23761074.html
Sent from the Ant - Dev mailing list archive at Nabble.com
javac executable ?
Jan
-Ursprüngliche Nachricht-
Von: peibel [mailto:p.castre...@ibermatica.com]
Gesendet: Donnerstag, 28. Mai 2009 14:51
An: dev@ant.apache.org
Betreff: JDK version in javac tag
Hi,
Is there a way to bind the javac tag to compile whith JDKS 1.5 java
version
peibel p.castre...@ibermatica.com wrote on 05/28/2009 08:50:47 AM:
Is there a way to bind the javac tag to compile whith JDKS 1.5 java
version.
Are you talking about the JLS level (i.e. language features) or the APIs?
thanks,
but, I want to indicate a version that is not and if that does not compile.
I want only to compile the 1.5
my soruce:
target name=compileModelo depends=cleanModelo
javac srcdir=${src.fuentes.modelo.dir}
destdir=${modelo.bin.dir}
taskname=javac1.5 fork=true compiler
Hi
We are creating a CI process for a large java projects with an estimated
15-20-thousand java object. It is crucial for the process that we find and
report all Compile errors at each build, the problem is that we cant figure
this out with ANT's javac task as we cant catch each error without
Jesse Glick wrote:
Jess Holle wrote:
We've seen this before where A depends on B which /internally/ depends
upon C and then suddenly one has to have C around to compile A.
Although this is not forbidden by the JLS (as far as I know), it does
seem undesirable. If you know of particular
Steve Loughran wrote:
Jesse Glick wrote:
Jess Holle wrote:
We've seen this before where A depends on B which /internally/
depends upon C and then suddenly one has to have C around to compile A.
Although this is not forbidden by the JLS (as far as I know), it does
seem undesirable. If you
Hi Stefan!
I followed your advice and set sourcepath to .
Compilation by javac works properly in JDK 5 and 6:
javac -sourcepath -classpath b.jar A.java
Compilation by ant task works properly in JDK 5, but does not work in JDK 6:
project default=compile
target name=compile
javac
On Wed, 5 Nov 2008, Sergey Bondarenko [EMAIL PROTECTED] wrote:
Hi Stefan!
I followed your advice and set sourcepath to .
Compilation by javac works properly in JDK 5 and 6:
javac -sourcepath -classpath b.jar A.java
Compilation by ant task works properly in JDK 5, but does not work
Jess Holle wrote:
We've seen this before where A depends on B which /internally/ depends upon C
and then suddenly one has to have C around to compile A.
Although this is not forbidden by the JLS (as far as I know), it does seem undesirable. If you know of particular examples which can be
Well, I tried javac:
javac -sourcepath A.java -classpath b.jar A.java
It works properly in both JDK 5 and 6.
But Ant's javac task with includes and excludes does not work with JDK
6.
So I am not sure that problem is in javac compiler. It looks like there is a
problem in javac Ant task.
Could
On Tue, 4 Nov 2008, Sergey Bondarenko [EMAIL PROTECTED] wrote:
Regarding compilation issue, it looks like Ant javac task does not
handle includes and excludes attributes correctly when it is
used with JDK 6. But it works properly with JDK 5.
Uhm, no.
includes/excludes controls which source
On Tue, 4 Nov 2008, Sergey Bondarenko [EMAIL PROTECTED] wrote:
javac -sourcepath A.java -classpath b.jar A.java
It works properly in both JDK 5 and 6.
This is not what Ant does (and why I pointed you at sourcepath= in
order to get something like that.
But Ant's javac task with includes
On Sat, 1 Nov 2008, Sergey Bondarenko [EMAIL PROTECTED] wrote:
Any new regarding this issue?
IMHO you are simply not sending your question to the set of people
that could answer them. Based on your description the javac compilers
behave differently, but Ant doesn't. I don't see how the Ant
on the classpath, beyond the
obvious fact that if the content of such a dependency could possibly affect the generated bytecode then it must be present. I seem to recall that Jikes used to behave
differently than javac, and I am not that surprised if JDK 5 javac behaves differently from JDK 6 javac
Any new regarding this issue?
Thanks!
Sergey.
2008/10/30 Sergey Bondarenko [EMAIL PROTECTED]
Hi dear Ant developers!
I think I found a bug in Ant javac task, (or maybe in Java compiler).
I need you help to check if it is true.
Javac task behaves differently in Java 6 and Java 5
Sergey Bondarenko wrote:
I created simple test case, so could you please look at it and try to find
out the cause of the problem?
http://download.cl1p.net/javac_bug/?FILE=17647
There are two bat-files in archive: works.bat and fails.bat. The only
difference between them is JDK version.
I
Hi dear Ant developers!
I think I found a bug in Ant javac task, (or maybe in Java compiler).
I need you help to check if it is true.
Javac task behaves differently in Java 6 and Java 5.
For some reason it works properly in Java 5 on the same project structure,
but fails in Java 6.
Imagine
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=18950.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=42397
Summary: NPE when combining files and javac/classpath
Product: Ant
Version: 1.7.0
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
Author: kevj
Date: Wed May 9 21:42:26 2007
New Revision: 536740
URL: http://svn.apache.org/viewvc?view=revrev=536740
Log:
-use antunit-base
Modified:
ant/core/trunk/src/tests/antunit/taskdefs/delete-test.xml
ant/core/trunk/src/tests/antunit/taskdefs/javac-test.xml
ant/core/trunk/src
euge wrote:
May be it's not the place to write my question. If yes, I'm sorry.
Why is it not allowed to put javac in condition tag? Is there any reason
why it was not developed? or the developers did not just get to it yet?
Asking just out of curiosity.
Ant has a very simple view
javac DOES something. It does not CHECK for something...
That's why a
condition
javac
makes not sence.
Otherwise a conditional compile could be done with
target if
javac
construct.
Jan
-Ursprüngliche Nachricht-
Von: euge [mailto:[EMAIL PROTECTED]
Gesendet
Author: peterreilly
Date: Fri Dec 29 06:10:21 2006
New Revision: 491013
URL: http://svn.apache.org/viewvc?view=revrev=491013
Log:
replace a noop test
Modified:
ant/core/trunk/src/tests/antunit/taskdefs/javac-test.xml
Modified: ant/core/trunk/src/tests/antunit/taskdefs/javac-test.xml
URL
Author: peterreilly
Date: Thu Dec 28 08:03:45 2006
New Revision: 490748
URL: http://svn.apache.org/viewvc?view=revrev=490748
Log:
tests for errorProperty and updatedProperty of javac
Added:
ant/core/trunk/src/tests/antunit/taskdefs/javac-dir/
ant/core/trunk/src/tests/antunit/taskdefs
Author: peterreilly
Date: Thu Dec 28 08:06:26 2006
New Revision: 490749
URL: http://svn.apache.org/viewvc?view=revrev=490749
Log:
pset svn:eol-style native
Modified:
ant/core/trunk/src/tests/antunit/taskdefs/javac-dir/bad-src/Bad.java
(contents, props changed)
ant/core/trunk/src/tests
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28941.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35637.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19224.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34138.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19224.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34138.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40839.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
with the current SVN.
This issue is more general than an issue with the javac/ task, it is a change
in the behavior of fileset. Could it be even due to changes in introspection
mechanisms ?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40722.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40722.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=40839
Summary: javac fails with NPE when compiling with eclipse ecj
3.1.x
Product: Ant
Version: 1.7.0Beta3
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40839.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40839.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37148.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
--- Additional Comments From [EMAIL PROTECTED] 2006-10-20 14:22 ---
The REOPENED bug seems to describe something different than the original. As
for Stuff.java being recompiled in the REOPENED stuff, that would be javac for
you. It is a greedy compiler. What would you expect a compiler to do
/show_bug.cgi?id=37148
--- Additional Comments From [EMAIL PROTECTED] 2006-10-20 15:50 ---
FYI: You can prevent javac to be greedy by specifying an explicit empty
sourcepath, as in javac sourcepath= --DD
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19224.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34138.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40722.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=40722
Summary: include if=property logic changed for javac since
ant 1.6.5
Product: Ant
Version: 1.7.0Beta2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40722.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Benson wrote:
Could you distill this down to a smaller example and
submit a report in Bugzilla?
http://issues.apache.org/bugzilla/show_bug.cgi?id=40722
- --
Vlastimil Babka (Caster)
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40718.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40718.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
***
[echo] Avalon-Framework not found: Cannot Build AvalonLogger
[echo]
compile-non-log4j:
[javac] Compiling 12 source files to
/var/tmp/portage/commons-logging-1.1-r1/work/commons-logging-1.1-src/target/classes
[javac] --
...
compile-1.4:
warning:
show-lib-presence
:
- START
log4j12-warning:
log4j13-warning:
logkit-warning:
jdk1.4-warning:
avalon-framework-warning:
[echo]
[echo] *** WARNING ***
[echo] Avalon-Framework not found: Cannot
Build AvalonLogger
[echo]
compile-non-log4j:
[javac] Compiling 12
/show_bug.cgi?id=40718
Summary: javac nested exclude tag broken with comma separated
values
Product: Ant
Version: 1.6.5
Platform: All
URL: http://www.rawbw.com/~kbrussel/anttest.zip
OS/Version: All
Status: NEW
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40718.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40718.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Tue, 10 Oct 2006, Vlastimil Babka [EMAIL PROTECTED] wrote:
Not sure which behaviour is more correct, i.e. if the difference is
a bug or feature.
I don't think we've consciously changed it, so I'd call it a bug.
Stefan
-
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19224.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34138.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
--- Additional Comments From [EMAIL PROTECTED] 2006-09-14 21:52 ---
The error is not that strange
Assuming out have a directory layout:
src/org/acme/A.java
src/poi/C.java
gen/org/acme/plane/B.java
javac srcdir=src destdir=classes/
corresponds to the command line:
javac -sourcepath src -d
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19224.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34138.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
OK. I give up. how do you pass down a fileset by ref as the souce dir to
javac? src is a path ,and there is no srcref ID in the matching task.
I tried to use the fileset inside the src dir, but got told off for not
setting a srcdir attribute:
target name=javac-refid
fileset id
, it was an error (it did work though)
And your exclude is only a hint to Ant, and Javac may overrule that
unless you also reset the sourcepath. Maybe not an issue in your case,
if it's code that doesn't compile on purpose ;-) --DD
I know that , i was going to mention it.
the main thing
Right. But you should be able to pass in a patternset by if, which is
almost as good, no? I'm not sure why filesets are not handled as usual
in javac. It may have to be with the source paths. It could
automatically add all the filesets' dirs to the sourcepath for
example. I noticed this quirk
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28642.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28642.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=39936
Summary: when javac fails, no .class files are created (even for
.java files which had no errors)
Product: Ant
Version: 1.6.5
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity
--- Additional Comments From [EMAIL PROTECTED] 2006-06-30 01:04 ---
This is the behavior of SUN's Javac compiler. Ant cannot do anything about it.
Sorry, --DD
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because
1 - 100 of 501 matches
Mail list logo
