Merge jnosql-communication-driver and jnosql-mapping-extension repositories into a single module[Task]
otaviojava opened this issue · comments
The task for the: #353
Structure
- Rename the project from
jnosql-communication-drivertojnosql-databases - Rename the project from
jnosql-mapping-extensiontojnosql-extensions - Update Parent-pom to use
org.eclipse.jnosql.databasesas group ID - Create and define tags to test that needs a database and disable it by default.
Merge project
This one needs to merge communication and mapping into a single module.
- We need to be sure that we won't impact the package name
- Update documentation at readme
- Remove codes from the extension repository
Databases
- jnosql-arangodb-extension
- jnosql-cassandra-extension
- jnosql-couchbase-extension
- jnosql-elasticsearch-extension
- jnosql-hazelcast-extension
- jnosql-mongodb-extension
- jnosql-orientdb-extension
- jnosql-solr-extension
I've created this issue to rename the project:
@dearrudam let me know if you wanna take some of this.
@otaviojava, I could work at this one: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2894, but I think that I need to have permission to do it. Could you help me with that?!
@otaviojava never mind! This renaming process could be done later...
I could work on the jnosql-arangodb-extension, okay?
I got an idea: I think that you could convert each item of this "Databases" list into sub-issues. With that, any of us could assign ourselves to one of these sub-issues. Also, on each state changing of each sub-issue will be propagated to this issue automatically.
I like it; I'll take the Cassandra one to feel the terrain.
the ulrs have been updated:
I'll close this one.
Thank you @dearrudam