Home > Ant Cannot > Ant Cannot Use Classic Compiler

Ant Cannot Use Classic Compiler

The easiest way then would be to use a property for your javac executable attributes. and then on the command line you by faisal abdallah on December 12 2000 21:42 EST bloody classic compiler ![ Go to top ] Posted by: faisal abdallah Posted on: December 12 2000 21:42 EST in response to The one in Sun's jdk118_v1 usesJAVA_HOME if it is set,and consequently fails if used from an "exec" in ant under jdk1.2.(I modified .java_wrapper to solve the problem.)Doug.--------------------------------------------------------------------Douglas Guptill [email protected] Assurance Specialist All other users should be unaffected by this change.

java.vendor.url : http://java.sun.com/ path.separator : ; java.vm.name : Java HotSpot(TM) Client VM file.encoding.pkg : sun.io user.country : US sun.os.patch.level : Service Pack 2 java.vm.specification.name : Java Virtual Machine Specification user.dir : XINDICE uses the -classpath set method for execution thereby avoiding my versions of ant (1.5.3-1), xalan (2.5-D.1), xerces (1.4.4), and xml-apis (version unknown w/size of 122 kb). Bug25577 - ANT uses wrong class/bin path! I would send you homepage comments to the eclipse webmaster.

Thanks a bunch. modern (the standard compiler of JDK 1.3/1.4/1.5/1.6/1.7) – javac1.3 and javac1.4 and javac1.5 and javac1.6 and javac1.7 (since Ant 1.8.2) can be used as aliases. What is really curved, spacetime, or simply the coordinate lines?

Thanks again. When I initially used a simple example in a directory with a build.xml file and a simple java application, I received the classic compiler message. extJavac (run either modern or classic in a JVM of its own). Dennis Post Reply Bookmark Topic Watch Topic New Topic Similar Threads echo classpath in build Classic Compiler error while running ant.

The workaround is to fork when invoking the compiler. This easily solved using a property for the executable and then passing it from the command line with -D (e.g., -Dmyjavacpath=whatever will set the ${myjavacpath} variabile –Matteo Oct 23 '11 at The external Ant build works fine and building with Eclipse itself works fine. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed

awt.toolkit : sun.awt.windows.WToolkit java.vm.info : mixed mode java.version : 1.4.1_02 java.ext.dirs : c:\j2sdk\jre\lib\ext sun.boot.class.path : c:\j2sdk\jre\lib\rt.jar;c:\j2sdk\jre\lib\i18n.jar;c:\j2sdk\jre\lib\sunrsasig n.jar;c:\j2sdk\jre\lib\jsse.jar;c:\j2sdk\jre\lib\jce.jar;c:\j2sdk\jre\lib\ch arsets.jar;c:\j2sdk\jre\classes java.vendor : Sun Microsystems Inc. However, in the case of the xindice build, the build routine could never find my java file and instead I ened up with the following variation to the above message: "Unable yes - to c:\j2sdk %JAVA_HOME%\lib\tools.jar exists? As a point of order, if you leave both in the directory and try to do a build, the 1.4.1 version is used.

TechTarget Corporate Web Site|Media Kits|Reprints|Site Map All Rights Reserved, Copyright 2000 - 2,016, TechTarget|Terms of Use|Read our Privacy Statement TechTarget - The IT Media ROI Experts IBM developerWorksSorry! why not find out more You should set it to /usr/java (assuming that you'vegot the tree /usr/java/jre.....). Perhaps JAVA_HOME does not point to the JDK Total time: 1 second -----Original Message----- From: Jesse Stockall [mailto:[email protected]] Sent: Monday, May 05, 2003 5:10 PM To: Ant Users List Subject: RE: asked 5 years ago viewed 17095 times active 5 years ago Linked 3 Ant build failing, “[javac] javac: invalid target release: 7” 0 javac class not found when compiling with ant

Valid values for either the build.compiler property or the compiler attribute are: classic (the standard compiler of JDK 1.1/1.2) – javac1.1 and javac1.2 can be used as aliases. Description MH 2002-10-31 07:02:07 EST I tried to compile one Eclipse Project with the new Java 1.4.1 SDK but calling the ANT script from within Eclipse always got errors when I The target from your build file. >From the XINDICE.zip Note - I am using the updated batch files for java 1.4 from the users group and not the ones shipped Not the answer you're looking for?

Then typedef that task and use it in the javac compiler attribute. I have an installation of gcj, built as part of gcc, within a library we distribute, and I'd like to have a particular piece of Java software built against that. C:\poolman-2.0.3\build>echo %JAVA_HOME% C:\jdk1.3 Why is ant throwing up this message. at org.apache.tools.ant.taskdefs.compilers.Javac12.execute (Javac12.java:96) at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:557) at org.apache.tools.ant.Task.perform(Task.java:217) at org.apache.tools.ant.Target.execute(Target.java:184) at org.apache.tools.ant.Target.performTasks(Target.java:202) at org.apache.tools.ant.Project.executeTarget(Project.java:601) at org.apache.tools.ant.Project.executeTargets(Project.java:560) at org.eclipse.ant.internal.core.ant.InternalAntRunner.run (InternalAntRunner.java:262) at java.lang.reflect.Method.invoke(Native Method) at org.eclipse.ant.core.AntRunner.run(AntRunner.java:233) at org.eclipse.ui.externaltools.internal.core.AntFileRunner.execute (AntFileRunner.java:59) at org.eclipse.ui.externaltools.internal.core.DefaultRunnerContext.executeRunner (DefaultRunnerContext.java:413) at org.eclipse.ui.externaltools.internal.core.DefaultRunnerContext.run

sj (Symantec java compiler) – symantec can be used as an alias. How to NOT render a part of a document Singular cohomology and birational equivalence Mysterious creeper-like explosions Add-in salt to injury? Thanks, Andy Bowes Ranch Hand Posts: 171 posted 13 years ago Have you tried setting your JAVA_HOME environment variable as it suggests in the output ?

D:\projects\Java\J2EE\Servlet\build.xml:13: Cannot use classic compiler, as it is not available A common solution is to set the environment variable JAVA_HOME to your jdk directory.

Info: i have set JAVA_HOME to my JDK 1.4.0_01 installation. Word for "using technology inappropriately"? Repeating my original questions from my 1st reply: Can you please confirm the following: JAVA_HOME is set? %JAVA_HOME%\lib\tools.jar exists? %JAVA_HOME%\bin\javac.exe exists? First Last Prev Next This bug is not in your last search results.

Back to the top DownloadGetting StartedMembersProjects Community MarketplaceEventsPlanet EclipseNewsletterVideosParticipate Report a BugForumsMailing ListsWikiIRCHow to ContributeWorking Groups AutomotiveInternet of ThingsLocationTechLong-Term SupportPolarSysScienceOpenMDM More CommunityMarketplaceEventsPlanet EclipseNewsletterVideosParticipateReport a BugForumsMailing ListsWikiIRCHow to ContributeWorking GroupsAutomotiveInternet of ThingsLocationTechLong-Term Description MH 2002-08-21 08:33:09 EDT When I want to call the build.xml in my project (select "build.xml", right click, popup menu "Run Ant", select target, press "Finish"), i get the following Brad Baker Greenhorn Posts: 15 posted 13 years ago I don't undstand why I am geting this: [javac] Modern compiler is not available - using classic compiler Here is my build.xml Messenger.

latex command for diagonal matrix of this kind Was there no tax before 1913 in the United States? Buildfile: build.xml init: idl: prepare: clean-jar: [delete] Deleting: C:\xindice\java\lib\xindice.jar [delete] Unable to delete file C:\xindice\java\lib\xindice.jar src: [echo] Compiling Source [javac] Modern compiler is not available - using classic compiler [javac] Compiling Buildfile: build.xml init: idl: prepare: clean-jar: [delete] Deleting: C:\xindice\java\lib\xindice.jar [delete] Unable to delete file C:\xindice\java\lib\xindice.jar src: [echo] Compiling Source [javac] Compiling 324 source files to C:\xindice\java\classes BUILD FAILED file:c:/xindice/build.xml:123: Unable to I have: in my build.xml and it gives me: [echo] JavaHome: d:\java\jdk1.4.1 So as far as I can tell I have JAVA_HOME set.

Get thread feed bloody classic compiler ! (1 messages) Posted by: faisal abdallah Posted on: December 05 2000 19:33 EST Hi Recently I've run into a stupid ANT makefile problem I How is True < 2 implemented? The first two Google links returned for a searchon "ant cannot use classic compiler" seem to have info onthis error, but the links are broken.I suspect that this must be some more hot questions question feed default about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation

Join them; it only takes a minute: Sign up How to tell ant to build using a specific javac executable? Build exception: D:\data\deka\bav\build.xml:71: Cannot use classic compiler, as it is not available A common solution is to set the environment variable JAVA_HOME to your jdk directory. Is "she don't" sometimes considered correct form? WebSphere Studio Problem Anyone ever compiled poolman (one dead end after another) Eclipse/Ant Issue - Modern compiler is not available [ant][eclipse][junit] fails to build All times are in JavaRanch time: GMT-6

A common solution is to > set the environment variable JAVA_HOME to your jdk directory. > > Total time: 1 second > > ____________________________________________ > > Report message to a moderator Post Reply Bookmark Topic Watch Topic New Topic Similar Threads Classic Compiler error while running ant. Realizing this work is unfunded :-), it would be nice if when some of the common files were updated as binary distributions, the supported projects would be re-zipped with the most Basically, it's the install dir for thejdk, not for the jre (which is what many other programs expect when they seeJAVA_HOME)Matt-----Original Message-----From: Joe FaithSent: Thursday, November 30, 2000 9:11 AMTo: [email protected]:

D:\GameServe\build.xml:43: Cannot use classic compiler, as it is not available A common solution is to set the environment variable JAVA_HOME to your jdk directory. I think the solution is to make sure your path contains one JDK or at least the one you want first in the path. Email This Discussions EJB design: bloody classic compiler ! That is to say Eclipse isn't using javac from the PATH but the Ant it launches most definitely is.

J2EE 1.3.1 works with JDK 1.4. See iftools.jar is there and no typo occurred.The easiest way to ensure that Ant will pick up tools.jar is settingJAVA_HOME correctly and invoke Ant via its ant shell script BTW, noneed Messenger.http://im.yahoo.com reply | permalink Matthew Geis Are you sure you've set the JAVA_HOME environment variable? Closing bug.