search

arrowhead-f / client-java

Arrowhead Framework Client Skeletons in Java
https://forge.soa4d.org/plugins/mediawiki/wiki/arrowhead-f/index.php/Main_Page
Apache License 2.0
1 stars 6 forks source link

Version number of arrowhead client should be 4.1.0 #8

Closed fortikeco closed 5 years ago

fortikeco commented 5 years ago

I noticed that, although the core is version 4.1.0, the client git tag for 4.1.0 and master currently have the version number 4.0 in the pom file. Could the version number be bumped?

hegeduscs commented 5 years ago

The clients are not versioned according to the core systems entirely.

They are versioned by having "major.patch" semantic versioning, where the major of the clients correspond to the core systems' major number (i.e. REST interface compatibility), while the minor of the clients is merely a patch number.

fortikeco commented 5 years ago

Seems to me that versioning schematic is very unusual!

Op wo 6 mrt. 2019 om 09:05 schreef Csaba Hegedus notifications@github.com:

The clients are not versioned according to the core systems entirely.

They are versioned by having "major.patch" semantic versioning, where the major of the clients correspond to the core systems' major number (i.e. REST interface compatibility), while the minor of the clients is merely a patch number.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/arrowhead-f/client-java/issues/8#issuecomment-470008532, or mute the thread https://github.com/notifications/unsubscribe-auth/ATM26OMhgrRIgDKtt8G8_dvXw7L2UgvBks5vT3bQgaJpZM4beshe .

hegeduscs commented 5 years ago

Well, that happens when we have several core modules developed separately, with separate versioning and with various client types that interact with various core systems.

The clients are versioned with having their major number correspond to the major number of the core system they are interacting with:

fortikeco commented 5 years ago

Thanks for your answer! Is there a possibility then that the arrowhead-client 4.0 jar (although it then is compatible with 4.1.0 services) gets uploaded to the Maven Central Repository? Right now, I make the client be part of our services and include all the code, which is actually unmaintainable. A dependency would be more logical.