|Re: How to update subset of p2 site content? [message #765491 is a reply to message #765243]
||Wed, 14 December 2011 07:26
|| Thomas Hallgren
Registered: July 2009
It's likely that you would benefit from using a
lastModified/lastRevision qualifier generator. It will generate a
qualifier based on repository (svn/git/cvs) data so that unless you
change your code, the qualifier will remain the same.
The feature qualifier is then based on the qualifiers of each of its
included features/plugins so that unless at least one them change, the
feature qualifier will also remain stable.
On 2011-12-13 18:25, Andrey Ilinykh wrote:
> Hello everybody!
> Our application has a bunch of features. Each feature has its own life
> cycle and release schedule, but all of them use the same p2 site. As far
> I understand, buckminster rebuilds all projects. As result when we
> create p2 site all features get new versions (because of qualifier), and
> application has to update everything even only one feature gets version
> What is the best way to handle this situation? What is the best practice
> to use the same p2 site for several independent components?
> Thank you,
Powered by FUDForum
. Page generated in 0.02062 seconds