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
Consider the build.sbt from scalajs-react-template. For the most part, it's just dependencies, and translating them to Maven using scalor-maven-plugin is straightforward.
There are basically at least three other concerns:
Settings such as packageJSDependencies. jsDependencies, etc.
Scoping those Settings per task, such as fastOptJS in Compile scope.
Providing some equivalent to Workbench for rapid iteration of Scala.js projects in Maven.
1 and 2 can probably be addressed with a Wiki page describing how the sbt plugin settings map to arguments in the scalor plugin. 3 might be addressed by using Eclipse and building on save, but it's not clear to me how scalor plugin settings are being reflected as Eclipse project settings such that e.g. an HTML page referring by relative path to the local compile target will be pointing to where the pom.xml says rather than whatever the default target path is after Eclipse imports a Maven project.
More generally, it would be nice if there were more standalone examples than the demo and the scalor-maven-plugin project itself, and ideally, if some of these examples were conversions of Scala.js projects in sbt, for comparison's sake.
The text was updated successfully, but these errors were encountered:
Consider the build.sbt from scalajs-react-template. For the most part, it's just dependencies, and translating them to Maven using scalor-maven-plugin is straightforward.
There are basically at least three other concerns:
packageJSDependencies
.jsDependencies
, etc.Settings
per task, such asfastOptJS
inCompile
scope.1 and 2 can probably be addressed with a Wiki page describing how the sbt plugin settings map to arguments in the scalor plugin. 3 might be addressed by using Eclipse and building on save, but it's not clear to me how scalor plugin settings are being reflected as Eclipse project settings such that e.g. an HTML page referring by relative path to the local compile target will be pointing to where the
pom.xml
says rather than whatever the default target path is after Eclipse imports a Maven project.More generally, it would be nice if there were more standalone examples than the
demo
and thescalor-maven-plugin
project itself, and ideally, if some of these examples were conversions of Scala.js projects in sbt, for comparison's sake.The text was updated successfully, but these errors were encountered: