search

omkardash / jaql

Automatically exported from code.google.com/p/jaql
0 stars 0 forks source link

Class resolution depends on order of jars #78

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a class called A
2. Create a class called B that derives from A
3. Create a jars for A and B
4. Call jaql, listing B.jar,A.jar as the additional jars (in that order)
5. Call B to produce the error

What is the expected output? What do you see instead?

This is a regression. The union of all classes supplied on the command 
line should be resolved from jaql. In this case, the call to B should 
work. The problem with this regression is that user scripts that 
previously specified multiple jars, in particular when the list of jars 
included inter-dependencies (such as the example above), now fail.

Original issue reported on code.google.com by vuk.erce...@gmail.com on 20 Apr 2010 at 12:48

GoogleCodeExporter commented 9 years ago 
The fix has been checked in and unit tests added. Refer to 
src/test/com/ibm/jaql/util/TestClassLoader.java along with sample jars A.jar, 
B.jar.

Original comment by vuk.erce...@gmail.com on 20 Apr 2010 at 12:51