Redefining classes/objects <-> packages gives errors until a clean
If you define a class/object Foo, then later change this to a package, you're left with an error complaining that "Foo is already defined as object Foo," and vice-versa.
To repro, try:
package blah {
object foo
}
Save, then change that to:
package blah {
package foo {}
}
You'll then see the error.
Assigning normal priority since this can be worked around with a Project > Clean.
Using the latest nightly.
To repro, try:
package blah {
object foo
}
Save, then change that to:
package blah {
package foo {}
}
You'll then see the error.
Assigning normal priority since this can be worked around with a Project > Clean.
Using the latest nightly.
Leave a comment
on 2011-07-22 13:12 *
By Mirco Dotta
Milestone set to 2.0
Priority changed from Normal (3) to High (2)
Hubert, I'm assigning this to you as I believe that the coming sbt builder should fix this issue. If I'm wrong, please reassigned it to me.
on 2011-08-11 18:36 *
By Mirco Dotta
This is working fine with the new sbt builder from the nightly (just tested).
Though, if `package foo` is changed back to `object foo`, an error is reported. This might be a sbt problem, we need to check that.
Though, if `package foo` is changed back to `object foo`, an error is reported. This might be a sbt problem, we need to check that.
on 2011-08-15 21:15 *
By Mirco Dotta
This works fine when compiling within SBT, hence it's an IDE bug and we have to fix it on our side :)
on 2011-09-26 17:31 *
By Iulian Dragos
Both SBT and the Eclipse SBT builder leave around the old (empty) directory corresponding to the package. It looks like the Eclipse compiler uses the output directory as part of the class path, which SBT does not (or something similar), hence the double definition error.
on 2012-01-30 18:37 *
By skyluc
Assigned to changed from Hubert Plociniczak to -none-
Permission type changed from None to Public