You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I import into eclipse like this, Eclipse finds the shared folders, but it sets their output folders to the source folder. See (from .classpath in the JS project):
I don't know how sbt-eclipse decides what output path to default to when eclipseOutput is None, but at least in this case it's not the right thing.
This might, of course, be an issue on the ScalaJS plugin side, I don't know.
Edit: Sorry forgot to write versions:
sbt 0.13.12
sbteclipse 5.1.0
sbtscalajs 0.6.14
The text was updated successfully, but these errors were encountered:
There appears to be an issue with shared sources in ScalaJS crossProject builds with Eclipse.
Consider a standard setup of
If I import into eclipse like this, Eclipse finds the shared folders, but it sets their output folders to the source folder. See (from .classpath in the JS project):
When I set
eclipseOutput
manually to some other folder, it generates the correct output, as seen below.I don't know how sbt-eclipse decides what output path to default to when
eclipseOutput
isNone
, but at least in this case it's not the right thing.This might, of course, be an issue on the ScalaJS plugin side, I don't know.
Edit: Sorry forgot to write versions:
The text was updated successfully, but these errors were encountered: