Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

publishM2 in sbt 0.13.2-M2 don't overwrite

See original GitHub issue

Changed behaviour compared to 0.13.1.

See log from this pull request build

java.io.IOException: file copy not done from /localhome/jenkinsakka/workspace/pr-validator-per-commit/akka-persistence/target/akka-persistence-experimental_2.10-2.3-SNAPSHOT.pom to /localhome/jenkinsakka/.m2/repository/com/typesafe/akka/akka-persistence-experimental_2.10/2.3-SNAPSHOT/akka-persistence-experimental_2.10-2.3-SNAPSHOT.pom: destination already exists and overwrite is false
    at org.apache.ivy.plugins.repository.file.FileRepository.copy(FileRepository.java:78)
    at org.apache.ivy.plugins.repository.file.FileRepository.put(FileRepository.java:58)
    at org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
    at org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:234)
    at org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:216)
    at sbt.IvyActions$$anonfun$publish$3.apply(IvyActions.scala:262)
    at sbt.IvyActions$$anonfun$publish$3.apply(IvyActions.scala:261)
    at scala.collection.TraversableLike$WithFilter$$anonfun$foreach$1.apply(TraversableLike.scala:772)
    at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
    at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47)
    at scala.collection.TraversableLike$WithFilter.foreach(TraversableLike.scala:771)
    at sbt.IvyActions$.publish(IvyActions.scala:261)
    at sbt.IvyActions$$anonfun$publish$1$$anonfun$apply$1.apply$mcV$sp(IvyActions.scala:97)
    at sbt.IvyActions$$anonfun$publish$1$$anonfun$apply$1.apply(IvyActions.scala:97)
    at sbt.IvyActions$$anonfun$publish$1$$anonfun$apply$1.apply(IvyActions.scala:97)
    at sbt.IvyActions$.withChecksums(IvyActions.scala:106)
    at sbt.IvyActions$.sbt$IvyActions$$withChecksums(IvyActions.scala:101)
    at sbt.IvyActions$$anonfun$publish$1.apply(IvyActions.scala:97)
    at sbt.IvyActions$$anonfun$publish$1.apply(IvyActions.scala:91)

Issue Analytics

State:
Created 10 years ago
Comments:31 (15 by maintainers)

Top GitHub Comments

1reaction

hvesalaicommented, Jun 23, 2016

Could we have an option to completely ignore this. I’ve got a multiproject build where I aggregate submodules so that publishing the main project publishes the submodules. Each submodule has its own version so often the submodule has already been published. I would like publish to work so that I can instruct it to just quietly fail if the artifact already exists (and to overwrite it if it is SNAPSHOT).

1reaction

dircsemcommented, Jul 8, 2014

I’m facing the same problem. isSnapshot has solved it, although it is a temporary solution right? Is there somebody working to solve this issue? Is there an overwrite parameter in sbt? If so how can I use it?

Top Results From Across the Web

sbt - How to overwrite local stable version artifacts using ...

Basically, as of sbt 0.13.2 you can no longer republish a release if it already exists. This is quite a dangerous thing to...

sbt/sbt - Gitter

IOException: destination file exists and overwrite == false ). The problem I'm having is that +publish still attempts to publish the ivy.xml multiple...

sbt Reference Manual — Publishing

This page describes how to publish your project. Publishing consists of uploading a descriptor, such as an Ivy file or Maven POM, and...

Overwrite ivy cache with publish-local - Google Groups

If not what would be the best way to automate the "cleaning" of the cache? (we don't want to have to clean the...

[idea] Add publishStaging task to sbt for creating bundles for ...

If we have publishStaging task (like publishM2) in sbt, we can create a local bundle folder at ease without overriding publishTo setting.