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
{{ message }}
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.
Is there a way to configure 'ibazel_notify_changes'?
Currently ibazel can be configured that the Binary is only notified for File Changes and does not restart on it's own. I'm currently looking in creating a small launcher for Playframework and I try to actually only rebuild my bazel target if a file changes and just try to swap the Classpath, as Play does with sbt.
The text was updated successfully, but these errors were encountered:
Hi @schmitch. I'm not sure I understand. Rebazel will by default watch for changes to the input files a target depends on and retriggers an action when they change. What would you like to see in addition to that?
i.e. if I call ibazel run //:mytarget and the target has a label called ibazel_notify_changes
than ibazel will rebuild the target but not restart the target i.e. consider a java programm:
it will only print "Hello World!" and if I edit it to "Hello NAME!" it won't print "Hello NAME!" instead it will actually just rebuild the java source file to a new jar and than it will send "BUILD COMPLETED" to the stdin of the current program.
So basically a Java Program could listen via new BufferedReader(new InputStreamReader(System.in)) to new input and if a input comes in it could just reload the ClassLoader, so it could actually Hot Reload a Webserver.
Is there a way to configure 'ibazel_notify_changes'?
Currently ibazel can be configured that the Binary is only notified for File Changes and does not restart on it's own. I'm currently looking in creating a small launcher for Playframework and I try to actually only rebuild my bazel target if a file changes and just try to swap the Classpath, as Play does with
sbt
.The text was updated successfully, but these errors were encountered: