Re: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Jean-Baptiste Onofré
Hi, Karaf is not a problem, we will use one property per spec used in Karaf features. Not a big deal, I will do the change accordingly. Regards JB On 01/05/2018 07:47 AM, Grzegorz Grzybek wrote: Hello Separator "_" would match ordinary SMX bundles versioning, so it's consistent. One thing

Re: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Grzegorz Grzybek
Hello Separator "_" would match ordinary SMX bundles versioning, so it's consistent. One thing that comes to my mind is that now (e.g., in Karaf's pom.xml) we have: 2.9.0 That has to change. But I can imagine it's still much easier than releasing all specs when only one is needed. best

Re: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Daniel Kulp
Yea… using the “_” separator would work. We couldn’t do a “.”, but a separator could work to denote the “version” from servicemix. Dan > On Jan 4, 2018, at 12:04 PM, Jean-Baptiste Onofré wrote: > > That could work but we need to extend the version with a specific

R: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Andrea Cosentino
I agree. +1. It makes sense. Inviato da Yahoo Mail su Android Il gio, 4 gen, 2018 alle 16:39, Jean-Baptiste Onofré ha scritto: Hi guys, Up to now, we did monolithic ServiceMix Spec release (all spec in a row). As the spec are very stable, it's really painful to do a

Re: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Jean-Baptiste Onofré
That could work but we need to extend the version with a specific iteration. For instance servicemix-specs-jaxrs-api-2.1 could be servicemix-specs-jaxrs-api-2.1_1 (for instance, we can imagine to have a new fix/builds on the same spec version). It's the same format as in the bundles. Regards

Re: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Francois Papon
Hi, I think it's a very good idea. Just for my curiosity, why not use the specification version in the release ? For example, in servicemix-specs-2.9.0, the jaxrs-api version is 2.1, may be it would be easier to check if the new release will be servicemix-specs-jaxrs-api-2.1 ? And to release a

Re: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Jean-Baptiste Onofré
Agree to start all new SMX specs to 3.0 and increase async each one. Regards JB On 01/04/2018 04:49 PM, Daniel Kulp wrote: I definitely agree with this.The last thing I needed from specs was JUST a new jax-rs bundle so I did just do a release of just that bundle. However, with the build

Re: [PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Daniel Kulp
I definitely agree with this.The last thing I needed from specs was JUST a new jax-rs bundle so I did just do a release of just that bundle. However, with the build setup for monolithic releases, it was harder than it should be. It would be great to get the poms and such setup so we

[PROPOSAL] Prepare ServiceMix Spec to be able to release per spec

2018-01-04 Thread Jean-Baptiste Onofré
Hi guys, Up to now, we did monolithic ServiceMix Spec release (all spec in a row). As the spec are very stable, it's really painful to do a full specs release when a did a minor update or fix on a single spec. As we do for the bundles, I propose to change ServiceMix Specs in order to be