problem with eclipse plugin?

Olindo,

The Eclipse plug-in is coming along well, but it is still very much a WIP, as far as I can see. If you're willing to go to the effort of learning the basics of another IDE, the IntelliJ IDEA Community Edition works pretty well. It has its own problems, but as of the most recent "stable" version of Eclipse, it is significantly more useable than Eclipse, IMHO. If your goal right now is to learn Scala and start using it, that's the route I'd recommend. Then when you're more familiar with the language, you can shift back to the Eclipse environment, and you'll be in a better position to figure out what is a Scala problem and what is an Eclipse problem.

If you do decide to try IDEA and also want to use SBT (which I'd recommend if you're just in a learning phase), you'll probably want to use two third-party plugins, somewhat confusingly named "idea-sbt-plugin" and "sbt-idea-plugin" (in addition to enabling IDEA's own Scala support). You can find docs on these through a Google search.

I hope this doesn't come across as me dissing the Eclipse Scala plugin. Given the ubiquity of Eclipse, I think that Eclipse support is absolutely vital for Scala's success, and I'm really glad to see the progress that is being made in that direction. I simply think that, for a newcomer _at the moment_, trying to get into Scala via Eclipse can be a little frustrating.

Cheers,
Ken

On Mar 30, 2011, at 11:06 AM, Olindo Pindaro wrote:

> I configurated my Helios using plugin with scala 2.8.
>
>
> it slow in compilation (but Odersky declared that incremental
> compilation is not implemented).
>
> But it shows some oddities growing the size of code in a project.
>
> 1) package must must be organized as directory as Java
> 2) Sometime some classes required import to use other classes in some
> package (and directory)
> 3) Import at 2) report me a warning of "not necessary" import
> 4) Int.toByte or Int.asInstanceofByte[Byte] give me compilation error,
> the same snippet in an other (small) scala projects works fine.
>
> i am a little discoraged even if I am a newbe and is hard to
> understand what is a my fualt and what is plug-in bug.
>
> Other experiences?
> Suggestion.
>
>
> Thank to all.

I would also recommend checking out Intellij. I only recently started using it instead of Eclipse, and it has been a great boon to my Scala work.Its not perfect, but the warts are a lot smaller and less painful than the current version of the Eclispe plugin. Unless you are willing to be an early-access tester for the Eclipse plugin, I would switch over to Intellij until a more stable and feature-rich version of the Eclipse plugin is released.

Brian Maso

On Wed, Mar 30, 2011 at 11:49 AM, Kenneth McDonald <kenneth.m.mcdonald@sbcglobal.net> wrote:

Olindo,

The Eclipse plug-in is coming along well, but it is still very much a WIP, as far as I can see. If you're willing to go to the effort of learning the basics of another IDE, the IntelliJ IDEA Community Edition works pretty well. It has its own problems, but as of the most recent "stable" version of Eclipse, it is significantly more useable than Eclipse, IMHO. If your goal right now is to learn Scala and start using it, that's the route I'd recommend. Then when you're more familiar with the language, you can shift back to the Eclipse environment, and you'll be in a better position to figure out what is a Scala problem and what is an Eclipse problem.

If you do decide to try IDEA and also want to use SBT (which I'd recommend if you're just in a learning phase), you'll probably want to use two third-party plugins, somewhat confusingly named "idea-sbt-plugin" and "sbt-idea-plugin" (in addition to enabling IDEA's own Scala support). You can find docs on these through a Google search.

I hope this doesn't come across as me dissing the Eclipse Scala plugin. Given the ubiquity of Eclipse, I think that Eclipse support is absolutely vital for Scala's success, and I'm really glad to see the progress that is being made in that direction. I simply think that, for a newcomer _at the moment_, trying to get into Scala via Eclipse can be a little frustrating.

Cheers,
Ken

On Mar 30, 2011, at 11:06 AM, Olindo Pindaro wrote:

> I configurated my Helios using plugin with scala 2.8.
>
>
> it slow in compilation (but Odersky declared that incremental
> compilation is not implemented).
>
> But it shows some oddities growing the size of code in a project.
>
> 1) package must must be organized as directory as Java
> 2) Sometime some classes required import to use other classes in some
> package (and directory)
> 3) Import at 2) report me a warning of "not necessary" import
> 4) Int.toByte or Int.asInstanceofByte[Byte] give me compilation error,
> the same snippet in an other (small) scala projects  works fine.
>
> i am a little discoraged even if I am a newbe and is hard to
> understand what is a my fualt and what is plug-in bug.
>
> Other experiences?
> Suggestion.
>
>
> Thank to all.

--
Best regards,
Brian Maso
(949) 395-8551
brian@blumenfeld-maso.com

i'd go for idea right now, but i'm biased. but that's only because idea
is better :)
i suggest giving every ide a change every once in a while to see if they
improved, i regularly check eclipse and netbeans. kepps you from
becoming a "i only use what i know"-type

