On Feb 22, 2013, at 10:43 AM, David Bosschaert <[email protected]> wrote:
> Hi all, > > I was looking at the Aries Versioning Plugin and have a few questions: > > * How does one make the distinction between interfaces that are supposed to > be implemented by the client? In OSGi this is typically marked with a > @noimplement javadoc tag, but this doesn't seem to work? When I was playing > with it additions to an interface (i.e. adding a method) always results in a > minor version update, regardless of whether the @noimplement doclet tag was > there or not... Or should that be configured differently? I don't think it handles it at all. To use javadoc tags would require parsing source which it currently doesn't do (I think). An annotation would be more useful I think, but that may then require an extra dependency. > * I see that the previous version of the bundle is marked in the pom.xml, i.e. > > <oldArtifact>org.apache.aries.proxy:org.apache.aries.proxy.api:1.0.0</oldArtifact> > does this automatically get updated when a release is done? No. Needs to be done manually post release. Which makes doing release in Aries even crappier. > * Some of the messages still made a reference to WAS, e.g: > "In the ProxyManager.java class or its supers, the following abstract > methods have been added since the last release of WAS." > I changed that to 'this bundle' in r1449076, hope that's ok with everyone. +1 -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
