Releasing to bintray produces an error

[jmaassen]

When releasing xenon as described in RELEASE.md, the bintray step produces an error:

> Task :publishDocGeneratorPublicationPublicationToDocGeneratorRepoRepository FAILED
Could not transfer artifact nl.esciencecenter.xenon:xenon-docgenerator:jar:3.0.2 from/to remote (https://api.bintray.com/maven/nlesc/xenon/xenon-docgenerator/;publish=1): Could not write to resource 'nl/esciencecenter/xenon/xenon-docgenerator/3.0.2/xenon-docgenerator-3.0.2.jar'
Could not transfer artifact nl.esciencecenter.xenon:xenon-docgenerator:pom:3.0.2 from/to remote (https://api.bintray.com/maven/nlesc/xenon/xenon-docgenerator/;publish=1): Could not write to resource 'nl/esciencecenter/xenon/xenon-docgenerator/3.0.2/xenon-docgenerator-3.0.2.pom'
Could not transfer artifact nl.esciencecenter.xenon:xenon-docgenerator:jar:sources:3.0.2 from/to remote (https://api.bintray.com/maven/nlesc/xenon/xenon-docgenerator/;publish=1): Could not write to resource 'nl/esciencecenter/xenon/xenon-docgenerator/3.0.2/xenon-docgenerator-3.0.2-sources.jar'

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':publishDocGeneratorPublicationPublicationToDocGeneratorRepoRepository'.
> Failed to publish publication 'DocGeneratorPublication' to repository 'DocGeneratorRepo'
   > Could not write to resource 'https://api.bintray.com/maven/nlesc/xenon/xenon-docgenerator/;publish=1/nl/esciencecenter/xenon/xenon-docgenerator/3.0.2/xenon-docgenerator-3.0.2.jar'.
      > Could not PUT 'https://api.bintray.com/maven/nlesc/xenon/xenon-docgenerator/;publish=1/nl/esciencecenter/xenon/xenon-docgenerator/3.0.2/xenon-docgenerator-3.0.2.jar'. Received status code 409 from server: Conflict

The cause seems to be that the xenon-docgenerator is now released separately, and version 3.0.2 already existed.

Should we remove the publishing of the docgenerator from this step?

[sverhoeven]

To generate adaptor documentation for the cloud adaptors I had to make a release.
Let's not delete a existing release.

I see you did a 3.0.3 release, which would have been my suggestion.

Did that release go according to the steps in RELEASE.md?

[jmaassen]

No longer an issue. Worked fine for 3.1.0 release