-
Notifications
You must be signed in to change notification settings - Fork 1
mvn deploy no longer works in DevTools with Server credentials with ID "ossrh" not found!
#9
Comments
Why mvn deploy is used? Shouldn't it be fabric8:deploy instead? |
|
I wonder if its the introduction of the <plugin>
<groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId>
<version>${nexus-staging-maven-plugin.version}</version>
<extensions>true</extensions>
<configuration>
<serverId>ossrh</serverId>
<nexusUrl>https://oss.sonatype.org/</nexusUrl>
<autoReleaseAfterClose>true</autoReleaseAfterClose>
</configuration>
</plugin> If so I wonder if we can put it into some optional profile so its not activated OOTB? We don't want to use sonatype staging repo for releases on DevTools; we include a nexus-like thingy |
That makes sense. I think we should move it under a |
Yes that's our release process. What are you doing in the |
I guess I'm surprised that a generated quickstart has staging repo stuff enabled OOTB? |
it comes from the parent, without this we can't release the parent to maven central. Introducing a release profile, would actually introduce another profile in which the "verification build" is issued. |
So you bind fabric8:deploy to the deploy phase. While To use it like that we need to redo the parent and release process (and probably give up with the maven central sync) |
FWIW on fabric8 we release archetypes to maven central; but the archetypes use different I wonder if this relates to #10 as to whether or not the generated projects should use parent poms at all? Maybe a workaround is to just remove the parent pom in the wizard as the project is created? |
@jstrachan AIUI in this case we do want to run a deploy, as we want to deploy the code to a local content repository for the user as part of the CD pipeline, and having the quickstart's clobber this makes it hard. I would suggest hat how we release the quickstart should not be part of quickstarts code, as the quickstart should be a learning experience for the end user. |
I believe this may be closed by nature of the course of action detailed by #11 ? |
do the boosters do something now with staging plugins or explicitly specify distribution properties or something? This used to work fine but seems to have broken recently...
Will see if we can add some extra property or something to disable/configure this...
Here's the log for the pipeline using Vertx Booster:
The text was updated successfully, but these errors were encountered: