Bug #7255
FWD resolves a OO file not included in conversion, if it exists on disk and on PROPATH
Status:
New
Priority:
Urgent
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
History
#2 Updated by Constantin Asofiei about 1 year ago
For an application, you can have a abl/src1/oo/Bar.cls
and abl/src2/oo/Bar.cls
. In conversion, you include only abl/src2/oo/Bar.cls
and some class abl/src/oo/Foo.cls
which extends (or inherits) from oo.Bar
, as an explicit file list.
On PROPATH in p2j.cfg.xml
, you have abl/src1
, abl/src2
and abl/src
. During conversion, FWD will wrongly match on abl/src1/oo/Bar.cls
when resolving oo.Bar
, even if this file is not included in conversion.
Of course this can be solved by not having abl/src1/oo/Bar.cls
at all on disk, but I think we need to fix FWD so that the PROPATH lookup is done only for files included in conversion.