Error marks on class references in dependent jars that have same packages
Say, I have project A having a ClassA.java in my.package, and it depends on project B having a ClassB.java in the same my.package. (I know it is not a good practice but that is what our legacy system does) . When I refer them in a scala class, either ClassA or ClassB will have a "not found: value" error mark depends on the Build Classpath Order setting. The project works fine in maven build and it seems the scala class get built in Eclipse too. Just the error marks are annoying.
Leave a comment