Hi
Am 10.06.2013 um 19:21 schrieb Carsten Ziegeler:
Hi,
the current version of the scr tooling (maven scr plugin, ant task) has
grown over time. We already had a major refactoring due to the drop of
support the javadoc tags.
Now, looking at the code and the features, I would like to
Hi
Am 10.06.2013 um 19:21 schrieb Carsten Ziegeler:
Hi,
the current version of the scr tooling (maven scr plugin, ant task) has
grown over time. We already had a major refactoring due to the drop of
support the javadoc tags.
Now, looking at the code and the features, I would like to
2013/6/11 Felix Meschberger fmesc...@adobe.com
Actually versioning is not the only problem: The other problem is that for
inheritance to work across bundle boundaries, the (abstract) base class has
to be exported which is less of a problem if the base class is abstract
(yet there might be
Hi,
the current version of the scr tooling (maven scr plugin, ant task) has
grown over time. We already had a major refactoring due to the drop of
support the javadoc tags.
Now, looking at the code and the features, I would like to discuss to drop
some more and create a new 2.0 release:
a)
While I kinda think everyone should use the bnd scr plugin and the DS
annotations….. the bnd plugin does support inheritance and IMO it is extremely
useful even if you can break it if you try hard enough. I'm actually not sure
how you'd break it if the bundle with the super class was
Inheritance can break if a lifecycle or reference method is found at build
time in the super class which is not available at run time, e.g. like the
activate method or a bind one.
Right, as the super class needs to be exported, it should be semantically
versioned as well - however such methods
+1 to both changes.
If it was possible to have inheritance work but ONLY within the same bundle
(and fail loudly if you tried to have inheritance across bundles), I think
that would be worth keeping, but not if it is too much trouble.
Justin
On Mon, Jun 10, 2013 at 1:21 PM, Carsten Ziegeler