Am 30.03.2011 20:49, schrieb Kenneth McDonald:
> Olindo,
>
> The Eclipse plug-in is coming along well, but it is still very much a WIP, as far as I can see. If you're willing to go to the effort of learning the basics of another IDE, the IntelliJ IDEA Community Edition works pretty well. It has its own problems, but as of the most recent "stable" version of Eclipse, it is significantly more useable than Eclipse, IMHO. If your goal right now is to learn Scala and start using it, that's the route I'd recommend. Then when you're more familiar with the language, you can shift back to the Eclipse environment, and you'll be in a better position to figure out what is a Scala problem and what is an Eclipse problem.
>
> If you do decide to try IDEA and also want to use SBT (which I'd recommend if you're just in a learning phase), you'll probably want to use two third-party plugins, somewhat confusingly named "idea-sbt-plugin" and "sbt-idea-plugin" (in addition to enabling IDEA's own Scala support). You can find docs on these through a Google search.
>
> I hope this doesn't come across as me dissing the Eclipse Scala plugin. Given the ubiquity of Eclipse, I think that Eclipse support is absolutely vital for Scala's success, and I'm really glad to see the progress that is being made in that direction. I simply think that, for a newcomer _at the moment_, trying to get into Scala via Eclipse can be a little frustrating.
>
> Cheers,
> Ken
>
> On Mar 30, 2011, at 11:06 AM, Olindo Pindaro wrote:
>
>> I configurated my Helios using plugin with scala 2.8.
>>
>>
>> it slow in compilation (but Odersky declared that incremental
>> compilation is not implemented).
>>
>> But it shows some oddities growing the size of code in a project.
>>
>> 1) package must must be organized as directory as Java
>> 2) Sometime some classes required import to use other classes in some
>> package (and directory)
>> 3) Import at 2) report me a warning of "not necessary" import
>> 4) Int.toByte or Int.asInstanceofByte[Byte] give me compilation error,
>> the same snippet in an other (small) scala projects works fine.
>>
>> i am a little discoraged even if I am a newbe and is hard to
>> understand what is a my fualt and what is plug-in bug.
>>
>> Other experiences?
>> Suggestion.
>>
>>
>> Thank to all.
>

Learning an other IDE doesn't look me attractive..

I am going to try beta 2.0 eclipse plugin version hoping perform
better..

I any case i will submit bug to Scala org.

I agree that support for eclipse could be the edge beetwen a large
adoption in real world and an amazingand powrfull language for nerds?

Cheers
Olindo

On 30 Mar, 21:10, HamsterofDeath wrote:
> i'd go for idea right now, but i'm biased. but that's only because idea
> is better :)
> i suggest giving every ide a change every once in a while to see if they
> improved, i regularly check eclipse and netbeans. kepps you from
> becoming a "i only use what i know"-type
>
> Am 30.03.2011 20:49, schrieb Kenneth McDonald:
>
>
>
>
>
>
>
> > Olindo,
>
> > The Eclipse plug-in is coming along well, but it is still very much a WIP, as far as I can see. If you're willing to go to the effort of learning the basics of another IDE, the IntelliJ IDEA Community Edition works pretty well. It has its own problems, but as of the most recent "stable" version of Eclipse, it is significantly more useable than Eclipse, IMHO. If your goal right now is to learn Scala and start using it, that's the route I'd recommend. Then when you're more familiar with the language, you can shift back to the Eclipse environment, and you'll be in a better position to figure out what is a Scala problem and what is an Eclipse problem.
>
> > If you do decide to try IDEA and also want to use SBT (which I'd recommend if you're just in a learning phase), you'll probably want to use two third-party plugins, somewhat confusingly named "idea-sbt-plugin" and "sbt-idea-plugin" (in addition to enabling IDEA's own Scala support). You can find docs on these through a Google search.
>
> > I hope this doesn't come across as me dissing the Eclipse Scala plugin. Given the ubiquity of Eclipse, I think that Eclipse support is absolutely vital for Scala's success, and I'm really glad to see the progress that is being made in that direction. I simply think that, for a newcomer _at the moment_, trying to get into Scala via Eclipse can be a little frustrating.
>
> > Cheers,
> > Ken
>
> > On Mar 30, 2011, at 11:06 AM, Olindo Pindaro wrote:
>
> >> I configurated my Helios using plugin with scala 2.8.
>
> >> it slow in compilation (but Odersky declared that incremental
> >> compilation is not implemented).
>
> >> But it shows some oddities growing the size of code in a project.
>
> >> 1) package must must be organized as directory as Java
> >> 2) Sometime some classes required import to use other classes in some
> >> package (and directory)
> >> 3) Import at 2) report me a warning of "not necessary" import
> >> 4) Int.toByte or Int.asInstanceofByte[Byte] give me compilation error,
> >> the same snippet in an other (small) scala projects  works fine.
>
> >> i am a little discoraged even if I am a newbe and is hard to
> >> understand what is a my fualt and what is plug-in bug.
>
> >> Other experiences?
> >> Suggestion.
>
> >> Thank to all.

Olindo,

I am using the Eclipse Scala plugin WIP 2.9 snapshot on a large project
and it's usable and it's becoming better day by day.

I agree with you, the standard 2.8 version, on my codebase, would hang
in no time, it would simply not cope with the size of the project. I was
using ItelliJ IDEA with SBT integration and Scala plugin. I have
abandoned IDEA and replaced it with Eclipse Helios + Scala WIP 2.9.

The actual build on Jenkins is done with SBT compiling against Scala
2.8.1, but within the editor it's using 2.9 (this also guarantees my
code can compile on both versions).

