Closed gkossakowski closed 9 years ago
Hi @pdalpra! You mentioned in #62 that I should ping you in case there are some problems. It's a bit belated but I'm doing it now :)
I'm looking into it right now ;)
Excellent! Please let me know about your findings!
This is what I thought : sbt-native-packager adds any packages it's building to the list of artifacts that will be published. This is the chain of calls that leads to this behaviour :
The simplest solution IMO is to empty the list of published artifacts in the Universal config after the tarballs settings have been added.
I'll submit a PR right now !
After further investagation, this had, in fact, nothing to do with that :) But I found the issue, which emerges from incorrect settings after the dist project has been merged with the main project.
When I try to publish a new zinc release I get:
The
publishSigned
should just upload signed jars and not try to uploadtgz
archive containing the distribution. The distribution archives should be uploaded to S3.Quick look at
show packagedArtifacts
reveals:This seems to be broken because
packagedArtifacts
should contain jars not the tgz archive.It's most likely that regression has been introduced in #62