aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Przybysz <>
Subject Re: [Proposal] Use release per subproject for blueprint
Date Tue, 03 Jan 2017 12:28:48 GMT
I think this is great idea but plugin directory should be excluded from
common versioning. Maybe we should even put this directory next to
blueprint in aries root.

2017-01-03 12:34 GMT+01:00 Christian Schneider <>:

> Currently the blueprint bundles are released individually. I think this
> creates a lot of overhead as there are quite many bundles and for each
> release you have to manually update the dependencies in several places. I
> am also sure that we quite regularly forgot to update dependencies. For
> example the blueprint-repository project was not updated for any recent
> releases.
> So I propose we change the blueprint subproject to always release all
> bundles and keep the bundle versions aligned. We should still be able to
> make the project very stable by using package versions for the APIs.
> A side effect would be that we could have blueprint karaf features and an
> OBR repository for other non karaf deployments in the aries blueprint code
> and the maintenance would be quite low.
> So what do you think?
> Christian
> --
> Christian Schneider
> Open Source Architect

Pozdrawiam / Regards,
Dominik Przybysz

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message