To switch, I have used eclipsify SBT plugin to create all the various
project files from the SBT project. Then unfortunately a lot of manual
changes were needed (eclipsify is far from perfect) but it only took me
half an hour and overall eclipsify saved me time. I think there is a
plan to make the Scala Eclipse plugin open SBT projects directly,
looking forward to that!

Anyway, this is the link:
http://scala-ide.assembla.com/wiki/show/scala-ide/wip_experiment

And this is the update site:
https://scala-webapps.epfl.ch/jenkins/job/scala-ide-wip_experiment/ws/or
g.scala-ide.sdt.update-site/target/site/

There are a few minor issues, but nothing major.
The minimum recommended heap size for eclipse (in order to use scala
plugin) is 1500M, but I know it can also run with 1000M. On one
workstation I am giving 3000M (it has 8G), on the other I have to run
with 1000M (and it still gets job done).
I recommend changing/adding lines to eclipse.ini to make sure you have:

--launcher.XXMaxPermSize
256m
-vmargs
-server
-XX:+DoEscapeAnalysis
-XX:+CMSClassUnloadingEnabled
-Xms600m
-Xmx1500m (or more)

Does anyone have a better or more official set of eclipse.ini
parameters?
Make sure you run Java 6u24 if you can.
I think the 1.5GB requirement seems very very high... but at then end of
the day when I write code I do little else and I can use most of my RAM
for the editor.

Let us know how this works for you and if you find any bugs, let the
team know.

Hope this helps.

Tommaso

-----Original Message-----
From: scala-user@googlegroups.com [mailto:scala-user@googlegroups.com]
On Behalf Of Olindo Pindaro
Sent: 30 March 2011 17:07
To: scala-user
Subject: [scala-user] problem with eclipse plugin?

I configurated my Helios using plugin with scala 2.8.

it slow in compilation (but Odersky declared that incremental
compilation is not implemented).

But it shows some oddities growing the size of code in a project.

1) package must must be organized as directory as Java
2) Sometime some classes required import to use other classes in some
package (and directory)
3) Import at 2) report me a warning of "not necessary" import
4) Int.toByte or Int.asInstanceofByte[Byte] give me compilation error,
the same snippet in an other (small) scala projects works fine.

i am a little discoraged even if I am a newbe and is hard to
understand what is a my fualt and what is plug-in bug.

Other experiences?
Suggestion.

Thank to all.

The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed, to persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS do not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW

Ah, yes:

http://download.scala-ide.org/

Beta releases relative to Scala 2.9.0.RC1
Scala IDE 2.0.0-beta1 with Scala 2.9.0.RC1
Note that this build does not support Eclipse Galileo.
Update site URL: http://download.scala-ide.org/releases/wip_experiment-2.0.0-beta1

That's pretty much what I am using, except I am on the latest snapshot... (link I gave you in other post). I am used to be on the snapshot, but probably you are right, this is a better way to go for you.

Let us know.

Tommaso

-----Original Message-----
From: scala-user@googlegroups.com [mailto:scala-user@googlegroups.com] On Behalf Of Olindo Pindaro
Sent: 31 March 2011 09:19
To: scala-user
Subject: [scala-user] Re: problem with eclipse plugin?

Learning an other IDE doesn't look me attractive..

I am going to try beta 2.0 eclipse plugin version hoping perform
better..

I any case i will submit bug to Scala org.

I agree that support for eclipse could be the edge beetwen a large
adoption in real world and an amazingand powrfull language for nerds?

Cheers
Olindo

On 30 Mar, 21:10, HamsterofDeath wrote:
> i'd go for idea right now, but i'm biased. but that's only because idea
> is better :)
> i suggest giving every ide a change every once in a while to see if they
> improved, i regularly check eclipse and netbeans. kepps you from
> becoming a "i only use what i know"-type
>
> Am 30.03.2011 20:49, schrieb Kenneth McDonald:
>
>
>
>
>
>
>
> > Olindo,
>
> > The Eclipse plug-in is coming along well, but it is still very much a WIP, as far as I can see. If you're willing to go to the effort of learning the basics of another IDE, the IntelliJ IDEA Community Edition works pretty well. It has its own problems, but as of the most recent "stable" version of Eclipse, it is significantly more useable than Eclipse, IMHO. If your goal right now is to learn Scala and start using it, that's the route I'd recommend. Then when you're more familiar with the language, you can shift back to the Eclipse environment, and you'll be in a better position to figure out what is a Scala problem and what is an Eclipse problem.
>
> > If you do decide to try IDEA and also want to use SBT (which I'd recommend if you're just in a learning phase), you'll probably want to use two third-party plugins, somewhat confusingly named "idea-sbt-plugin" and "sbt-idea-plugin" (in addition to enabling IDEA's own Scala support). You can find docs on these through a Google search.
>
> > I hope this doesn't come across as me dissing the Eclipse Scala plugin. Given the ubiquity of Eclipse, I think that Eclipse support is absolutely vital for Scala's success, and I'm really glad to see the progress that is being made in that direction. I simply think that, for a newcomer _at the moment_, trying to get into Scala via Eclipse can be a little frustrating.
>
> > Cheers,
> > Ken
>
> > On Mar 30, 2011, at 11:06 AM, Olindo Pindaro wrote:
>
> >> I configurated my Helios using plugin with scala 2.8.
>
> >> it slow in compilation (but Odersky declared that incremental
> >> compilation is not implemented).
>
> >> But it shows some oddities growing the size of code in a project.
>
> >> 1) package must must be organized as directory as Java
> >> 2) Sometime some classes required import to use other classes in some
> >> package (and directory)
> >> 3) Import at 2) report me a warning of "not necessary" import
> >> 4) Int.toByte or Int.asInstanceofByte[Byte] give me compilation error,
> >> the same snippet in an other (small) scala projects  works fine.
>
> >> i am a little discoraged even if I am a newbe and is hard to
> >> understand what is a my fualt and what is plug-in bug.
>
> >> Other experiences?
> >> Suggestion.
>
> >> Thank to all.

