-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Java] Allow specification of distributionManagement section in generated pom.xml #9069
base: master
Are you sure you want to change the base?
Conversation
FYI technical committee @bbdouglas @sreeshas @jfiala @lukoyanov @cbornet @jeff9finger @karismann @Zomzog @lwlee2608 @nmuesch |
Hi @falk-stefan, since this PR didn't really go anywhere (sadly!!!) I've found a way to achieve this in the meantime by creating a standalone Maven API project that we're using to build a jaxrs-spec server and a typescript-angular client via our build server.
I removed some bits like a HTML2 and a custom AsciiDoc Generator, as well as some project-specific information, but something like this should be working. During the build, we're simply calling
Credentials for pushing the libraries to our registry (Artifactory in our case) are injected via a custom HTH, |
Hi! Thanks a lot for sharing! I am not sure if this can work in my case though. I'm trying to publish a package to GitHub packages (see). The docs state:
So, I think in order to automate this, I somehow need OpenAPI to set |
Hi @falk-stefan, you're welcome. I never maven published to GitHub but we're also using As for NPM, which we also publish to our Artifactory (instead of GitHub or NPM), we had to learn some things about scoped packages and |
Ah, silly me. I think I misunderstood what you did at first. Now I get it. You're right, this should work. Just let the CI generate the code and publish it. Thanks a lot! :) |
You can achieve this by using Another much less convenient option is using |
This PR enables the configuration to pass repository and snapshotRepository information to the generated pom.xml, so a user can publish the generated package to a maven repository.
Disclaimer: implemented as close as possible to PR #1132, since the functionality is almost identical (thank you @mwoodland, all kudos to you)
PR checklist
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.For Windows users, please run the script in Git BASH.
master
,5.1.x
,6.0.x