Change groupId
keilw opened this issue · comments
Along the planned change of the package (#183) the Maven groupId should also use org.eclipse.jnosql.
@waynebeaton Is there anything we'd have to request for that with Sonatype, or does any groupId under org.eclipse work for Eclipse projects anyway?
I guess we can request it without a problem.
@keilw
What is the the name convention?
Communicatoin
- org.eclipse.jnosql.diana.*
E.g.: - org.eclipse.jnosql.diana.keyvalue
- org.eclipse.jnosql.diana.column
- org.eclipse.jnosql.diana.document
Mapping
- org.eclipse.jnosql.artemis.*
E.g.:
- org.eclipse.jnosql.artemis.keyvalue
- org.eclipse.jnosql.artemis.column
- org.eclipse.jnosql.artemis.document
- org.eclipse.jnosql.artemis.graph
For most Eclipse projects, the standard is "org.eclipse.", so in the case of Eclipse JNoSQL, it should be "org.eclipse.jnosql".
For specification projects run under the supervision of the Jakarta EE working group, the standard is to use "jakarta.", so for Jakarta NoSQL, it should be "jakarta.nosql".
Request the group.id:
https://issues.sonatype.org/browse/OSSRH-51415
I also created a ticket to do it by Jenkins.
Hey everybody, yesterday, I created PRs to adjustment to the new Group id.
Right now, we're moving to the new JNoSQL infra.
Will those 2-3 PRs work without creating a conflict? The groupId could have been separate from refactoring the internal package-name because the package does not rely on Sonatype.
IC it was merged, so guess Jenkins won't fail right now?
Now it is working :).
I need to create the publisher jobs, I'll do it after the Jarkarta One sessions.
Finally, we have all set up that includes the Jenkins instances:
- Eclipse JNoSQL: https://ci-staging.eclipse.org/jnosql/
- Jakarta NoSQL: https://ci.eclipse.org/nosql/