Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

SBT publish



  • I'm trying to get sbt publishing from the command line to work with ProGet's maven repository system. I can successfully publish as long as I have the isSnapshot set to true, however, that doesn't seem to show up anywhere in ProGet. As soon as I set isSnapshot to false, the publish fails saying it already exists and can't be overwritten (regardless whether I change the version number or anything else).

    relevant bits of build.sbt:

    organization := "MyCorporation"
    scalaVersion := "2.10.6"
    name := "MyOrders-test"
    version := "1.0.1"
    publishTo := Some("packages.mycorp.com" at "http://packages.mycorp.com/maven-feeds/private-maven")
    credentials += Credentials("packages.mycorp.com", "packages.mycorp.com", "myadmin", "redacted")
    //isSnapshot := true
    

    As is probably obvious in the above, my ProGet install is at http://packages.mycorp.com and the url to my maven feed is http://packages.mycorp.com/maven-feeds/private-maven.

    Any ideas why I would be seeing this or any suggestions on how to work through this?

    Product: ProGet
    Version: 4.4.1



  • We actually haven't tried using SBT just yet (in fact, I just learned about it from your post).

    But generally speaking, one of challenges with Maven is that it's convention-based, and doesn't have any documentation on the convention. So it's possible that SBT is using a slightly different convention than Maven or Ivy clients are. Moreover, different "packages" have a convention to behave differently...

    Would you able to attach Fiddler and see where some of the discrepancies in the request/responses might be? Sometimes it's incredibly obvious, and that might allow us to implement yet another undocumented convention. It may be easier to communicate over email, so perhaps fill out a ticket or just email us at support-at-Inedo-com once you have some details?


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation