You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bu...@apache.org on 2017/12/29 18:56:00 UTC

[Bug 61936] New: Ant not picking the correct javac version

https://bz.apache.org/bugzilla/show_bug.cgi?id=61936

            Bug ID: 61936
           Summary: Ant not picking the correct javac version
           Product: Ant
           Version: 1.9.9
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Build Process
          Assignee: notifications@ant.apache.org
          Reporter: sdev1978@rediffmail.com
  Target Milestone: ---

I have multiple versions of java installed in my machine and I am changing the
JAVA_HOME and putting the following lines in build.xml

<javac srcdir="${JAVA_SRC_DIR}"    destdir="${JAVA_BUILD_DIR}"  
includeAntRuntime="no"   taskname ="javac1.6">
                 <classpath refid="class.path"/>


Whatever I put in the taskname is not shown in ant.java.version.The java
version what is defined in JAVA_HOME gets shown though on the command prompt I
can see that the compilation is going on with javac1.6,javac1.7,javac1.8

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61936] Ant not picking the correct javac version

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61936

moultryjermaine@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WORKSFORME                  |DUPLICATE

--- Comment #2 from moultryjermaine@gmail.com ---


*** This bug has been marked as a duplicate of bug 3 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61936] Ant not picking the correct javac version

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61936

Jan Mat <ja...@materne.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME
                 OS|                            |All

--- Comment #1 from Jan Mat <ja...@materne.de> ---
The taskname attribute has nothing to do with other properties.
Every task has this attribute and this controlls the name of the task in the
log (e.g. the console log during the build).

<echo message="test"/>
 [echo] test

<echo message="test" taskname="test"/>
[test] test

I use this if I use presetdef or macrodef or scriptdef.

-- 
You are receiving this mail because:
You are the assignee for the bug.