You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a devon4j user/developer, I want to make SNAPSHOT versions publically available so that they can be easily accessed in other builds or for externals who want to test an upcoming release that is WIP.
Therefore we should do the following:
extend maven-parent with snapshot repo pointing to OSSRH and release update
update devon4j to that maven-parent
extend .travis.yml of devon4j to deploy SNAPSHOTS to OSSRH
Then even MTS can use intermediate SNAPSHOT versions of devon4j in CI.
So the deployment succeeded for all artifacts except the last one which is devon4j-doc that failed with 401.
So if the other deployments succeeded the secrets and credentials have to be correct. So why on earth should the last artifact get a 401. This does not make any sense to me. Any ideas?
BTW: I also considered using a new travis stage for the deployment but unfortunately every stage runs in a seprate container and therefore previous results would be lost. That would lead to duplicated build efforts and longer build times. Hence, I sticked to the approach that worked best for me from the mmm project (with somewhat ugly && and || chained commands in the script).
Activity
devonfw/devon4j#198: add OSSRH as snapshot repo
devonfw#198: deploy SNAPSHOTs to OSSRH
devonfw#198: created new nexus user token and updated secrets
devonfw#198: was a copy&paste bug from old repo
devonfw#198: also fixed repo id
devonfw#198: do not deploy from PR
devonfw#198: trial and error
#198: deploy SNAPSHOTs to OSSRH (#226)
hohwille commentedon Mar 5, 2020
Travis now procudes such build:
hohwille commentedon Mar 5, 2020
So the deployment succeeded for all artifacts except the last one which is
devon4j-docthat failed with 401.So if the other deployments succeeded the secrets and credentials have to be correct. So why on earth should the last artifact get a 401. This does not make any sense to me. Any ideas?
BTW: I also considered using a new travis stage for the deployment but unfortunately every stage runs in a seprate container and therefore previous results would be lost. That would lead to duplicated build efforts and longer build times. Hence, I sticked to the approach that worked best for me from the
mmmproject (with somewhat ugly && and || chained commands in the script).#198: updated .travis (deploy SNAPSHOTs)
hohwille commentedon Mar 6, 2020
I figured it out myself:
The parent of devon4j-doc is not pointing to devon4j but to
devonfw-docgen-pdfhttps://github.com/devonfw/devon4j/blob/develop/documentation/pom.xml#L7
That POM has
devonfw-docgenas parent in version5.0.0:view-source:https://repo1.maven.org/maven2/com/devonfw/tools/devonfw-docgen/5.0.0/devonfw-docgen-5.0.0.pom
And that POM points to
devonfw-maven-parentin version2:https://repo1.maven.org/maven2/com/devonfw/maven-parent/2/maven-parent-2.pom
As you can see in version
2the repository IDs have still been different:Hence I first have to update
docgenand push out a new release.#198: updated docgen to 5.0.1
hohwille commentedon Mar 6, 2020
Yep. Analysis was correct. Fix confirmed. Closing.