The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed, to persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS do not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW

learning another xyz is what would make you pretty unique, many people stick with the one they learned first, become attached to it, and the next step is becoming a biased fanboy ;)

-------- Original-Nachricht --------
> Datum: Thu, 31 Mar 2011 01:19:29 -0700 (PDT)
> Von: Olindo Pindaro
> An: scala-user
> Betreff: [scala-user] Re: problem with eclipse plugin?

> Learning an other IDE doesn't look me attractive..
>
> I am going to try beta 2.0 eclipse plugin version hoping perform
> better..
>
> I any case i will submit bug to Scala org.
>
> I agree that support for eclipse could be the edge beetwen a large
> adoption in real world and an amazingand powrfull language for nerds?
>
> Cheers
> Olindo
>
>
>
>
>
>
> On 30 Mar, 21:10, HamsterofDeath wrote:
> > i'd go for idea right now, but i'm biased. but that's only because idea
> > is better :)
> > i suggest giving every ide a change every once in a while to see if they
> > improved, i regularly check eclipse and netbeans. kepps you from
> > becoming a "i only use what i know"-type
> >
> > Am 30.03.2011 20:49, schrieb Kenneth McDonald:
> >
> >
> >
> >
> >
> >
> >
> > > Olindo,
> >
> > > The Eclipse plug-in is coming along well, but it is still very much a
> WIP, as far as I can see. If you're willing to go to the effort of learning
> the basics of another IDE, the IntelliJ IDEA Community Edition works
> pretty well. It has its own problems, but as of the most recent "stable" version
> of Eclipse, it is significantly more useable than Eclipse, IMHO. If your
> goal right now is to learn Scala and start using it, that's the route I'd
> recommend. Then when you're more familiar with the language, you can shift
> back to the Eclipse environment, and you'll be in a better position to figure
> out what is a Scala problem and what is an Eclipse problem.
> >
> > > If you do decide to try IDEA and also want to use SBT (which I'd
> recommend if you're just in a learning phase), you'll probably want to use two
> third-party plugins, somewhat confusingly named "idea-sbt-plugin" and
> "sbt-idea-plugin" (in addition to enabling IDEA's own Scala support). You can
> find docs on these through a Google search.
> >
> > > I hope this doesn't come across as me dissing the Eclipse Scala
> plugin. Given the ubiquity of Eclipse, I think that Eclipse support is absolutely
> vital for Scala's success, and I'm really glad to see the progress that is
> being made in that direction. I simply think that, for a newcomer _at the
> moment_, trying to get into Scala via Eclipse can be a little frustrating.
> >
> > > Cheers,
> > > Ken
> >
> > > On Mar 30, 2011, at 11:06 AM, Olindo Pindaro wrote:
> >
> > >> I configurated my Helios using plugin with scala 2.8.
> >
> > >> it slow in compilation (but Odersky declared that incremental
> > >> compilation is not implemented).
> >
> > >> But it shows some oddities growing the size of code in a project.
> >
> > >> 1) package must must be organized as directory as Java
> > >> 2) Sometime some classes required import to use other classes in some
> > >> package (and directory)
> > >> 3) Import at 2) report me a warning of "not necessary" import
> > >> 4) Int.toByte or Int.asInstanceofByte[Byte] give me compilation
> error,
> > >> the same snippet in an other (small) scala projects  works fine.
> >
> > >> i am a little discoraged even if I am a newbe and is hard to
> > >> understand what is a my fualt and what is plug-in bug.
> >
> > >> Other experiences?
> > >> Suggestion.
> >
> > >> Thank to all.

On Thu, Mar 31, 2011 at 9:25 AM, Tommaso Galleri
wrote:
> I was
> using ItelliJ IDEA with SBT integration and Scala plugin. I have
> abandoned IDEA and replaced it with Eclipse Helios + Scala WIP 2.9.

How would you compare the two? Is it a multi-module project or a single project?

Best,
Ismael

@Dennis,

I am 50 years old and during my entire life I learned "another xyz",
some of them totally useless.

My years are ending, my mind is limited, the Knowledge is infinite,
so i need the filter the "next xyz".

So ok learning Scala, ko a new ide (if nobody pay me for that)

Cheers
Olindo

On 31 Mar, 10:47, "Dennis Haupt" wrote:
> learning another xyz is what would make you pretty unique, many people stick with the one they learned first, become attached to it, and the next step is becoming a biased fanboy ;)
>

It's got a dozen "modules" with dependencies between then. It's got
around 150 scala files and a dozen java files. The only files WIP is
struggling a bit with are the ones generated by ScalaXB as these are
very large.

What I like about Eclipse WIP 2.9 is better navigation, better tooltips
when hovering, and most importantly immediate feedback when something
just typed does not compile.

