publishing and retrieving plugins.

[Josh Cough]

I have a question about publishing plugins, and then using then. The short version of the problem is, I've published my plugin jar, but sbt isn't finding it.

Details follow:

I just created a new plugin (https://github.com/joshcough/ScalaMinecraftYmlGen) and published it to bintray using bintray-sbt (https://github.com/softprops/bintray-sbt/). 

My jar was published here: http://dl.bintray.com/joshcough/maven/jcdc/pluginfactory/scala-minecraft-yml-gen/0.3.1/scala-minecraft-yml-gen-0.3.1.jar

I then went to use that plugin from a different project, using this in my plugin.sbt:

resolvers += "joshcough bintray maven" at "http://dl.bintray.com/joshcough/maven/"

addSbtPlugin("jcdc.pluginfactory" % "scala-minecraft-yml-gen" % "0.3.1")

Unfortunately, sbt was unable to find the plugin. It said it trid here:  http://dl.bintray.com/joshcough/maven/jcdc/pluginfactory/scala-minecraft-yml-gen_2.10_0.13/0.3.1/scala-minecraft-yml-gen-0.3.1.pom, which is just slightly different from the location it was actually published. 

Basically, it was looking for scala-minecraft-yml-gen_2.10_0.13/0.3.1, but it was published at scala-minecraft-yml-gen/0.3.1. It looks like the '_2.10_0.13' was left off when I published my plugin. Does anyone have any idea why that might be?

Thanks.

-Josh

[Doug Tangren]

On Wed, Jul 31, 2013 at 4:58 PM, Josh Cough <josh...@gmail.com> wrote:

I have a question about publishing plugins, and then using then. The short version of the problem is, I've published my plugin jar, but sbt isn't finding it.

Details follow:

I just created a new plugin (https://github.com/joshcough/ScalaMinecraftYmlGen) and published it to bintray using bintray-sbt (https://github.com/softprops/bintray-sbt/). 

My jar was published here: http://dl.bintray.com/joshcough/maven/jcdc/pluginfactory/scala-minecraft-yml-gen/0.3.1/scala-minecraft-yml-gen-0.3.1.jar

I then went to use that plugin from a different project, using this in my plugin.sbt:

resolvers += "joshcough bintray maven" at "http://dl.bintray.com/joshcough/maven/"

addSbtPlugin("jcdc.pluginfactory" % "scala-minecraft-yml-gen" % "0.3.1")

Unfortunately, sbt was unable to find the plugin. It said it trid here:  http://dl.bintray.com/joshcough/maven/jcdc/pluginfactory/scala-minecraft-yml-gen_2.10_0.13/0.3.1/scala-minecraft-yml-gen-0.3.1.pom, which is just slightly different from the location it was actually published. 

dl.bintray.com is the cdn for bintray packages. I see your pom here: 

http://dl.bintray.com/joshcough/maven/jcdc/pluginfactory/scala-minecraft-yml-gen/0.3.1

 

Basically, it was looking for scala-minecraft-yml-gen_2.10_0.13/0.3.1, but it was published at scala-minecraft-yml-gen/0.3.1. It looks like the '_2.10_0.13' was left off when I published my plugin. Does anyone have any idea why that might be?

This may be my plugins doing. Can you post another gh issue for my plugin?  The _2.10_0.13 in plugin name is the equiv of cross versioning for 2 levels of binary compatibly: _2.10 for scala _0.13 for sbt. I think that sbt plugins are generally published with ivy still, https://github.com/joshcough/ScalaMinecraftYmlGen/blob/master/build.sbt#L22 may need to be set to false. I think this has something to do with encoding that extra sbt version meta data in some ivy specific format.

For sbt plugins,

publishTo := Some(Classpaths.sbtPluginReleases)

may still be your best bet. I think Josh Suereth is working on setting up an sbt bintray repo so anything you/I can learn from this exercise is helpful. Can you pull this info into a gh issue in bintray-sbt? I dont think its an sbt issue.

 

Thanks.

-Josh

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simple-build-t...@googlegroups.com.
To post to this group, send email to simple-b...@googlegroups.com.
Visit this group at http://groups.google.com/group/simple-build-tool.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Josh Suereth]

Don't be publishing plugins to maven.  It's not the best of ideas.

I'm currently working on sbt-plugin support for bintray, so stay tuned there.  In the meantime, you can publish, using ivy, to our community repo: 

http://www.scala-sbt.org/release/docs/Community/Community-Plugins.html

On Wed, Jul 31, 2013 at 4:58 PM, Josh Cough <josh...@gmail.com> wrote:

-Josh

--

[Josh Cough]

On Thu, Aug 1, 2013 at 1:06 PM, Josh Suereth <joshua....@gmail.com> wrote:

Don't be publishing plugins to maven.  It's not the best of ideas.

Ok, So, bintray has a maven repo by default, and that is where things are magically published with plugin (https://github.com/softprops/bintray-sbt). Would you suggest doing it differently, like, creating a new bintray repo called ivy, and publishing ivy style to that? Or is there anything else you would suggest doing that I'm missing?

 

I'm currently working on sbt-plugin support for bintray, so stay tuned there.

Sure. Can I help in any way?

 

 In the meantime, you can publish, using ivy, to our community repo: 

http://www.scala-sbt.org/release/docs/Community/Community-Plugins.html

These things I'm mentioning aren't plugins, they are just regular projects. I do have one plugin that I could publish there. I was hoping to figure out a way to just get everything published to one place, though. But I still might publish there for now, just so I can have everything building. Thanks.

[Josh Cough]

Sorry, I think some of what I just said might have been confusing because I thought I was replying to a different thread.