eclipse / jnosql

Eclipse JNoSQL is a framework which has the goal to help Java developers to create Jakarta EE applications with NoSQL.
Other
231 stars 72 forks source link

Change groupId #205

Closed keilw closed 4 years ago

keilw commented 5 years ago

Along the planned change of the package (#183) the Maven groupId should also use org.eclipse.jnosql.

keilw commented 5 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?

otaviojava commented 5 years ago

I guess we can request it without a problem.

@keilw What is the the name convention?

Communicatoin

Mapping

E.g.:

waynebeaton commented 5 years ago

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".

otaviojava commented 5 years ago

@keilw

otaviojava commented 5 years ago

Request the group.id: https://issues.sonatype.org/browse/OSSRH-51415

otaviojava commented 5 years ago

I also created a ticket to do it by Jenkins.

otaviojava commented 5 years ago

Hey everybody, yesterday, I created PRs to adjustment to the new Group id. Right now, we're moving to the new JNoSQL infra.

keilw commented 5 years ago

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?

otaviojava commented 5 years ago

Now it is working :). I need to create the publisher jobs, I'll do it after the Jarkarta One sessions.

otaviojava commented 5 years ago

Finally, we have all set up that includes the Jenkins instances: