#1000119
- Created on2010-08-19 00:56
- Reported by
- StatusFixed
- PriorityHigh (2)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
ClassNotFoundException trying to run scala app in Helios
When I attempt to run a Scala app from an object with a def main(args:Array[String]) I get a java.lang.ClassNotFoundException: scala.ScalaObject. I verified that the Scala library is on the build and the runtime bootstrap classpath. I had no trouble running scala apps in Galileo
Leave a comment
on 2010-08-19 01:09 *
By Michael Allman
I just noticed I can no longer run my scala app in Galileo either. I'm not sure what the problem is, but it may have to do with the fact that I'm now using org.scala-ide.sdt.launching.SCALA_CONTAINER whereas before I was using ch.epfl.lamp.sdt.launching.SCALA_CONTAINER.
on 2010-08-19 01:34 *
By
Can you create a trival hello world application and run it?
on 2010-08-19 01:49 *
By Michael Allman
That worked fine.
Turns out the problem is that you have to put the Scala Library before the JRE System Library on the project classpath. That's weird. Why might that be?
Thanks.
Turns out the problem is that you have to put the Scala Library before the JRE System Library on the project classpath. That's weird. Why might that be?
Thanks.
Updating tickets (#1000069, #1000195, #1000213, #1000223, #1000006, #1000021, #1000038, #1000048, #1000051, #1000052, #1000075, #1000103, #1000109, #1000115, #1000119, #1000156, #1000186, #1000207, #1000238, #1000262, #1000263, #380, #389, #683, #1238, #1331, #1635, #1645, #1715, #1729, #1744, #1783, #1839, #1869, #1885, #1890, #1902, #1918, #1919, #1924, #1925, #1946, #1964, #1991, #2131, #2233, #2342, #2348, #2408, #2459, #2499, #2523, #2572, #2582, #2602, #2614, #2615, #2675, #2710, #2745, #2763, #2816, #2830, #2834, #2878, #2879, #2887, #2888, #2901, #2911, #2912, #2922, #2937, #2938, #2942, #2951, #2955, #2957, #2961, #2964, #2965, #2974, #2975, #2989, #2990, #3002, #3055, #3070, #3087, #3135, #3139, #3173, #3182, #3184, #3200, #3213, #3214, #3221, #3243, #3251)
on 2011-03-24 18:18 *
By Iulian Dragos
Updating tickets (#1000199, #1000200, #1000201, #1000204, #1000205, #1000209, #1000210, #1000211, #1000212, #1000215, #1000217, #1000218, #1000220, #1000222, #1000226, #1000227, #1000228, #1000230, #1000231, #1000232, #1000233, #1000235, #1000236, #1000237, #1000239, #1000240, #1000241, #1000242, #1000243, #1000244, #1000248, #1000249, #1000252, #1000253, #1000254, #1000255, #1000256, #1000258, #1000259, #1000032, #1000059, #1000062, #1000163, #1000197, #1000216, #1000221, #1000224, #1000121, #1000175, #1000219, #1000251, #1000069, #1000195, #1000213, #1000223, #1000006, #1000021, #1000038, #1000048, #1000051, #1000052, #1000075, #1000103, #1000109, #1000115, #1000119, #1000156, #1000186, #1000207, #1000238, #1000262, #1000263, #380, #389, #683, #1238, #1331, #1635, #1645, #1715, #1729, #1744, #1783, #1839, #1869, #1885, #1890, #1902, #1918, #1919, #1924, #1925, #1946, #1964, #1991, #2131, #2233, #2342, #2348, #2408)
on 2011-03-25 11:50 *
By Hubert Plociniczak
Assigned to changed from login to Hubert Plociniczak
Status changed from New to Fixed
That really weird restriction is fixed in wip_experiment in fad98ccf8f6f73f4516b45556d980d2da2c7c62e.
on 2011-03-25 12:19 *
By David Bernard
The workaround is to check that in the classpath (of launcher) Scala-library container is in the boot before (above) JRE lib container
on 2011-03-25 12:54 *
By Hubert Plociniczak
Yeah, but actually requiring that from users is unrealistic. In reality one can spend easily a couple of hours staring at the monitor if you don't know what to look for.