search

telefonicaid / fiware-cygnus

A connector in charge of persisting context data sources into other third-party databases and storage systems, creating a historical view of the context
https://fiware-cygnus.rtfd.io/
GNU Affero General Public License v3.0
65 stars 105 forks source link

Cygnus: versioning system #17

Closed fgalan closed 10 years ago

fgalan commented 10 years ago

Implement a full fledged versioning system, so the .jar get marked with a proper version instead of using always the same "1.0-SNAPSHOT" and a changelog between version can be maintained.

Probably Maven has some plugin to manage that. Research needed.

fgalan commented 10 years ago

We'd probably need per-component package in each version (e.g. a package for flume compoment, a package for the SFTP inyector, etc.).

Regarding the packaging "technologies" several alternatives are on the table: RPMs, jar in a Nexus artifactory, a .tgz including all the stuff. For Flume components, maybe the last one is the most appropriate: it would consist of basically using the same .tgz that Flume uses, but adding our .jar in the lib/ directory.

frbattid commented 10 years ago

I think this issue is solved since a milestone schedule has been designed for the next 3 months, and a versioning schema has been provided.

fgalan commented 10 years ago

By "versioning schema" you mean the things included in PR #49 https://github.com/telefonicaid/fiware-connectors/pull/49?

fgalan commented 10 years ago

Given the RPM framework we are using now and the issue about printing Cygnus version in the logs (see #104), this issue can be closed.