When Roundup does mvn deploy with the release profile in the ArtifactPublicationStep, we treat errors here as "soft"; that is, we can ignore them and move on.
This made sense in the past when we were re-running Roundups for a single release and wanted to get past OSSRH publication. However, the mvn deploy does a ton of different things and now site (javadoc) generation is failing in the registry-api.
We should fail on this, of course! But really, we shouldn't be re-running Roundups anyway. So the easiest solution is just treat mvn deploy failures as "hard" errors"
When Roundup does
mvn deploywith thereleaseprofile in theArtifactPublicationStep, we treat errors here as "soft"; that is, we can ignore them and move on.This made sense in the past when we were re-running Roundups for a single release and wanted to get past OSSRH publication. However, the
mvn deploydoes a ton of different things and now site (javadoc) generation is failing in the registry-api.We should fail on this, of course! But really, we shouldn't be re-running Roundups anyway. So the easiest solution is just treat
mvn deployfailures as "hard" errors"