Closed keilw closed 4 years ago
@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?
E.g.:
For most Eclipse projects, the standard is "org.eclipse.
For specification projects run under the supervision of the Jakarta EE working group, the standard is to use "jakarta.
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:
Along the planned change of the package (#183) the Maven groupId should also use
org.eclipse.jnosql
.