- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Re: [eclipse] Java problems in scala files
Thu, 2009-11-12, 18:14
2009/11/11 Miles Sabin :
> OK, that shows Scala sources being treated as Java. That indicates
> that the Scala plugins haven't started correctly for some reason or
> other. You say you've verified that JDT Weaving is enabled, and
> presumably you've followed the heap configuration and troubleshooting
> instructions here,
>
> http://www.scala-lang.org/node/94
Yup, though the most heap I could get was 800MB but it should be enough.
>
> If so then I'd suggest starting from a fresh Eclipse install and
> workspace and seeing if we can at least create a basic "Hello world"
> Scala project. If that's successful we can try and see what differs
> from the install/workspace that's causing the problem.
Weird, first I've tried in fresh workspace but it failed, then I unpacked
whole new fresh eclipse and it worked.
After that, I started doing some semi-random changes in my old eclipse
like changing workspaces, restarting with -clean, reinstalling scala and
finally I think after disabling and re-enabling weaving something worked:
a file icon changed from [J] to [S] but opening it produced error like "Unable
to open editor ID scala something". On second attempt (reopening project)
it opened without syntax coloring. One more restart fixed that and cleaning
project removed remaining syntax errors that were reported.
Everything seems to work now.
Fri, 2009-11-13, 07:57
#2
Re: .manager
Hi,
it is used for internal source code management (built in eclipse)
I am not sure if there is a way to turn it off.
On Fri, Nov 13, 2009 at 3:41 AM, Will McQueen <willmcqueen@yahoo.com> wrote:
BR
--
Peter Šiška
it is used for internal source code management (built in eclipse)
I am not sure if there is a way to turn it off.
On Fri, Nov 13, 2009 at 3:41 AM, Will McQueen <willmcqueen@yahoo.com> wrote:
Hi,
Can someone kindly tell me what is the purpose of the ".manager" folder and its contents? I see this folder in the root dir of my project.
Thank you.
Cheers,
Will
BR
--
Peter Šiška
Fri, 2009-11-13, 09:07
#3
Re: .manager
On Fri, 2009-11-13 at 07:51 +0100, Peter Šiška wrote:
> Hi,
> it is used for internal source code management (built in eclipse)
>
> I am not sure if there is a way to turn it off.
It has been replaced by a .scala_dependencies file in 2.8.x.
Best,
Ismael
Fri, 2009-11-13, 18:57
#4
Re: .manager
> it is used for internal source code management (built in eclipse)
Okay, so it sounds like this ".manager" folder is created by some built-in Eclipse functionality that is called by the Scala IDE plugin? Does this have anything to do with the built-in Eclipse Update Manager, or with Eclipse resource markers? The names of the files in this folder seem to be of the form:
_$_<path to each src file in project, separated by '_$_'>
Is this a standard naming convention, or one chosen specifically by Scala IDE?
I don't know when 2.8.x will be available, so in the meantime I'd like to understand more about this to learn how Scala IDE works so that when I run into problems it (as I have in the past), I can smartly troubleshoot.
I didn't find any relevant references to the ".manager" functionality/feature on Google, nor in any of my reference books:
Can you please point me to the relevant keyword (or link/book) for looking-up more info on ".manager"?
At this link:
http://www.scala-lang.org/node/94
...I see that is says:
"There are persistent issues with dependency management which might show us after upgrading. If you experience hangs or extremely slow builds then I recommend locating and deleting the .manager folders that you will find at the top level of your Scala project."
I'd like to know why deleting the ".manager" file might make a difference here.
I noticed that this folder and its contents are marked with "derived" attribute (when I get properties on them). So then after doing a a "clean" build command, the entire folder is wiped-out as expected by any builder that recognizes derived files. It's re-created on the next build command... which leads me to believe it has nothing to do with the Eclipse Update Manager. My best guess is that it has something to do with resource markers, or with creating stubs from the ".java" files that are passed to scalac (similar to what IntelliJ does, I've heard).
More technical info would be greatly appreciated. Thank you.
Cheers,
Will
--- On Thu, 11/12/09, Ismael Juma <mlists@juma.me.uk> wrote:
Okay, so it sounds like this ".manager" folder is created by some built-in Eclipse functionality that is called by the Scala IDE plugin? Does this have anything to do with the built-in Eclipse Update Manager, or with Eclipse resource markers? The names of the files in this folder seem to be of the form:
_$_<path to each src file in project, separated by '_$_'>
Is this a standard naming convention, or one chosen specifically by Scala IDE?
I don't know when 2.8.x will be available, so in the meantime I'd like to understand more about this to learn how Scala IDE works so that when I run into problems it (as I have in the past), I can smartly troubleshoot.
I didn't find any relevant references to the ".manager" functionality/feature on Google, nor in any of my reference books:
- Official Eclipse 3.0 FAQs
- The Java Developer's Guide to Eclipse (2nd ed)
- Eclipse Plug-ins (3rd ed)
Can you please point me to the relevant keyword (or link/book) for looking-up more info on ".manager"?
At this link:
http://www.scala-lang.org/node/94
...I see that is says:
"There are persistent issues with dependency management which might show us after upgrading. If you experience hangs or extremely slow builds then I recommend locating and deleting the .manager folders that you will find at the top level of your Scala project."
I'd like to know why deleting the ".manager" file might make a difference here.
I noticed that this folder and its contents are marked with "derived" attribute (when I get properties on them). So then after doing a a "clean" build command, the entire folder is wiped-out as expected by any builder that recognizes derived files. It's re-created on the next build command... which leads me to believe it has nothing to do with the Eclipse Update Manager. My best guess is that it has something to do with resource markers, or with creating stubs from the ".java" files that are passed to scalac (similar to what IntelliJ does, I've heard).
More technical info would be greatly appreciated. Thank you.
Cheers,
Will
--- On Thu, 11/12/09, Ismael Juma <mlists@juma.me.uk> wrote:
From: Ismael Juma <mlists@juma.me.uk>
Subject: Re: [scala-tools] .manager
To: "Peter Šiška" <siska.pe@gmail.com>
Cc: "Will McQueen" <willmcqueen@yahoo.com>, scala-tools@listes.epfl.ch
Date: Thursday, November 12, 2009, 11:54 PM
On Fri, 2009-11-13 at 07:51 +0100, Peter Šiška wrote:
> Hi,
> it is used for internal source code management (built in eclipse)
>
> I am not sure if there is a way to turn it off.
It has been replaced by a .scala_dependencies file in 2.8.x.
Best,
Ismael
Fri, 2009-11-13, 19:07
#5
Re: .manager
On Fri, Nov 13, 2009 at 5:51 PM, Will McQueen wrote:
>
> > it is used for internal source code management (built in eclipse)
> Okay, so it sounds like this ".manager" folder is created by some built-in
> Eclipse functionality that is called by the Scala IDE plugin?
No, it's unique to the Scala components (for releases <= 2.7.x).
> At this link:
> http://www.scala-lang.org/node/94
> ...I see that is says:
> "There are persistent issues with dependency management which might show us after upgrading. If you experience hangs or extremely slow builds then I recommend locating and deleting the .manager folders that you will find at the top level of your Scala project."
>
> I'd like to know why deleting the ".manager" file might make a difference here.
Because the incremental dependency computation algorithm which depends
on the data persisted in that directory is completely broken and can
get stuck chasing it's tail around cyclic dependencies. When that
happens the only way to unwedge it is to delete the .manager directory
so that the dependency computation starts again from scratch.
It's been completely rewritten on trunk.
Cheers,
Miles
--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://www.chuusai.com/
http://twitter.com/milessabin
Fri, 2009-11-13, 21:57
#6
Re: .manager
Thanks, Miles. So it sounds like if I see compiler errors that don't make sense, I should try manually deleting the ".manager" file and then re-build. And that this is apparently no longer a problem in Scala IDE 2.8.x nightly build.
On this site:
http://www.scala-lang.org/node/94
...it mentions this Scala IDE update site for nightly builds:
http://www.scala-lang.org/scala-eclipse-plugin-nightly
...and says:
"please note that this is the bleeding edge, and we can't gurarantee that it will function correctly or at all."
The "at all" part leads me to believe that there are no continuous integration tests running against these nightly builds that would help guarantee some minimal level of quality for these nightly builds. Is this true? If that's true, then is there some other build (beta, milestone, etc) of the Scala IDE that is less bleeding-edge, but still contains the improvements to the incremental dependency computation algorithm? eg, Some build that does get tested before being blessed as a milestone?
Also, can the Scala IDE 2.8.x plugin be used with Scala 2.7.7? Ideally, I'd like to use a stable Scala IDE v2.8.x with Scala 2.7.7. Otherwise I'm battling against stability on 3 different fronts: Scala 2.8.x, Scala IDE 2.8.x, and (possibly) ScalaTest version for 2.8.x.
Or, maybe the improvements made to the dependency computation algorithm in Scala IDE 2.8.x is dependent on some specific feature that exists only in Scala 2.8.x?
Thank you.
Cheers,
Will
--- On Fri, 11/13/09, Miles Sabin <miles@milessabin.com> wrote:
On this site:
http://www.scala-lang.org/node/94
...it mentions this Scala IDE update site for nightly builds:
http://www.scala-lang.org/scala-eclipse-plugin-nightly
...and says:
"please note that this is the bleeding edge, and we can't gurarantee that it will function correctly or at all."
The "at all" part leads me to believe that there are no continuous integration tests running against these nightly builds that would help guarantee some minimal level of quality for these nightly builds. Is this true? If that's true, then is there some other build (beta, milestone, etc) of the Scala IDE that is less bleeding-edge, but still contains the improvements to the incremental dependency computation algorithm? eg, Some build that does get tested before being blessed as a milestone?
Also, can the Scala IDE 2.8.x plugin be used with Scala 2.7.7? Ideally, I'd like to use a stable Scala IDE v2.8.x with Scala 2.7.7. Otherwise I'm battling against stability on 3 different fronts: Scala 2.8.x, Scala IDE 2.8.x, and (possibly) ScalaTest version for 2.8.x.
Or, maybe the improvements made to the dependency computation algorithm in Scala IDE 2.8.x is dependent on some specific feature that exists only in Scala 2.8.x?
Thank you.
Cheers,
Will
--- On Fri, 11/13/09, Miles Sabin <miles@milessabin.com> wrote:
From: Miles Sabin <miles@milessabin.com>
Subject: Re: [scala-tools] .manager
To: "Will McQueen" <willmcqueen@yahoo.com>
Cc: "Peter Šiška" <siska.pe@gmail.com>, "Ismael Juma" <mlists@juma.me.uk>, scala-tools@listes.epfl.ch
Date: Friday, November 13, 2009, 10:01 AM
On Fri, Nov 13, 2009 at 5:51 PM, Will McQueen <willmcqueen [at] yahoo [dot] com" href="/mc/compose?to=willmcqueen@yahoo.com" rel="nofollow">willmcqueen@yahoo.com> wrote:
>
> > it is used for internal source code management (built in eclipse)
> Okay, so it sounds like this ".manager" folder is created by some built-in
> Eclipse functionality that is called by the Scala IDE plugin?
No, it's unique to the Scala components (for releases <= 2.7.x).
> At this link:
> http://www.scala-lang.org/node/94
> ...I see that is says:
> "There are persistent issues with dependency management which might show us after upgrading. If you experience hangs or extremely slow builds then I recommend locating and deleting the .manager folders that you will find at the top level of your Scala project."
>
> I'd like to know why deleting the ".manager" file might make a difference here.
Because the incremental dependency computation algorithm which depends
on the data persisted in that directory is completely broken and can
get stuck chasing it's tail around cyclic dependencies. When that
happens the only way to unwedge it is to delete the .manager directory
so that the dependency computation starts again from scratch.
It's been completely rewritten on trunk.
Cheers,
Miles
--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://www.chuusai.com/
http://twitter.com/milessabin
Fri, 2009-11-13, 22:07
#7
Re: .manager
On Fri, Nov 13, 2009 at 8:55 PM, Will McQueen wrote:
> Thanks, Miles. So it sounds like if I see compiler errors that don't make
> sense, I should try manually deleting the ".manager" file and then re-build.
Closing the problematic source files and doing a clean build is
usually sufficient, but yes, as a last ditch deleting the .manager
directory might help.
> And that this is apparently no longer a problem in Scala IDE 2.8.x nightly build.
Correct.
> The "at all" part leads me to believe that there are no continuous integration
> tests running against these nightly builds that would help guarantee some
> minimal level of quality for these nightly builds. Is this true?
The continuous integration tests are the users who follow trunk
continuously. If you're able to put together something automated then
please do let me know.
> If that's true, then is there some other build (beta, milestone, etc) of the
> Scala IDE that is less bleeding-edge, but still contains the improvements to
> the incremental dependency computation algorithm? eg, Some build that does get
> tested before being blessed as a milestone?
Not at the moment. There will be something of this sort when the 2.8
beta (nb. not beta candidate) is released.
> Also, can the Scala IDE 2.8.x plugin be used with Scala 2.7.7?
No.
> Ideally, I'd like to use a stable Scala IDE v2.8.x with Scala 2.7.7. Otherwise
> I'm battling against stability on 3 different fronts: Scala 2.8.x, Scala IDE
> 2.8.x, and (possibly) ScalaTest version for 2.8.x.
No matter how desirable, this simply isn't possible.
> Or, maybe the improvements made to the dependency computation algorithm in
> Scala IDE 2.8.x is dependent on some specific feature that exists only in Scala
> 2.8.x?
Yes. In spadefuls ;-)
Cheers,
Miles
--
Miles Sabin
tel: +44 (0)7813 944 528
skype: milessabin
http://www.chuusai.com/
http://twitter.com/milessabin
Can someone kindly tell me what is the purpose of the ".manager" folder and its contents? I see this folder in the root dir of my project.
Thank you.
Cheers,
Will