Ossrh Migration Support #900
Conversation
…ts easier to locate in the maven central repository.
…hought I could use the project name to create a customized filter URL to simplify the link in the instructions, but that doesn't appear to work as desired. This qualifier should make it easier to identify the desired project contents much easier among multiple deployments.
|
@jeremiahjstacey - Sorry about that... I made a few additional comments and some very minor corrections to https://docs.google.com/document/d/1ObOHGk9LzxMUdZH_1ONqzSJxl78zjGXzNkZB5iCmE-E/edit?tab=t.0 before I realized that you'd saved that as an ODT and PDF here. I must say that you have done an exemplary job with the documentation though. I really appreciate you taking this over. Thanks again. |
kwwall
left a comment
kwwall
left a comment
There was a problem hiding this comment.
LGTM. I didn't check, but I presume that this still uploads the files used with
<classifier>jakarta</classifier>such as "esapi-2.x.y.z-jakarta.jar" file, right?
Also, some new comments over at Google Docs.
the jakarta artifacts were created and published, and should be publicly available |
Updating section 2.3 with sonatype-supported gpg key servers Updating section 7 with new Reference URLs for updated workflow.
Updated section 7 (references) with some new link information. Most of the Sonatype links were no longer valid: Note the GPG Management::Sonatype Supported Servers content. Servers listed in the Sonatype documentation have been added to section 2.3, and invalid links have been removed Thank you for calling out the invalid references! |
xeno6696
left a comment
xeno6696
left a comment
There was a problem hiding this comment.
Looks like the documentation was much more difficult than the actual change here.
3 participants
Closes #891
Contains pom configuration changes and documentation updates accounting for migration to OSSRH maven central hosting.
Documentation updates performed through google docs, exported as .odt and .pdf formats.