Closed knuton closed 11 years ago
Sorry for major delay in answering. I noticed this during my vacation but then couldn't answer. And then I forgot.
I wrote this just as a hobby while learning Play Framework, and don't have any roadmap as such for the plugin. I have nothing against publishing it in some repository thought, and publishing to Sonatype would be a learning experience, so could try to do it soonish. I have some not yet pushed changes pending on testing to support incrementalAssetsCompilation, but after that I could try to push 0.1.1 to Sonatype.
Great, thanks!
Finally published 0.1.3 to Sonatype OSS repository.
Thanks! :ok_hand:
I am currently in the process of handing play-stylus over to my employer’s account, @patiencelabs. As part of the transfer I am also going to publish the latest version of play-stylus to our package repository to allow people using the plugin to properly cache the artifact in their repository proxy.
We actually switched to Sass a while ago ourselves, though, and are now using your plugin. (I was so pleased to find your plugin when contemplating the switch!) So I would be interested in giving play-sass the same treatment for more standard dependency management.
Do you have any intention to publish it to a repository of your own, Sonatype, or another central repository?
sbt has a guide for publishing to Sonatype. I would be interested in working on this, too, in case it doesn’t fit your roadmap.