# Additional repositories (for java 17) **URL:** https://community.sonatype.com/t/additional-repositories-for-java-17/9446 **Category:** Central Repository **Created:** [October 13, 2022, 10:24am UTC](https://community.sonatype.com/t/additional-repositories-for-java-17/9446 "2022-10-13T10:24:32Z") **Posts on this page:** 1 **Showing post:** 1
### Author: ![nigel.l.jones](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/nigel.l.jones/32/1892_2.png) [@nigel.l.jones](https://community.sonatype.com/u/nigel.l.jones) #### Post date: [October 13, 2022, 10:24am UTC](https://community.sonatype.com/t/additional-repositories-for-java-17/9446/1 "2022-10-13T10:24:32Z")
I am a maintainer on ‘Egeria’ (g: org.odpi.egeria) and considering our Java 11-\>17 strategy. We publish many (100s) maven artifacts to ‘Snapshots’ as part of our merge builds, and via staging to ‘Release’ for our monthly releases. Artifacts get signed etc & it’s mostly automated other than promoting staging-\>release. We do build verification/tests on Java 17 already - but don’t distribute the artifacts. Java 17 may cause a little disruption with users of these artifacts. I was considering whether we could publish the java 17 versions to a different repository. I’m unclear if this is doable with the central repositories? Alternatives include using other maven repositories like perhaps github, another artifactory - but that’s a little more work to the pipelines. Or another option might be to adopt different group or artifact names, but with 100s involved i’m concerned this would just be confusing and lead to clutter. Also I know we could use classifiers, but the proposal here is for short term (3-4 months?) testing, with minimal impact to any consumers - like flipping a switch, and classifiers could get messy… We’re hoping NOT to continue building with java 11 beyond this and flip over for our next major version. Any suggestions? --- _[View the full topic](https://community.sonatype.com/t/additional-repositories-for-java-17/9446)._