inter-project dependencies not working in plugin 2.6.1B3?
Migrated from http://lampsvn.epfl.ch/trac/scala/ticket/132
Reporter moors
I have two projects, a and b, that resp. contain packages a and b. Project b's build path has a dependency on project a, but the import a._ in project b does not work. Is this a known limitation?
Reporter moors
I have two projects, a and b, that resp. contain packages a and b. Project b's build path has a dependency on project a, but the import a._ in project b does not work. Is this a known limitation?
package a
class AA {
}
package b
import a._ // error: value a not found :-(
class BB extends AA {
}
I've attached a zip of the two folders in my workspace to help reproduce the problem.
Leave a comment
on 2007-09-25 19:58 *
By tracImporter
on 2007-10-03 07:55 *
By tracImporter
Trac author: mcdirmid
You have to close and re-open your project after any project setting or classpath change. I haven't figured out how to re-initialize the presentation compiler with new settings/classpaths yet so this limitation will hang around for awhile. If you setup the build path before you edit or build, then you should have no porblem as the compilers haven't been initialized yet. Otherwise, close and re-open the project will work. I should pop up a dialogue box that says this, if I can figure out how to do that.
You have to close and re-open your project after any project setting or classpath change. I haven't figured out how to re-initialize the presentation compiler with new settings/classpaths yet so this limitation will hang around for awhile. If you setup the build path before you edit or build, then you should have no porblem as the compilers haven't been initialized yet. Otherwise, close and re-open the project will work. I should pop up a dialogue box that says this, if I can figure out how to do that.
Trac author: mcdirmid
Should work now.
Should work now.
on 2008-04-08 15:50 *
By tracImporter
Closed As: fixed