IDEA with SBT was better for a few other things. It never stopped for
~10 seconds (every so often, even with WIP, luckily not frequently, you
type something and then everything hangs for ~10 seconds). It uses same
compiler/build-tool that's used by real build (SBT with 2.8.1). It does
not suffer from a few minor bugs in WIP (which in my case are not a big
issue: For example some constant annotations are reported to be
non-constant and are "underlined" as error (but no problem reported in
Problems tab!), but everything runs fine, so it's just a nuisance for
the eyes).
Also IDEA was less memory hungry.

Overall, I feel I am already slightly more productive on Eclipse + WIP,
hence the move. I understand I am an early adopter and this carries its
own risks; but it's only going to get better week after week. (if not I
can still move to IDEA as a fallback plan).

Certainly, WIP is a huge improvement over the standard 2.8 plugin that
could not handle anything larger than a couple of files and even then
sometimes it struggled.

On a final note, I am a lot more familiar with Eclipse, I do not have
any problem with IntelliJ IDEA, which I also like, but given two equally
good plugins, I would choose the Eclipse one.

Tommaso

-----Original Message-----
From: ismaelj@gmail.com [mailto:ismaelj@gmail.com] On Behalf Of Ismael
Juma
Sent: 31 March 2011 13:11
To: Tommaso Galleri
Cc: Olindo Pindaro; scala-user
Subject: Re: [scala-user] problem with eclipse plugin?

On Thu, Mar 31, 2011 at 9:25 AM, Tommaso Galleri
wrote:
> I was
> using ItelliJ IDEA with SBT integration and Scala plugin. I have
> abandoned IDEA and replaced it with Eclipse Helios + Scala WIP 2.9.

How would you compare the two? Is it a multi-module project or a single
project?

Best,
Ismael

The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed, to persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS do not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW

not sure that SBT is needed, I personally have great success defining
project in maven and using scala plugin for maven.

mvn scala:cc

keep all my classes compiled all the time, and is quite faster than
compiling them from withing an IDE (even in IntelliJ - which is THE
ide to use for scala IMO)

then using maven shell and executing unit tests without compilation
steps makes for very quick dev cycles

mvn surefire:test -Dtest=SomeServiceSpec

and lastly, if your application is web application written in scala
and running in a web container then enabling JRebel (free for Scala
and great for productivity) makes development as dynamic as with PHP.
I personally work this way with Wicket framework and I love it.
export JREBELHOME=$HOME/java/lib/ZeroTurnaround/jrebel-3.6.1
export MAVEN_OPTS="$MAVEN_OPTS -noverify -javaagent:$JREBELHOME/
jrebel.jar"
export JREBEL_MAVEN_OPTS=$MAVEN_OPTS

mvn jetty:run

Almost reached a nirvana ;)

On Mar 31, 8:11 am, Ismael Juma wrote:
> On Thu, Mar 31, 2011 at 9:25 AM, Tommaso Galleri
>
> wrote:
> > I was
> > using ItelliJ IDEA with SBT integration and Scala plugin. I have
> > abandoned IDEA and replaced it with Eclipse Helios + Scala WIP 2.9.
>
> How would you compare the two? Is it a multi-module project or a single project?
>
> Best,
> Ismael

On Thu, Mar 31, 2011 at 4:58 PM, kgignatyev wrote:
> not sure that SBT is needed, I personally have great success defining
> project in maven and using scala plugin for maven.

Everything that you describe can be done with SBT in a nicer way in my
opinion (as someone who moved from Maven to SBT).

Best,
Ismael

maybe, IMO:
- maven is 'standard' tool that is accepted by many developers so it lessens a barrier for people to try using Scala;
- IDE-s understand POMs and can open project defined in POM right away, that if I add dependency it is immediately picked up by IDE (all the niceties of code completion, navigation, browse sources etc);
- Maven has more plugins, than SBT that I already use or might need to use;

To summarize, SBT might be better tool for something, but Maven wins in terms of mindshare. Use of different language alienates fellow developers enough, I personally do not want them to learn more new things than necessary _just to get started_

It is like IntelliJ vs. Eclipse: IntelliJ is vastly superior IDE, but _require_ it to get started with Scala creates barrier of entry for many developers, therefore to promote Scala we need the plugin for Eclipse.

And having POM as project definition makes it totally painless to switch between IDE-s, or have some developers using IntelliJ and some Eclipse

On Thu, Mar 31, 2011 at 9:06 AM, Ismael Juma <ismael@juma.me.uk> wrote:

On Thu, Mar 31, 2011 at 4:58 PM, kgignatyev <kgignatyev@gmail.com> wrote:
> not sure that SBT is needed, I personally have great success defining
> project in maven and using scala plugin for maven.

Everything that you describe can be done with SBT in a nicer way in my
opinion (as someone who moved from Maven to SBT).

Best,
Ismael

--
Konstantin Ignatyev
 
PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000
 
Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206)

Hi Konstantin,

On Thu, Mar 31, 2011 at 5:18 PM, Konstantin Ignatyev
wrote:
> - maven is 'standard' tool that is accepted by many developers so it lessens
> a barrier for people to try using Scala;

Sure. If using Maven makes it easier for you to use Scala, please go ahead.

> - IDE-s understand POMs and can open project defined in POM right away, that
> if I add dependency it is immediately picked up by IDE (all the niceties of
> code completion, navigation, browse sources etc);

