Closed escay closed 8 months ago
For building source code that is from a version that is not released yet, it may be the case that some components are still in staging. You can build in that case with -Pstaging.
It is time though to release shoal to maven central. I'll do this soon. For now you can try building with -Pstaging if you want.
I can confirm -Pstaging builds shoal as well. I was not aware of the OSSRH staging approach, I only checked the tag and release commit here.
From https://github.com/eclipse-ee4j/glassfish#special-profiles documentation:
staging - In some development stages may happen that some dependencies are available just in OSSRH staging repository. Then you have to use this profile, which is not enabled by default.
When building Glassfish 7.0.12 from master https://github.com/eclipse-ee4j/glassfish/ I get during the build:
I see shoal version 3.1.0 is not available in the maven repo: https://central.sonatype.com/artifact/org.glassfish.shoal/shoal-cache/versions causing it to fail being available in local nexus.
Last available version in maven is 3.0.1 while shoal version release is on 3.1.0: https://github.com/eclipse-ee4j/glassfish-shoal/tree/3.1.0
Expectation: release 3.1.0 is also available in mvn repository.
Workaround: build shoal 3.1.0 local.