Closed lihaoyi closed 9 years ago
I don't currently plan to really publish the ScalaParser as a stand-alone entity to be used independently as I won't have any capacity to improve/maintain it. I regard it more as a "complex example".
How about publishing parboiled itself in its current state? I'd love to maintain/publish the scala parser but cannot rely on snapshots On Feb 17, 2015 11:18 PM, "Mathias" notifications@github.com wrote:
I don't currently plan to really publish the ScalaParser as a stand-alone entity to be used independently as I won't have any capacity to improve/maintain it. I regard it more as a "complex example".
— Reply to this email directly or view it on GitHub https://github.com/sirthias/parboiled2/issues/131#issuecomment-74683727.
Ok. I'll see what I can do. I might just publish 2.1.0 with more or less the current state in order to ship the fixes and improvements that are already in.
Ok, just published 2.1.0 to sonatype, should hit maven central soon.
Cool, thanks!
@alexander-myltsev any chance of a Scala.js release? ^_^
Sure, will make to as soon as I can.
@lihaoyi , https://github.com/alexander-myltsev/parboiled2/commits/scala-2.11-scalajs-0.6.x . sbt scalaParser/fastOptJS
does not pass. Please, take a look why.
@alexander-myltsev is this the error message you got?
[error] (parboiledCore/*:update) sbt.ResolveException: unresolved dependency: name.myltsev#shapeless_sjs0.6_2.11;2.1.0: not found
Seems pretty self-explanatory to me, unless I'm missing something obvious
Oops... Sure no. You should sbt publishLocal
that https://github.com/alexander-myltsev/shapeless/commits/shapeless-2.1.0-scalajs-0.6.x beforehand.
Any chance of publishing what we have right now both for Parboiled2 itself as well as the Scala parser? I'd like to use it and improve it, but it doesn't make sense to improve something (the parser) which will not be properly published/usable for the forseeable future.