If you're using IDEA, I'd say that sbt-idea does a sufficiently good
job that this is not much of an advantage (again the main project I
work on has both Maven and SBT build files and I've used the Maven
support and sbt-idea and I prefer the latter for a multi-module build
that relies on continuous compilation as it configures things better
if you want to run and debug from IDEA).

> - Maven has more plugins, than SBT that I already use or might need to use;

If you need the plugins, yes.

> To summarize, SBT might be better tool for something, but Maven wins in
> terms of mindshare. Use of different language alienates fellow developers
> enough, I personally do not want them to learn more new things than
> necessary _just to get started_

I don't think there's a right or wrong answer here. If someone is
willing to learn a new language, maybe they're also willing to learn a
build system that is suited to the language. Or maybe they aren't.
Both are valid choices depending on your circumstances. Your original
email didn't focus on this aspect, it focused on some features as if
they were specific to Maven when in fact SBT has better support for
them. And my reply just made that clear.

> It is like IntelliJ vs. Eclipse: IntelliJ is vastly superior IDE, but
> _require_ it to get started with Scala creates barrier of entry for many
> developers, therefore to promote Scala we need the plugin for Eclipse.

I am not convinced that IntelliJ is a vastly superior IDE in general,
but it's certainly better for Scala at the moment. The gap is
narrowing though.

> And having POM as project definition makes it totally painless to switch
> between IDE-s, or have some developers using IntelliJ and some Eclipse

I haven't used Eclipse in a few months, but I expect its support for
SBT to be as good as IDEA's soon in case it isn't yet:

https://github.com/musk/SbtEclipsify
http://hseeberger.wordpress.com/2011/03/31/sbt-eclipse-integration/

Anyway, it's definitely good to have options.

Best,
Ismael

It looks as though SBT might be getting more official support from Scala...
The team working on WIP eclipse plugin, lead by Martin Odersky has, among many other goals:

"The current build manager ... it's beeing phased out towards an SBT-based build manager."
"Use SBT for tracking builds. SBT does a lot more than just dependency tracking. Ideally, SBT integration should provide more than just build management."
"- import an existing SBT project in Eclipse"
"- edit SBT project ..."
"- export existing Scala projects to SBT"
[https://lampsvn.epfl.ch/trac/scala/wiki/NewIDE]

For now, I have used eclipsify SBT plugin, but looks as though we are going to get something more official (and hopefully more complete too).

I agree with you, SBT is yet again one more thing to learn and if you are happy with maven and/or need something that maven offers and SBT yet does not, then it makes sense to use Maven.

Personally, I think build tools are just build tools. However, I like the idea to have a build tool based on an expressive programming language rather than XML... (in fact I have always hated Ant for this very reason!). So, that's why I am using SBT instead of Ant or Maven, also, for what I do, SBT is sufficient. One wish though: better documentation for SBT.

I know current version of SBT is quite old (and is run with an old version of scala), and there is a 0.9 being developed. I might give it a go one day.

Tommaso

-----Original Message-----
From: scala-user@googlegroups.com [mailto:scala-user@googlegroups.com] On Behalf Of kgignatyev
Sent: 31 March 2011 16:58
To: scala-user
Subject: [scala-user] Re: problem with eclipse plugin?

not sure that SBT is needed, I personally have great success defining
project in maven and using scala plugin for maven.

mvn scala:cc

keep all my classes compiled all the time, and is quite faster than
compiling them from withing an IDE (even in IntelliJ - which is THE
ide to use for scala IMO)

then using maven shell and executing unit tests without compilation
steps makes for very quick dev cycles

mvn surefire:test -Dtest=SomeServiceSpec

and lastly, if your application is web application written in scala
and running in a web container then enabling JRebel (free for Scala
and great for productivity) makes development as dynamic as with PHP.
I personally work this way with Wicket framework and I love it.
export JREBELHOME=$HOME/java/lib/ZeroTurnaround/jrebel-3.6.1
export MAVEN_OPTS="$MAVEN_OPTS -noverify -javaagent:$JREBELHOME/
jrebel.jar"
export JREBEL_MAVEN_OPTS=$MAVEN_OPTS

mvn jetty:run

Almost reached a nirvana ;)

On Mar 31, 8:11 am, Ismael Juma wrote:
> On Thu, Mar 31, 2011 at 9:25 AM, Tommaso Galleri
>
> wrote:
> > I was
> > using ItelliJ IDEA with SBT integration and Scala plugin. I have
> > abandoned IDEA and replaced it with Eclipse Helios + Scala WIP 2.9.
>
> How would you compare the two? Is it a multi-module project or a single project?
>
> Best,
> Ismael

The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed, to persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS do not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW

On Thu, Mar 31, 2011 at 5:58 PM, Tommaso Galleri
wrote:
> I know current version of SBT is quite old (and is run with an old version of scala), and there is a 0.9 being developed. I might give it a go one day.

SBT 0.9.x is a development series. 0.10.0 will be stable. I would not
recommend trying 0.9.x before 0.9.4 or 0.9.5 if you want a polished
experience.

Best,
Ismael

Am 31.03.2011 18:18, schrieb Konstantin Ignatyev:

