[2.7] Javadoc generation before upload to staging server #788
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix is required due a switch to new staging server https://jakarta.oss.sonatype.org.
There is a new repository closing policy which requires, that published artifact contains binaries, sources and javadoc archive.
Without javadoc archive https://jakarta.oss.sonatype.org server throws error like:
[ERROR] * Missing: no javadoc jar found in folder '/org/eclipse/persistence/org.eclipse.persistence.jpa.jpql/2.7.7-RC1'
see https://ci.eclipse.org/eclipselink/view/Current%20Jobs/job/Maven%20repo%20operations/8/console .
This solution doesn't have any negative impact to build process performance.
Testing output is available at
https://jakarta.oss.sonatype.org/#view-repositories;orgeclipsepersistence-1005~browsestorage
or
https://jakarta.oss.sonatype.org/content/repositories/orgeclipsepersistence-1005/org/eclipse/persistence/
or
https://jakarta.oss.sonatype.org/content/groups/staging/org/eclipse/persistence/
as 2.7.7-RC1 version.
Signed-off-by: Radek Felcman [email protected]