Emily,

Are you using ASM, or some other bytecode tool, to work out what has changed, 
or do you have to load classes and use reflection to find out?

Regards,

Tim

> Date: Wed, 28 Sep 2011 16:58:33 +0100
> Subject: Re: Semantic Versioning tool
> From: [email protected]
> To: [email protected]
> 
> Hi David,
> 
> It works by comparing the current binary with the baseline binary:
> 1. For each export package, it scans each non private class to see whether
> there are binary incompatibility changes (according to Java specificiation
> chapter 13 Binary Compability). If yes, a major version change is needed for
> this pkg.
> 2. If there are not binary incompability changes, it will see whether there
> are abstract class, methods or new xsd file added. If yes, the package's
> minor version needs to be increased.
> 3. It then determine the bundle version based on package versions changed
> according to semantic versioning white paper.
> 
> The tool ignore micro version changes.
> 
> I can contribute the tool as a project and then we can create a mvn plugin
> from it or something even smarter.
> 
> Regards,
> Emily
> 
> On Wed, Sep 28, 2011 at 4:16 PM, David Bosschaert <
> [email protected]> wrote:
> 
> > Very interesting, Emily. Would you be able to provide some information
> > regarding how it works?
> >
> > In any case I would welcome such an addition to Aries.
> >
> > Best regards,
> >
> > David
> >
> > On 28 September 2011 16:02, Emily Jiang <[email protected]> wrote:
> > > I have developed a semantic checking tool to check whether a bundle's
> > > version or the export package versions are correclty versioned according
> > to
> > > OSGi semantic versioning whitepaper. I would like to contribute to Apache
> > > Aries as subproject under a code name of 'llama' ( or a better name. I am
> > > open to suggestions).
> > >
> > > Any thoughts or suggestions?
> > > --
> > > Thanks
> > > Emily
> > > =================
> > > Emily Jiang
> > > [email protected]
> > >
> >
> 
> 
> 
> -- 
> Thanks
> Emily
> =================
> Emily Jiang
> [email protected]
                                          

Reply via email to