-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
work around invalid component injector in m2e-1.8 #1
Comments
|
OK, here is logs.zip, which includes my current pom.xml, the Maven console output, and the stacktrace taken from the resulting alert. Thanks for the new plugin, which I'm very excited about, and for looking into this! |
thanks - from zips it looks like I depend on wrong version of M2E (you use 1.8 (?) vs I use 1.9) please attach zip (with sanitized system properties) eclipse config (so I can verify your plugin versions):
|
You're exactly right: I use 1.8.2, and in fact can't find a "1.9" anywhere. Here is |
thanks, now I can reproduce problem 100% |
|
With the latest plugin, updating my Maven settings gets me this Maven console:
I think it's correct. In particular, I have Thanks again! I think you can close this ticket, as the bug has clearly been fixed; the rest is just a gap in my understanding. |
|
It also builds fine with Maven 3.5.2 and m2e 1.9, so I think it's good. I'm still confused by one thing, though. If I have this source code: package tutorial.webapp
object TutorialApp {
def main(args: Array[String]): Unit = {
println("Hello world!")
}
} shouldn't I then be able to say: node runtime.js in the
in the console? Thanks so much! |
sure, as long as you export |
No dice. Here's my source code now: package tutorial.webapp
import scala.scalajs.js.annotation._
@JSExportTopLevel("TutorialApp")
object TutorialApp {
@JSExport
def main(args: Array[String]): Unit = {
println("Hello world!")
}
} but
still produces nothing: ⇒ node runtime.js
psnively@Ragnarok:~/eclipse-workspace/invest/target/classes/META-INF/resources/script|
⇒ I think there's something I'm still missing about how to specify that Update: I think we need the equivalent of |
right. |
OK, but... this seems kind of fundamental, right? It seems like the So I guess my immediate question is: what do I need to do to actually build a runnable JavaScript application with this plugin? This is admittedly mostly for validation purposes, as I do ultimately expect to be browser-based rather than standalone. I'm just trying to get from "Hello, world" to that point incrementally. |
a) try to run it with
b) or, skip the |
Understood, hence my comment about maybe wanting to support something like sbt's Now, you can certainly observe (and I could easily understand) that's specific to the sbt plugin and is out of scope for what you're trying to achieve. But you did encourage me to keep spelling out my wish list. :-) |
sure, you will have some form of |
In the meantime: psnively@Ragnarok:~|⇒ node -e 'require("/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js"); TutorialApp.main()'
/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:213
throw new $c_sjsr_UndefinedBehaviorError().init___jl_Throwable(
^
Error
at $c_sjsr_UndefinedBehaviorError.$c_jl_Throwable.fillInStackTrace__jl_Throwable (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:1738:14)
at $c_sjsr_UndefinedBehaviorError.fillInStackTrace__jl_Throwable (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:2756:67)
at $c_sjsr_UndefinedBehaviorError.$c_jl_Throwable.init___T__jl_Throwable (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:1754:8)
at $c_sjsr_UndefinedBehaviorError.init___T__jl_Throwable (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:2763:52)
at $c_sjsr_UndefinedBehaviorError.init___jl_Throwable (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:2759:67)
at $throwClassCastException (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:213:46)
at $throwArrayCastException (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:222:3)
at $asArrayOf_T (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:2289:64)
at $c_Ltutorial_webapp_TutorialApp$.main (/Users/psnively/eclipse-workspace/invest/target/classes/META-INF/resources/script/runtime.js:1153:15)
at [eval]:1:118 So the good news is the export annotations are working, compiling is working, and linking is working. But there's apparently still something I'm misunderstanding about how to actually use the result. |
great. |
please try 1.1.0 release use demo project as reference |
assume resolved |
@PaulAtBanno FYI: Scala.js module initializes are now supported: |
Creating a simple Maven project with the following pom.xml exhibits the above error when updating the project settings:
Replacing the new project's pom.xml rightly presents the issue that the project's settings need updating. Doing so, however, results in the error in the subject.
The text was updated successfully, but these errors were encountered: