I’m still not sure what the eventual resolution of this discussion will be as
it may be that Aries implementation needs simply cannot be met by using the
Service Mix spec bundles, however I do agree that we should be fixing up
Service Mix API bundles as far as we can. To that end I have created
> On Dec 22, 2017, at 10:30 AM, Raymond Auge wrote:
>
>> Do those spec bundles also exist over in SMX or Geronimo? Is there a
>> “significant” number of major Apache projects that are currently using
>> either the ones in Aries or the ones in ServiceMix/Geronimo? If so, then
>> yea, we shou
On Fri, Dec 22, 2017 at 8:12 AM, Daniel Kulp wrote:
>
>
> > On Dec 22, 2017, at 4:14 AM, Timothy Ward
> wrote:
> >
> > I’m completely against having yet another bundle here when the other
> bundles are the ones that will be be used by all the other projects.
> >
> > Well we already do have worki
> On Dec 22, 2017, at 4:14 AM, Timothy Ward wrote:
>
> I’m completely against having yet another bundle here when the other bundles
> are the ones that will be be used by all the other projects.
>
> Well we already do have working spec bundles here at Aries (and have had for
> quite some tim
How about fixing the servicemix bundles in a branch and maybe even release
a version from the branch to cope with the narrow time frame.
So the specs bundles still live in servicemix and it is easier to
consolidate them into one common version again.
Christian
2017-12-22 10:14 GMT+01:00 Timothy W
My mail client appears to have messed up the indenting, sorry about that. I
hope that people can still make sense of the previous mail.
Tim
> On 22 Dec 2017, at 09:14, Timothy Ward wrote:
>
> I’m completely against having yet another bundle here when the other bundles
> are the ones that will
I’m completely against having yet another bundle here when the other bundles
are the ones that will be be used by all the other projects.
Well we already do have working spec bundles here at Aries (and have had for
quite some time), so is your proposal to remove them?
That’s fine as a proposal,
> On Dec 21, 2017, at 1:00 PM, Raymond Auge wrote:
>
> On Thu, Dec 21, 2017 at 12:43 PM, Daniel Kulp wrote:
>
>> Can I ask why the spec/api bundles that are provided by ServiceMix are not
>> usable? Could the ServiceMix api bundles be updated to make them usable?
>>
>
> Most of the Servic
RE: geronimo
The geronimo ones were good in large part, but they aren't complete and
often no up to date and we couldn't afford to wait for someone to clean
room the updates we needed.
On Thu, Dec 21, 2017 at 12:43 PM, Daniel Kulp wrote:
> Can I ask why the spec/api bundles that are provided b
Can I ask why the spec/api bundles that are provided by ServiceMix are not
usable? Could the ServiceMix api bundles be updated to make them usable?
I really would prefer not getting into a situation where we have a bunch of
project that are commonly used together starting to pull in multiple v
Another alternative might be to use the Geronimo spec jars and make sure the
included osgi metadata is correct.
David Jencks
Sent from my iPhone
> On Dec 21, 2017, at 6:28 AM, Raymond Auge wrote:
>
> Hi Tim,
>
> I was thinking of proposing this very thing over the last few weeks.
>
> I had
Hi Tim,
I was thinking of proposing this very thing over the last few weeks.
I had already deliberately pushed the CDI related spec jars and also the
spec jar for JAX-RS into an aries sub-group in maven in order to better
accommodate and reflect this very thing.
So, I would be a big +1 for havin
Hi all,
I’ve noticed that an increasing number of Aries projects are producing wrapped
spec jars (JPA, JAX-RS, CDI...). In general I think that this is a good thing,
as few other Open Source projects package the jars with OSGi contract metadata.
I do wonder, however, if these spec jars should b
13 matches
Mail list logo
