Thanks for your answers! It really helps to know what people do in real life
Le 7 nov. 2013 à 08:43, Marcel Offermans a écrit : > There are two other solutions: > > If your latest release is, for example, 1.8.0 you can: > > 1) Start using snapshots that are named 1.8.0.xxx (where xxx is either > "SNAPSHOT" or some increasing number/timestamp) to ensure that whatever next > release you make after 1.8.0 is always newer than all of these "snapshots". > This also solves the problem that you might not yet know what the next > release will be (if you use semantic versioning it can be 1.8.1, 1.9.0 or > 2.0.0 depending on what happens to your code). > > 2) Also use qualifiers in your release versions and make sure that these > qualifiers are always newer than the qualifiers you use for the snapshots > before that. > > We actually use #1 succesfully in our company "continuous build" environment, > so that would be my recommendation. > > Greetings, Marcel > > > On 07 Nov 2013, at 8:32 am, David Jencks <[email protected]> wrote: > >> For felix projects we increment the version number on release, so >> >> 1.7.0-SNAPSHOT >> 1.8.0 >> 1.6.1-SNAPSHOT >> 1.6.2 >> etc. >> >> david jencks >> >> On Nov 6, 2013, at 1:05 PM, Benoît Thiébault <[email protected]> wrote: >> >>> OK, but how do you manage your OBR then? Only deploy final versions? >>> >>> "Richard S. Hall" <[email protected]> a écrit : >>> >>>> This is a known issue between how Maven interprets the -SNAPSHOT >>>> qualifier and how OSGi interprets version qualifiers. For Maven, the >>>> -SNAPSHOT qualifier is less that the actual version specified, but for >>>> OSGi qualifiers are just sorted so a qualified version is greater (i.e., >>>> newer) than an unqualified version. >>>> >>>> -> richard >>>> >>>> On 11/6/13, 11:48 , Benoît Thiébault wrote: >>>>> Hi, >>>>> >>>>> I have been playing with OSGi bundle repositories lately and noticed the >>>>> following behaviour. >>>>> >>>>> In Felix (4.0.2), after adding my OBR URL, I type "obr:deploy my-bundle". >>>>> >>>>> On the OBR, I have 2 versions available of this bundle: >>>>> - 1.0.7 >>>>> - 1.0.7-SNAPSHOT >>>>> >>>>> By default, Felix deploys the SNAPSHOT version. Is this an expected >>>>> behaviour? >>>>> >>>>> I know I can force the use of a given version, but I was surprise by the >>>>> default behaviour. >>>>> >>>>> Moreover, if my-bundle depends on a "my-bundle2" bundle, that itself is >>>>> available in SNAPSHOT and final versions, the SNAPSHOT is chosen by >>>>> default... >>>>> >>>>> Thanks for your help, >>>>> >>>>> Kind regards, >>>>> >>>>> Ben >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[� \�\��][��X��ܚX�P�[^ �\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[� \�\��Z[ �[^ �\X�K�ܙ�B >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Dr Benoît Thiébault Project Manager Artenum Toulouse - Science & Groupware http://www.artenum.com Bâtiment Calfocenter 10, rue Marguerite-Long 31320 Castanet-Tolosan France Phone: +33 (0)5 82 95 19 00