HSYE7VuTt-+w7_RGmpGoqGLfNs-G_8YFOV [at] mail [dot] gmail [dot] com" type="cite">maybe, IMO:
- maven is 'standard' tool that is accepted by many developers so it lessens a barrier for people to try using Scala;
- IDE-s understand POMs and can open project defined in POM right away, that if I add dependency it is immediately picked up by IDE (all the niceties of code completion, navigation, browse sources etc);
- Maven has more plugins, than SBT that I already use or might need to use;

To summarize, SBT might be better tool for something, but Maven wins in terms of mindshare. Use of different language alienates fellow developers enough, I personally do not want them to learn more new things than necessary _just to get started_

It is like IntelliJ vs. Eclipse: IntelliJ is vastly superior IDE, but _require_ it to get started with Scala creates barrier of entry for many developers, therefore to promote Scala we need the plugin for Eclipse.

where is the barrier? there's a free edition of idea

HSYE7VuTt-+w7_RGmpGoqGLfNs-G_8YFOV [at] mail [dot] gmail [dot] com" type="cite">
And having POM as project definition makes it totally painless to switch between IDE-s, or have some developers using IntelliJ and some Eclipse

On Thu, Mar 31, 2011 at 9:06 AM, Ismael Juma <ismael [at] juma [dot] me [dot] uk" rel="nofollow">ismael@juma.me.uk> wrote:

On Thu, Mar 31, 2011 at 4:58 PM, kgignatyev <kgignatyev [at] gmail [dot] com" rel="nofollow">kgignatyev@gmail.com> wrote:
> not sure that SBT is needed, I personally have great success defining
> project in maven and using scala plugin for maven.

Everything that you describe can be done with SBT in a nicer way in my
opinion (as someone who moved from Maven to SBT).

Best,
Ismael

--
Konstantin Ignatyev
 
PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000
 
Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206)

I'm surprised so many people like Intellij for Scala programming, I tried it and I felt it unusable. Code completion did nothing useful for me.

From Eclipse, Idea, and Netbeans I choose Netbeans. Ensime seemed great but I'm not too comfortable yet with Emacs.

Netbeans does not have SBT integration so Maven it is. It works just fine and does not tie me to Netbeans. SBT is great but for the time being I feel Maven has much more stuff right now making it easier to integrate into the rest of the projects that may not be coded in Scala or are half Scala - half Java.

(I'm not sure how the maven archetype is defined right now but I found in the past that it wasn't using the fsc properly.)

So... at least consider Netbeans even if so many people like other stuff

On Thu, Mar 31, 2011 at 2:17 PM, HamsterofDeath <h-star@gmx.de> wrote:

Am 31.03.2011 18:18, schrieb Konstantin Ignatyev:

maybe, IMO:
- maven is 'standard' tool that is accepted by many developers so it lessens a barrier for people to try using Scala;
- IDE-s understand POMs and can open project defined in POM right away, that if I add dependency it is immediately picked up by IDE (all the niceties of code completion, navigation, browse sources etc);
- Maven has more plugins, than SBT that I already use or might need to use;

To summarize, SBT might be better tool for something, but Maven wins in terms of mindshare. Use of different language alienates fellow developers enough, I personally do not want them to learn more new things than necessary _just to get started_

It is like IntelliJ vs. Eclipse: IntelliJ is vastly superior IDE, but _require_ it to get started with Scala creates barrier of entry for many developers, therefore to promote Scala we need the plugin for Eclipse.

where is the barrier? there's a free edition of idea

And having POM as project definition makes it totally painless to switch between IDE-s, or have some developers using IntelliJ and some Eclipse

On Thu, Mar 31, 2011 at 9:06 AM, Ismael Juma <ismael@juma.me.uk> wrote:

On Thu, Mar 31, 2011 at 4:58 PM, kgignatyev <kgignatyev@gmail.com> wrote:
> not sure that SBT is needed, I personally have great success defining
> project in maven and using scala plugin for maven.

Everything that you describe can be done with SBT in a nicer way in my
opinion (as someone who moved from Maven to SBT).

Best,
Ismael

--
Konstantin Ignatyev
 
PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000
 
Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206)

just wanted to squash this as it came up on a blog the other day as well...

On Thu, Mar 31, 2011 at 6:58 PM, Tommaso Galleri
wrote:
>
>
> I know current version of SBT is quite old (and is run with an old version of scala), and there is a 0.9 being developed. I might give it a go one day.
>
>

Its not old, and definitely not "quite old", but it stems from a time
where 2.7.7 being more used then 2.8.0. Whilst SBT itself is run with
an old version of Scala it allows the use of more recent scala
versions for both development exploration (via console / test) and
building. Only SBT plugins must be in 2.7.7 but thats hardly a
hardship, and is only ever seen when writing SBT plugins.

0.7.6 is around the corner as well, maintaining compatibility with the
other 0.7.x sbt versions.

I'm sure you know all of this but I want to make sure others searching
also get the right idea.

I've made a number of plugins - will shortly release them - that are
based around 0.7.4 and its been a very quick experience, even when
working in 2.7.7. But working with SBT 0.7.4 and 2.8.1 (plus ensime)
has been like an extremely productive dream. (I was also a fond user
of Seans eclipse plugin, only froze on me once and had a far lower
memory consumption then the last more public plugins).

Hi Chris,

I use SBT sometimes but I'm not sure how well it integrates with other Java projects.

Can it replace Maven? What are your thoughts on that? Perhaps it's another instance of misinformation?

