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
Unless it is not possible for some reason I can't think of, conscript should provide a bridge launch class that invokes the main method on a given class.
The text was updated successfully, but these errors were encountered:
Given that the dependencies still need to be pulled and classpath needs to be configured, we can't just call java -jar against the app's jar. Would that mean we need to implement an equivalent of sbt run with project/build/project.scala point at the app? A quick way may be to fork sbt and add another param to emulate that.
What I was thinking here is that it's easier for some people to implement a main class, since it's a familiar interface, and we could just invoke the main method from a regular launcher.
But in testing the installer that you made for conscript, I realized it can be very handy (as it is much faster) to run and test things from within their own project, instead of going through the cs-run action each time. And then there's the possibility of an aggregate, runnable jar.
It would be cool if conscript apps got these options for free, and it would be their choice to implement the launcher interface or a designated main method. But, this all seems less important than getting your changes out the door. My main hold up there is I need to decide about webstart for the installer.
Unless it is not possible for some reason I can't think of, conscript should provide a bridge launch class that invokes the main method on a given class.
The text was updated successfully, but these errors were encountered: