{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/ae656076d40ae9c1314136e3c4caaf81?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"ae656076d40ae9c1314136e3c4caaf81","url":"https://api.github.com/users/dirkhusemann","login":"dirkhusemann","id":48989},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-11-08T14:38:32Z","closed_at":null,"comments":2,"url":"https://api.github.com/repos/siasia/xsbt-web-plugin/issues/52","body":"with the 0.1 web-plugin we change source code and do a \"prepare-webapp\" which would trigger a compile and then cause a \"jetty-reload\" (we had scanInterval set to 0). i'm trying to figure out how to accomplish the same with the 0.2 version of the plugin. \r\n\r\n**first attempt:**\r\nusing\r\n```scanDirectories in Compile := Null```\r\nwe start jetty:\r\n```container:start```\r\nchange some source code and then compile:\r\n```compile```\r\ncontainer is not restarted and an explicit \r\n```container:reload /```\r\nis necessary.\r\n\r\n**second attempt:**\r\nwe drop the \"scanDirectories\" directive, start jetty:\r\n```container:start```\r\nchange some source code and then compile:\r\n```compile```\r\ncontainer is **immediately restarted and then is restarted once more** as soon as the compilation is finished. \r\n\r\nhow do we get the old prepare-webapp behavior?\r\n","html_url":"https://github.com/siasia/xsbt-web-plugin/issues/52","title":"\"compile\" triggers an immediate restart of a running container","number":52,"id":2174634,"created_at":"2011-11-08T14:23:41Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/a4c46907011b58560a266b2fc8e7bf6a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"a4c46907011b58560a266b2fc8e7bf6a","url":"https://api.github.com/users/siasia","login":"siasia","id":38494},"updated_at":"2011-11-08T14:38:32Z","url":"https://api.github.com/repos/siasia/xsbt-web-plugin/issues/comments/2668113","body":"For now you can check if `~container:reload /` with empty scandirs works\nfor you.\n\n2011/11/8 Artyom Olshevskiy <siasiamail@gmail.com>\n\n> Yup, I saw this behaviour too. Looks like the class files for recompiled\n> sources are cleaned out before actual compilation. Which in turn triggers\n> the reload.\n>\n> I'll check this in a meantime.\n>\n>\n> 2011/11/8 Dirk Husemann <\n> reply@reply.github.com>\n>\n>> with the 0.1 web-plugin we change source code and do a \"prepare-webapp\"\n>> which would trigger a compile and then cause a \"jetty-reload\" (we had\n>> scanInterval set to 0). i'm trying to figure out how to accomplish the same\n>> with the 0.2 version of the plugin.\n>>\n>> *first attempt:*\n>> using\n>>    scanDirectories in Compile := Null\n>> we start jetty:\n>>    container:start\n>> change some source code and then compile:\n>>    compile\n>> container is not restarted and an explicit\n>>    container:reload /\n>> is necessary.\n>>\n>> *second attempt:*\n>> we drop the \"scanDirectories\" directive, start jetty:\n>>    container:start\n>> change some source code and then compile:\n>>    compile\n>> container is *immediately restarted and then is restarted once more* as\n>> soon as the compilation is finished.\n>>\n>> how do we get the old prepare-webapp behavior?\n>>\n>> ---\n>> Reply to this email directly or view it on GitHub:\n>> https://github.com/siasia/xsbt-web-plugin/issues/52\n>>\n>\n>","id":2668113,"created_at":"2011-11-08T14:38:32Z"}}