aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Bosschaert <david.bosscha...@gmail.com>
Subject Re: Semantic version plugin integration into Aries modules
Date Fri, 11 Jan 2013 08:11:20 GMT
Jeremy, Emily, thanks for the info!

David


On 10 January 2013 22:33, Emily Jiang <emijiang6@googlemail.com> wrote:

> Hi David,
>
> Yes. Jeremy is correct. It doesn't matter what
> packageinfo/package-info.java you used  to denote the package version. The
> generated MANIFEST.MF in the bundle is used by the tool to compare the
> package version changes and the binary file is used for analysing codes
> changes.
>
> As for the plugin, if you enable the automatic generation/correction of
> package-info, the package-info.java will be created. I know you have
> especially expressed your preferrence not to set it as default:).
>
> Thanks
> Emily
>
> On Wed, Jan 9, 2013 at 10:09 AM, Jeremy Hughes <hughesj@apache.org> wrote:
>
> > I'll echo that. Thanks Emily!!
> >
> > David, I had thought it used the versions in the generated manifest. I
> > could be wrong.
> >
> > Cheers,
> > Jeremy
> >
> > On 3 January 2013 12:23, David Bosschaert <david.bosschaert@gmail.com>
> > wrote:
> > > Excellent! Kudos to Emily and others who were involved in this!
> > > One question, does it only work with package-info.java or does it also
> > work
> > > with packageinfo text files? AFAIK BND works with either...
> > >
> > > Looking forward to seeing my builds fail ;)
> > >
> > > Cheers,
> > >
> > > David
> > >
> > >
> > > On 3 January 2013 12:04, Emily Jiang <emijiang6@googlemail.com> wrote:
> > >
> > >> As you may know, I have spent some time to integrate the semantic
> > >> versioning plugin to Aries runtime modules. I have done all modules
> > except
> > >> spi-fly and subsystem as their 1.0.0 versions are not released (hence
> no
> > >> baseline available). Once these modules are released, I will integrate
> > the
> > >> versioning plugin into these modules.
> > >>
> > >> If you do any code changes, your build will fail if you have
> introduced
> > any
> > >> changes leading to semantic version changes without changing the
> > version in
> > >> the package-info.java. The error will tell you what the correct
> version
> > >> should be.
> > >>
> > >> If you find any modules I missed, please let me know. By the way, I
> left
> > >> testing modules out on purpose. If you have a business reason for
> these
> > >> modules to be properly semanitc versioned, please shout now.
> > >>
> > >> --
> > >> Thanks
> > >> Emily
> > >> =================
> > >> Emily Jiang
> > >> ejiang@apache.org
> > >>
> >
>
>
>
> --
> Thanks
> Emily
> =================
> Emily Jiang
> ejiang@apache.org
>

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