Hi Daniel,
Thanks for your suggestion.
As there are several "components" or (if declared that under Eclipse) subprojects like "Diana", "Artemis" etc. I don't think putting them all under a single repository might help.
Based on GitHub tagging the release would be rather difficult, if say Diana was updated or even just fixed to 0.0.2 or above while Artemis remained unchanged.
Also if some repositories can move to Eclipse earlier than others, it is easier to keep them somewhat separate.
Werner
Gesendet: Samstag, 18. März 2017 um 02:57 Uhr
Von: "Daniel Cunha" <danielsoro@xxxxxxxxx>
An: "jnosql developer discussions" <jnosql-dev@xxxxxxxxxxx>
Betreff: Re: [jnosql-dev] Release version 0.0.1
Hi Otávio,
we see a build problem on the project (current code on Github), it seems which the release was generated manually. Didn't you use maven-release-plugin to do that?
Other question, what do you think to keep all project in the same repository? A structure like that:
parent
- project 1
- project 1.1
- project 2
- project 3
- project 3.1
This way will be more simple to build all, simple to release all and etc.
Thank you.
_______________________________________________ jnosql-dev mailing list jnosql-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev