[Lift] Re: NetBeans and complex parser combinator files

2008-10-09 Thread Viktor Klang
Is it permGen OOM or Heap OOM?

On Wed, Oct 8, 2008 at 7:21 PM, David Pollak [EMAIL PROTECTED] wrote:


 Folks,

 I've been using NetBean pretty successfully... except for projects that
 refer to complex parser combinator files (e.g., Lift's Textile parser.)
 NetBeans looks for stuff on the classpath and when it gets to the file
 with the complex parser combinator stuff in it, it gets Out of Memory
 exceptions (I've allocated 3GB to the NB process).

 Is there a way to ask NetBeans to not parse these files?  Alternatively,
 is there a way to reduce the memory needs for these complex files?

 Thanks,

 David

 PS -- There's a separate problem editing these files, but I'm not
 worried about that right now... I'm happy to use emacs to edit the files.


 



-- 
Viktor Klang
Senior Systems Analyst

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---



[Lift] Re: NetBeans and complex parser combinator files

2008-10-09 Thread David Pollak


Erik Engbrecht wrote:
 I haven't tried this, but if possible I'd suggest moving them into a 
 separate libary and only letting NetBeans see the compiled jar.
Unfortunately, that doesn't work.  Anything that is seen as part of the 
project is parsed.  So, I can't edit the Lift Example code because it 
refers to the Lift Textile parser (even though it just refers to the JAR).

  
 As a side note, I bet the Eclipse plugin has the same problem.  They 
 are both use pieces of Scala compiler, and anything that makes the 
 compiler work hard makes the IDE work several times harder, because 
 new stuff is continuously being pushed through pieces of the compiler.

 On Wed, Oct 8, 2008 at 1:21 PM, David Pollak [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] wrote:


 Folks,

 I've been using NetBean pretty successfully... except for projects
 that
 refer to complex parser combinator files (e.g., Lift's Textile
 parser.)
 NetBeans looks for stuff on the classpath and when it gets to the file
 with the complex parser combinator stuff in it, it gets Out of Memory
 exceptions (I've allocated 3GB to the NB process).

 Is there a way to ask NetBeans to not parse these files?
  Alternatively,
 is there a way to reduce the memory needs for these complex files?

 Thanks,

 David

 PS -- There's a separate problem editing these files, but I'm not
 worried about that right now... I'm happy to use emacs to edit the
 files.



 

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---



[Lift] Re: NetBeans and complex parser combinator files

2008-10-09 Thread Miles Sabin

On Thu, Oct 9, 2008 at 1:55 PM, Erik Engbrecht [EMAIL PROTECTED] wrote:
 As a side note, I bet the Eclipse plugin has the same problem.

It'd be much appreciated if someone could give this a try ...

Cheers,


Miles

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---