Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 490570

Summary: [1.9] JDT's ant adapter should not rely on attributes unsupported in Jigsaw
Product: [Eclipse Project] JDT Reporter: Jay Arthanareeswaran <jarthana>
Component: CoreAssignee: Jay Arthanareeswaran <jarthana>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 4.5.1   
Target Milestone: BETA J9   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Jay Arthanareeswaran CLA 2016-03-29 05:00:58 EDT
The Ant compiler adapter (mostly in JDTCompilerAdapter) is using attributes such as -bootclasspath, -extdirs which no longer make sense with Jigsaw.

I currently don't know if this poses a problem, but we will use this bug to investigate and track if there's any impact.
Comment 1 Jay Arthanareeswaran CLA 2016-08-18 09:16:34 EDT
I can confirm that with Javc the following testcase fails:

<?xml version="1.0" encoding="UTF-8"?>
<project name="Eclipse Batch Compiler" default="init" basedir="..">
	<target name="init">
		<property name="srcdir" value="${user.dir}/src" />
		<property name="dest" value="${user.dir}/dest" />
		<javac target="1.9" source="1.9" srcdir="${srcdir}" destdir="${dest}" >
		    <compilerarg value="-Xbootclasspath/p:${boot.path}"/>
  		</javac>
	</target>
</project>

Error reported:

    [javac] javac: option -Xbootclasspath/p: not allowed with target 1.9

As of now, ECJ doesn't report any error.
Comment 2 Jay Arthanareeswaran CLA 2016-08-19 02:34:20 EDT
(In reply to Jay Arthanareeswaran from comment #1)
>     [javac] javac: option -Xbootclasspath/p: not allowed with target 1.9
> 
> As of now, ECJ doesn't report any error.

With a fix for bug 499961, the error is reported for bootclasspath and extdirs. ECJ doesn't appear to do anything with -Xbootclasspath, in which case, not reporting the error seems fine to me.
Comment 3 Eclipse Genie CLA 2019-11-19 20:03:11 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.