Nice work! I don't know if this is a side effect of that feature but I found that deploying snapshot seems broken.
After deploying a snapshot, I try to use it from an other package and I get the following error: Could not find artifact funcool:httpurr:jar:0.5.0-20160313.*195427-3* in clojars (https://clojars.org/repo/) This could be due to a typo in :dependencies or network issues. If you are behind a proxy, try setting the 'http_proxy' environment variable. Navigating (using the browser) we can found that under https://clojars.org/repo/funcool/httpurr/0.5.0-SNAPSHOT/ we have httpurr-0.5.0-20160313.*195434*-3.jar 13-Mar-2016 19:54 httpurr-0.5.0-20160313.195434-3.jar.md5 13-Mar-2016 19:54 httpurr-0.5.0-20160313.195434-3.jar.sha1 13-Mar-2016 19:54 httpurr-0.5.0-20160313.195434-3.pom 13-Mar-2016 19:54 httpurr-0.5.0-20160313.195434-3.pom.md5 13-Mar-2016 19:54 httpurr-0.5.0-20160313.195434-3.pom.sha1 13-Mar-2016 19:54 So, the snapshot is successfully uploaded but for some reason, leiningen tries to download a wrong file. I don't know if this is something wrong from my side but I have changed nothing for a while. On Tue, Mar 8, 2016 at 5:29 PM, Ning Sun <[email protected]> wrote: > Thanks! This is a great feature and especially important for users with > a poor network connection. > > On 03/08/2016 10:43 PM, Mayank Jain wrote: > > Thank you so much for this! I've personally faced this issue before. So > > I know how helpful this change is. Great job! :) > > > > On Mar 8, 2016 7:39 PM, "Toby Crawley" <[email protected] > > <mailto:[email protected]>> wrote: > > > > We just pushed a new release of Clojars that includes a new > > implementation of our internal deploy logic. The big change there is > > deployments are now atomic - if the deployment fails (due to a > network > > interruption/corruption or invalid artifacts), then we no longer > write > > it to the repository. > > > > We verify the deployment by applying a set of validations (see > > https://github.com/clojars/clojars-web/wiki/Pushing#validations) > after > > all of the artifacts have been uploaded, but before we send back a > > response to the final PUT. This allows us to return a (hopefully > > helpful) error message if any of the validations fail. > > > > >From a user perspective, deployment should behave the same for the > > most part - the only thing that would be different is we now validate > > after all of the artifacts are uploaded instead of applying some > > validations for each artifact. This means that if you try to redeploy > > a non-SNAPSHOT version, for example, it used to fail on the first > > artifact, but will now fail after the /last/ artifact has been > > uploaded. > > > > As part of this change, we repaired any invalid non-SNAPSHOT > > maven-metadata.xml files that had resulted from partial deploys > > (likely from network interruptions) in the past. > > > > Since this is a big internal change, please let us know if you see > any > > issues or oddness with deployment. You can file an issue > > (https://github.com/clojars/clojars-web/issues), or find us in > > #clojars on either the Clojurians slack or Freenode. > > > > - Toby > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Clojure" group. > > To post to this group, send email to [email protected] > > <mailto:[email protected]> > > Note that posts from new members are moderated - please be patient > > with your first post. > > To unsubscribe from this group, send email to > > [email protected] > > <mailto:clojure%[email protected]> > > For more options, visit this group at > > http://groups.google.com/group/clojure?hl=en > > --- > > You received this message because you are subscribed to the Google > > Groups "Clojure" group. > > To unsubscribe from this group and stop receiving emails from it, > > send an email to [email protected] > > <mailto:clojure%[email protected]>. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Clojure" group. > > To post to this group, send email to [email protected] > > Note that posts from new members are moderated - please be patient with > > your first post. > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > > http://groups.google.com/group/clojure?hl=en > > --- > > You received this message because you are subscribed to the Google > > Groups "Clojure" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [email protected] > > <mailto:[email protected]>. > > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to [email protected] > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Andrey Antukh - Андрей Антух - <[email protected]> http://www.niwi.nz https://github.com/niwinz -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
