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=37632.
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=35590.
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=36056.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
). They see someone using javac somewhere, they
copy
it, it seems to work, done. I can't imagine any case where you would
intentionally omit the 'source' attr except out of pure laziness.
Guilty. ;)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You
= loader.getResources(foo.properties);
from a warning into an error.
To Matt re. adding verbosity to builds for users who choose to ignore the
documentation's boldface warning - I doubt most people ever read the manual
very carefully (or at all). They see someone using javac somewhere, they copy
it, it seems
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=39183.
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=39183.
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=39183.
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=39183.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=39183
--- Additional Comments From [EMAIL PROTECTED] 2006-04-03 21:43 ---
aah, but presetdef changes the type of teh return of
project.createTask(javac), which could toast any custom task that assumed it
was castable.
It is presetdef problem (or feature) that can be fixed
/show_bug.cgi?id=39183
Summary: Make source attribute of javac mandatory
Product: Ant
Version: 1.6.5
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Core
AssignedTo: dev
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=39183.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Now that Gump has switched to java1.5, its showing up some problems in
javac.
Specifically, it appears to be defaulting to source=1.5
This breaks junit addons
http://vmgump.apache.org/gump/public/junit-addons/junit-addons/gump_work/build_junit-addons_junit-addons.html
I checked out
Specifically, it appears to be defaulting to source=1.5
[...]
I checked out the source in CVS; they are not saying source=1.5; they
are not saying anything about the source version. Yet javac has switched
to java1.5. This is breaking backwards compatibility for builds.
It was always my
Dominique Devienne wrote:
Specifically, it appears to be defaulting to source=1.5
[...]
I checked out the source in CVS; they are not saying source=1.5; they
are not saying anything about the source version. Yet javac has switched
to java1.5. This is breaking backwards compatibility for builds
Now, when rmic's dependency logic broke moving up to 1.5, I fixed it
by forcing the proxy generation to be downwards compatible, so
everything behaved as on a 1.3 or 1.4 box.
True, and was probably the right choice. But there are fewer rmic
users than javac users, so impacts less people
Loughran [EMAIL PROTECTED] wrote:
Dominique Devienne wrote:
Specifically, it appears to be defaulting to source=1.5
[...]
I checked out the source in CVS; they are not saying source=1.5; they
are not saying anything about the source version. Yet javac has
switched
to java1.5. This is breaking
+ months, but which still work.
Its only that they dont compile on java1.5.
if we the properties ant._internal._javac.source and
ant._internal._javac.target that set the defaults for javac, then you
can also use them on the command line to build anything 'legacy',
without touching the build
that set the defaults for javac, then you
can also use them on the command line to build anything 'legacy',
without touching the build file.
-steve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
if we the properties ant._internal._javac.source and
ant._internal._javac.target that set the defaults for javac, then you
can also use them on the command line to build anything 'legacy',
without touching the build file.
Even though someone could abuse these Magic properties for other
On Thu, 23 Mar 2006, Steve Loughran [EMAIL PROTECTED] wrote:
Now that Gump has switched to java1.5, its showing up some problems
in javac.
Specifically, it appears to be defaulting to source=1.5
Please take the time and look into the manual page of the task, in
particular the bold-face notes
forced their hand.
It finally pushed me to start a one hour upload of the Linux JDK
instead of playing with my kids on a weekend ;-)
Here are some options
(1) tweak javac to build at 1.4 or below unless stated.
-1, too late.
(2) provide a back door switch to let gump control the jvm
version
/show_bug.cgi?id=28142
--- Additional Comments From [EMAIL PROTECTED] 2006-01-23 10:26 ---
(In reply to comment #3)
(In reply to comment #2)
the compilerarg element in a javac task has no effect. see below.
I cannot run the command line because arg list is too long.
Thanks.
What
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=28142.
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=28142.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=28142
--- Additional Comments From [EMAIL PROTECTED] 2006-01-20 15:04 ---
(In reply to comment #2)
the compilerarg element in a javac task has no effect. see below.
I cannot run the command line because arg list is too long.
Thanks.
What exactly makes you say the arg list
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=28142.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=38094
--- Additional Comments From [EMAIL PROTECTED] 2006-01-03 15:22 ---
Can't you use compilerarg for the javac task?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee
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=38094.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=38109
Summary: The regular expression is expanded on the windows in the
javac task
Product: Ant
Version: unspecified
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
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=38109.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=38094
Summary: allow to specify also -Xlint:unchecked for target
javac
Product: Ant
Version: 1.7Alpha (nightly)
Platform: Other
OS/Version: Windows XP
Status: NEW
Severity: enhancement
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=38094.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=37148
--- Additional Comments From [EMAIL PROTECTED] 2005-12-28 16:45 ---
Same for me,
javac
excludes=
src path=${src}/
src
just ignores the excludes part.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab
/show_bug.cgi?id=37632
--- Additional Comments From [EMAIL PROTECTED] 2005-11-28 16:01 ---
right... src is a path. So, being that most javac implementations will only
know how to compile files, and path is a filesystem-only resource collection,
any type of resource collection should fit
/show_bug.cgi?id=37632
Summary: javac needs to be resource aware
Product: Ant
Version: 1.7Alpha (nightly)
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
17:10 ---
javac...
src
fileset refid=../
fileset refid=../
/src
/javac
Is that ok?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching
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=37546.
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=37546.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=37546
Summary: javac compilerarg doesn't support 'modern' compiler
Product: Ant
Version: 1.6.5
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
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=37546.
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=34638.
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=34638.
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=31106.
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=31106.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=37174
Summary: javac task and the -Xlint compiler switch
Product: Ant
Version: 1.6.2
Platform: Other
OS/Version: Solaris
Status: NEW
Severity: enhancement
Priority: P2
Component: Core tasks
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=37174.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
that such a usefull option is not brought to light by having a
standard javac property assigned to it.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee
/show_bug.cgi?id=37148
Summary: javac nested src element troube with excludes
Product: Ant
Version: 1.6.5
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
--- Additional Comments From [EMAIL PROTECTED] 2005-10-06 10:36 ---
This is not an ant issue.
issue 1: character encoding
Javac in java 1.5 is much more strict with regard to
the characters in java source files. By default on unix/linux
the character encoding is utf-8. With utf-8 characters
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=36939.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=36939
Summary: javac having issues compiling few classes
Product: Ant
Version: 1.6.2
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
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=36939.
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=34638.
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=34638.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
CLASSPATH variable is probably
correct) since I really ought to be using the jdk1.5.0_02 compiler. If I set
the compiler attribute of javac task in my build.xml to modern, it should
use the javac compiler that comes with my JDK. When I do I get this error:
Unable to find a javac compiler
Martin,
I tried changing my $PATH as you suggested but that didn't help. Also, java
and javac are both the same version (1.5.0_02).
I wonder if ant runs it's processes in another shell - one perhaps that
doesn't pick up my personal env variables? Maybe it doesn't even run them in
bash
[EMAIL PROTECTED] wrote:
Martin,
I tried changing my $PATH as you suggested but that didn't help. Also,
java and javac are both the same version (1.5.0_02).
I wonder if ant runs it's processes in another shell - one perhaps that
doesn't pick up my personal env variables? Maybe it doesn't even
Good Afternoon Paul
The documentation for the ant javac task is available at
http://ant.apache.org/manual/CoreTasks/javac.html
2 things..
set fork = yes
take a look at the parameter called executable
Complete path to the javac executable to use in case of fork=yes
HTH,
Martin-
- Original
I would guess from this trace that there is a bad JAR file somewhere in
my (long, convoluted, m2-tasks created) classpath, something breaking javac.
the problem of course is that javac isnt helpful enough to tell me which
file. I have tried unzipping everything, but of course, ant's unzip
Steve Loughran wrote:
I would guess from this trace that there is a bad JAR file somewhere in
my (long, convoluted, m2-tasks created) classpath, something breaking
javac.
the problem of course is that javac isnt helpful enough to tell me which
file. I have tried unzipping everything
/show_bug.cgi?id=36688
Summary: Using var expansion in include tags fails in javac
Product: Ant
Version: 1.6.5
Platform: All
OS/Version: Windows 2000
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
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=36688.
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=36688.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
-tasks created) classpath, something
breaking javac.
the problem of course is that javac isnt helpful enough to tell me
which file. I have tried unzipping everything, but of course, ant's
unzip task doesnt complain at all, and nor, apparently, does jar
and exec executable=jar /.
what else do
On Fri, 16 Sep 2005, Steve Loughran [EMAIL PROTECTED] wrote:
Why dont we set default=preserve rather than default=add on the
zip tasks, on the basis that it may break BC, but it is probably a
bug to have this problem anyway?
I know I closed a bug report with similar symptoms a while ago.
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=36688.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
for
|on value of debug |on value of debug
|attribute in javac |attribute in javac
--- Additional Comments From [EMAIL PROTECTED] 2005-08-10 20:48 ---
no. this has to be something else. Ant maps true/yes to a boolean value taken
/show_bug.cgi?id=36056
Summary: Manual mistake true for on value of debug attribute
in javac
Product: Ant
Version: 1.6.5
Platform: Other
URL: http://ant.apache.org/manual/CoreTasks/javac.html
OS/Version: other
/show_bug.cgi?id=35891
Summary: Task Javac doesn't include javac -X options of JDK 1.5
Product: Ant
Version: 1.6.5
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: enhancement
Priority: P2
Component: Core
Summary|Task Javac doesn't include |Task Javac doesn't include
|javac -X options of JDK 1.5 |javac -X options of JDK 1.5
--- Additional Comments From [EMAIL PROTECTED] 2005-07-27 13:07 ---
Task javac has compilerarg element precisely because different
/show_bug.cgi?id=35637
--- Additional Comments From [EMAIL PROTECTED] 2005-07-20 22:22 ---
Created an attachment (id=15724)
-- (http://issues.apache.org/bugzilla/attachment.cgi?id=15724action=view)
patch to add a failure property to be set if javac fails
my first patch... not sure if I need
Ok, you approach is fine, even if it doesn't fit my situation as I should find
at what *levels* of the tree structure I should apply your idea.
If you look at the Javac Task implementation you can see that it is not far
from beeing an API, the Javac developer could publish that his/her
We had problem with a (legacy) build from scratch, seems that, because we have
too many java files to compile, nothing is compiled (both on Linux and
Windows2000).
After spending 4 days on that, I decided to split the compilation, I created a
new task, name bydir-javac. The task is derived
Why not simply put two calls to javac in your build script and split the
source tree in two in the same way that you have in your new task,
passing one tree to the first call and the other to the second?
Clearly you need to ensure that the first call compiles pre-requisite
code for the second
=-Xms200m -Xmx1000m
in your .bashrc file
- spawn a jvm for the compiler
javac srcdir=${src}
destdir=${build}
fork=true memoryInitialSize=100m
memoryMaximumSize=1000m/
In extreme cases you can split the code into functional units
to split
because it could break in several months.
Jean
Phil Weighill Smith
wrote:
Why not simply put two calls to javac in your build script and split the
source tree in two in the same way that you have in your new task,
passing one tree to the first call and the other to the second?
Clearly you
put two calls to javac in your build script and split the
source tree in two in the same way that you have in your new task,
passing one tree to the first call and the other to the second?
Clearly you need to ensure that the first call compiles pre-requisite
code for the second call and that you
Phil is right Jean. Independently of splitting the code in subsystems, which
is always a good idea, even if you can't do that you can split the compile
of a single source tree into several passes using regular javac. This can
even enforce dependencies of the code compiled by the different passes
...
Any way, creating a new task that derives from the ant Javac task implemention
was pretty easy to do.
I thank you for you advice.
Jean
Dominique Devienne [EMAIL PROTECTED] wrote:
Phil is right Jean. Independently of splitting the code in subsystems, which
is always a good idea, even
Just FYI, I have legacy code I need to compile, I have been
building it with ant for years...
I just structure my build.xml to compile sections,
i.e. javac srcdir=com.abc
includes=Z/**/*.java/
javac srcdir=com.abc
includes=Y/**/*.java/
And so on for 26 sections!
It has
/show_bug.cgi?id=35637
Summary: Allow javac to set property when compile fails
Product: Ant
Version: unspecified
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: Core tasks
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=35590.
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=35590.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
=quot;javacquot;lt;javac
compiler=quot;$${build.compiler}quot;/lt;/presetdef\2/
/then
/if
/target
/project
This is a batch script that can be used to executed updated build:
#!/bin/bash
ant -f build2.xml
ant -f updated.xml $@
With ANT, you can execute the target and then execute ant
class files should work with.
build.xml
project
property file=build.properties/
!-- set defaults --
property name=javac.source value=1.4/
property name=javac.target value=1.4/
javac source=${javac.source} target=${javac.target} ...
build.properties
javac.source=1.3
/show_bug.cgi?id=35590
Summary: Request: control source/target of javac through a
property
Product: Ant
Version: unspecified
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
22:57 ---
From the manual on javac:
target
Generate class files for specific VM version (e.g., 1.1 or 1.2). Note that the
default value depends on the JVM that is running Ant. In particular, if you use
JDK 1.4+ the generated classes will not be usable for a 1.1 Java VM unless you
] 2005-06-11 08:46 ---
IMHO people using javac should always specify source (which implies a
reasonable target as well). If you wrote the sources, you know what source level
they use, so you should declare it. There is no reason I can see to make this
variable dependent on system config. (Obviously
/show_bug.cgi?id=35325
Summary: javac: properties for default source and target version
Product: Ant
Version: 1.6.2
Platform: All
URL: https://bugs.gentoo.org/show_bug.cgi?id=86903
OS/Version: All
Status: NEW
Severity
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=35325.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
to compile the project with reasonable
defaults for my system.
In this case you'd either have to rewrite the build.xml to introduce those
attrributes or to introduce using the presetdef defined task instead of the
plain javac. I don't see much difference between those two approaches.
Or is there a way
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=35325.
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=35325.
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=31106.
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=31106.
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=31106.
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=31106.
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=11143.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
101 - 200 of 501 matches
Mail list logo