Thanks!

On Thu, Mar 31, 2011 at 3:15 PM, Chris Twiner <chris.twiner@gmail.com> wrote:

just wanted to squash this as it came up on a blog the other day as well...

On Thu, Mar 31, 2011 at 6:58 PM, Tommaso Galleri
<Tommaso.Galleri@bjss.com> wrote:
>
>
> I know current version of SBT is quite old (and is run with an old version of scala), and there is a 0.9 being developed. I might give it a go one day.
>
>

Its not old, and definitely not "quite old", but it stems from a time
where 2.7.7 being more used then 2.8.0.  Whilst SBT itself is run with
an old version of Scala it allows the use of more recent scala
versions for both development exploration (via console / test) and
building.  Only SBT plugins must be in 2.7.7 but thats hardly a
hardship, and is only ever seen when writing SBT plugins.

0.7.6 is around the corner as well, maintaining compatibility with the
other 0.7.x sbt versions.

I'm sure you know all of this but I want to make sure others searching
also get the right idea.

I've made a number of plugins - will shortly release them - that are
based around 0.7.4 and its been a very quick experience, even when
working in 2.7.7.  But working with SBT 0.7.4 and 2.8.1 (plus ensime)
has been like an extremely productive dream.  (I was also a fond user
of Seans eclipse plugin, only froze on me once and had a far lower
memory consumption then the last more public plugins).

Honestly I don't think it can yet, as many have pointed out there is a
huge infrastructure behind Maven.

Maven gives alot, but things like the project version not being a
variable (you can't change it in your top most parent project and have
it all trickle down - thats what the release plugin is meant to do) or
the original everything including the build system updates are updated
by default, leave a sour taste in the mouth for many.

In my personal scala sbt projects I found I missed a simple site:site,
so I made something similar (the plugins I spoke of), although of
course not as polished. I've made the decision that the plugin and its
"skins" are bound together and that only the project can override that
skin. Maven 2x site loves to try to download skins, oops java.net
moved them and now our skins in the repo contain redirect html. My
unpleasent and timewasting experiences with Maven allowed me to write
that particular part better....

Hindsight and experience of the pain points of Ant / Maven / Make etc
is what allows build tool makers like sbt / gradle / rake etc to do
such a good job. Its also of course what enables the Maven 3 > 2 > 1.

Best answer I have therefore is - where is the sbt clover plugin?
Doesn't exist of course (possibly just a .."yet"), where is the sonar
plugin ? Same deal, and these kind of infrastructure things make sbt
pretty hard to justify against maven in the enterprise. I'm really
hoping its just a question of time though.

2011/3/31 Tomás Lázaro :
> Hi Chris,
>
> I use SBT sometimes but I'm not sure how well it integrates with other Java
> projects.
>
> Can it replace Maven? What are your thoughts on that? Perhaps it's another
> instance of misinformation?
>
> Thanks!
>
> On Thu, Mar 31, 2011 at 3:15 PM, Chris Twiner
> wrote:
>>
>> just wanted to squash this as it came up on a blog the other day as
>> well...
>>
>> On Thu, Mar 31, 2011 at 6:58 PM, Tommaso Galleri
>> wrote:
>> >
>> >
>> > I know current version of SBT is quite old (and is run with an old
>> > version of scala), and there is a 0.9 being developed. I might give it a go
>> > one day.
>> >
>> >
>>
>> Its not old, and definitely not "quite old", but it stems from a time
>> where 2.7.7 being more used then 2.8.0.  Whilst SBT itself is run with
>> an old version of Scala it allows the use of more recent scala
>> versions for both development exploration (via console / test) and
>> building.  Only SBT plugins must be in 2.7.7 but thats hardly a
>> hardship, and is only ever seen when writing SBT plugins.
>>
>> 0.7.6 is around the corner as well, maintaining compatibility with the
>> other 0.7.x sbt versions.
>>
>> I'm sure you know all of this but I want to make sure others searching
>> also get the right idea.
>>
>> I've made a number of plugins - will shortly release them - that are
>> based around 0.7.4 and its been a very quick experience, even when
>> working in 2.7.7.  But working with SBT 0.7.4 and 2.8.1 (plus ensime)
>> has been like an extremely productive dream.  (I was also a fond user
>> of Seans eclipse plugin, only froze on me once and had a far lower
>> memory consumption then the last more public plugins).
>
>

Hi
On Thu, Mar 31, 2011 at 5:25 AM, Tommaso Galleri <Tommaso.Galleri@bjss.com> wrote:

I recommend changing/adding lines to eclipse.ini to make sure you have:

--launcher.XXMaxPermSize
256m
-vmargs
-server
-XX:+DoEscapeAnalysis
-XX:+CMSClassUnloadingEnabled
-Xms600m
-Xmx1500m  (or more)

Does anyone have a better or more official set of eclipse.ini
parameters?

Maybe this:https://www.assembla.com/wiki/show/scala-ide/Setup
In resume, if you have enough memory and a recent Java version it recomends this configuration:
--launcher.XXMaxPermSize
256m
-vmargs
-Xms256m
-Xmx2048m
-XX:PermSize=64m
-Xss1M
-server
-XX:+DoEscapeAnalysis-XX:+UseConcMarkSweepGC
-XX:+UseCompressedOops (this one only for 64 bit JVM)

Regards,Germán