You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Jean-Baptiste Onofre <jb...@nanthrax.net> on 2009/12/14 08:54:14 UTC
[PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Hi gentlemen,
Yesterday I have upgraded SMX resources (component, feature, etc) to use
Apache Camel 2.1 as it has been released.
I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
I propose the following steps:
1/ I begin to prepare the 2009.02 components release. It includes:
- component-pom 4
- jbi-maven-plugin 4.2
These artifacts will be submit to a first vote.
- all components 2009.02
All components artifacts will be submit to a second vote.
1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
using Karaf 1.2.0 and perform some test to check how it runs.
2/ once these steps 1 and 1 bis have been performed, we can upgrade the
smx 3 and smx 4 POMs to use the previously released components.
Two votes will be submitted: one for SMX3 and another one for SMX4.
What do you think about that ?
Regards
JB
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Gert Vanthienen <ge...@gmail.com>.
Charles,
The only way to handle this scenario now is by removing the snapshot
jar from the system folder or by doing an osgi:update <id> <a
non-maven bundle location>.
We might be able to tweak FileInstall to somehow ignore the file in
system if a newer snapshot version is put in the deploy folder, but
I'd have to look into how we can do that (tweak the mvn: url handler
to ignore the the one file in the repo or, probably easier, update the
bundle from the alternative location.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/12/14 Charles Moulliard <cm...@gmail.com>:
> Hi Gert,
>
> This situation only occurs when we would like to update snapshot. In this
> case, karaf will pick up the snapshot file of the system folder and not the
> last from maven repository.
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Mon, Dec 14, 2009 at 10:24 AM, Gert Vanthienen <gert.vanthienen@gmail.com
>> wrote:
>
>> Charles,
>>
>> I'm not sure I understand what the problem is. If you install a newer
>> version of a JAR in the runtime, the jar file in the /system folder is
>> not being used, e.g. if you install CXF 2.2.6 in a few weeks, the
>> existing bundle in /system will still have the 2.2.5 version so it
>> should not interfere as long as the versions on the import/export
>> headers are ok. There might be an issue with things like custom
>> namespace handlers and things like that though. E.g. for camel, the
>> camel-blueprint work should make it easier to use multiple versions of
>> camel using the XML syntax.
>>
>> Actually, the only real solution is probably to have much shorter
>> release cycles on the ServiceMix 4.x line, where we do a release
>> quarterly or so to pick the latest and greatest bits of Camel, CXF,
>> ActiveMQ, ...
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> Open Source SOA: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> 2009/12/14 Charles Moulliard <cm...@gmail.com>:
>> > Excellent idea for SMX3 and SMX4.
>> >
>> > Concerning SMX 4.1 release, I propose that clarification is done for the
>> > user concerning features and jars already installed in the distro (folder
>> > system). The risk is that users using SMX4.1 wants in a near future to
>> > install newer versions of Camel, PAX, CXF, ... and use features file to
>> > install them. In this case, there will have a conflict with existing jars
>> > provided in the distro (system folder). What is the procedure to follow
>> to
>> > be able to use these newer versions ?
>> >
>> > Regards,
>> >
>> > Charles Moulliard
>> > Senior Enterprise Architect
>> > Apache Camel Committer
>> >
>> > *****************************
>> > blog : http://cmoulliard.blogspot.com
>> > twitter : http://twitter.com/cmoulliard
>> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>> >
>> > Apache Camel Group :
>> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>> >
>> >
>> > On Mon, Dec 14, 2009 at 8:54 AM, Jean-Baptiste Onofre <jb@nanthrax.net
>> >wrote:
>> >
>> >> Hi gentlemen,
>> >>
>> >> Yesterday I have upgraded SMX resources (component, feature, etc) to use
>> >> Apache Camel 2.1 as it has been released.
>> >>
>> >> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>> >>
>> >> I propose the following steps:
>> >>
>> >> 1/ I begin to prepare the 2009.02 components release. It includes:
>> >> - component-pom 4
>> >> - jbi-maven-plugin 4.2
>> >> These artifacts will be submit to a first vote.
>> >> - all components 2009.02
>> >> All components artifacts will be submit to a second vote.
>> >>
>> >> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
>> using
>> >> Karaf 1.2.0 and perform some test to check how it runs.
>> >>
>> >> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the
>> smx
>> >> 3 and smx 4 POMs to use the previously released components.
>> >> Two votes will be submitted: one for SMX3 and another one for SMX4.
>> >>
>> >> What do you think about that ?
>> >>
>> >> Regards
>> >> JB
>> >>
>> >
>>
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Charles Moulliard <cm...@gmail.com>.
Hi Gert,
This situation only occurs when we would like to update snapshot. In this
case, karaf will pick up the snapshot file of the system folder and not the
last from maven repository.
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Mon, Dec 14, 2009 at 10:24 AM, Gert Vanthienen <gert.vanthienen@gmail.com
> wrote:
> Charles,
>
> I'm not sure I understand what the problem is. If you install a newer
> version of a JAR in the runtime, the jar file in the /system folder is
> not being used, e.g. if you install CXF 2.2.6 in a few weeks, the
> existing bundle in /system will still have the 2.2.5 version so it
> should not interfere as long as the versions on the import/export
> headers are ok. There might be an issue with things like custom
> namespace handlers and things like that though. E.g. for camel, the
> camel-blueprint work should make it easier to use multiple versions of
> camel using the XML syntax.
>
> Actually, the only real solution is probably to have much shorter
> release cycles on the ServiceMix 4.x line, where we do a release
> quarterly or so to pick the latest and greatest bits of Camel, CXF,
> ActiveMQ, ...
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/12/14 Charles Moulliard <cm...@gmail.com>:
> > Excellent idea for SMX3 and SMX4.
> >
> > Concerning SMX 4.1 release, I propose that clarification is done for the
> > user concerning features and jars already installed in the distro (folder
> > system). The risk is that users using SMX4.1 wants in a near future to
> > install newer versions of Camel, PAX, CXF, ... and use features file to
> > install them. In this case, there will have a conflict with existing jars
> > provided in the distro (system folder). What is the procedure to follow
> to
> > be able to use these newer versions ?
> >
> > Regards,
> >
> > Charles Moulliard
> > Senior Enterprise Architect
> > Apache Camel Committer
> >
> > *****************************
> > blog : http://cmoulliard.blogspot.com
> > twitter : http://twitter.com/cmoulliard
> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >
> > Apache Camel Group :
> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >
> >
> > On Mon, Dec 14, 2009 at 8:54 AM, Jean-Baptiste Onofre <jb@nanthrax.net
> >wrote:
> >
> >> Hi gentlemen,
> >>
> >> Yesterday I have upgraded SMX resources (component, feature, etc) to use
> >> Apache Camel 2.1 as it has been released.
> >>
> >> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
> >>
> >> I propose the following steps:
> >>
> >> 1/ I begin to prepare the 2009.02 components release. It includes:
> >> - component-pom 4
> >> - jbi-maven-plugin 4.2
> >> These artifacts will be submit to a first vote.
> >> - all components 2009.02
> >> All components artifacts will be submit to a second vote.
> >>
> >> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
> using
> >> Karaf 1.2.0 and perform some test to check how it runs.
> >>
> >> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the
> smx
> >> 3 and smx 4 POMs to use the previously released components.
> >> Two votes will be submitted: one for SMX3 and another one for SMX4.
> >>
> >> What do you think about that ?
> >>
> >> Regards
> >> JB
> >>
> >
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Gert Vanthienen <ge...@gmail.com>.
Charles,
I'm not sure I understand what the problem is. If you install a newer
version of a JAR in the runtime, the jar file in the /system folder is
not being used, e.g. if you install CXF 2.2.6 in a few weeks, the
existing bundle in /system will still have the 2.2.5 version so it
should not interfere as long as the versions on the import/export
headers are ok. There might be an issue with things like custom
namespace handlers and things like that though. E.g. for camel, the
camel-blueprint work should make it easier to use multiple versions of
camel using the XML syntax.
Actually, the only real solution is probably to have much shorter
release cycles on the ServiceMix 4.x line, where we do a release
quarterly or so to pick the latest and greatest bits of Camel, CXF,
ActiveMQ, ...
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/12/14 Charles Moulliard <cm...@gmail.com>:
> Excellent idea for SMX3 and SMX4.
>
> Concerning SMX 4.1 release, I propose that clarification is done for the
> user concerning features and jars already installed in the distro (folder
> system). The risk is that users using SMX4.1 wants in a near future to
> install newer versions of Camel, PAX, CXF, ... and use features file to
> install them. In this case, there will have a conflict with existing jars
> provided in the distro (system folder). What is the procedure to follow to
> be able to use these newer versions ?
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Mon, Dec 14, 2009 at 8:54 AM, Jean-Baptiste Onofre <jb...@nanthrax.net>wrote:
>
>> Hi gentlemen,
>>
>> Yesterday I have upgraded SMX resources (component, feature, etc) to use
>> Apache Camel 2.1 as it has been released.
>>
>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>
>> I propose the following steps:
>>
>> 1/ I begin to prepare the 2009.02 components release. It includes:
>> - component-pom 4
>> - jbi-maven-plugin 4.2
>> These artifacts will be submit to a first vote.
>> - all components 2009.02
>> All components artifacts will be submit to a second vote.
>>
>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using
>> Karaf 1.2.0 and perform some test to check how it runs.
>>
>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the smx
>> 3 and smx 4 POMs to use the previously released components.
>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>
>> What do you think about that ?
>>
>> Regards
>> JB
>>
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Charles Moulliard <cm...@gmail.com>.
Excellent idea for SMX3 and SMX4.
Concerning SMX 4.1 release, I propose that clarification is done for the
user concerning features and jars already installed in the distro (folder
system). The risk is that users using SMX4.1 wants in a near future to
install newer versions of Camel, PAX, CXF, ... and use features file to
install them. In this case, there will have a conflict with existing jars
provided in the distro (system folder). What is the procedure to follow to
be able to use these newer versions ?
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Mon, Dec 14, 2009 at 8:54 AM, Jean-Baptiste Onofre <jb...@nanthrax.net>wrote:
> Hi gentlemen,
>
> Yesterday I have upgraded SMX resources (component, feature, etc) to use
> Apache Camel 2.1 as it has been released.
>
> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>
> I propose the following steps:
>
> 1/ I begin to prepare the 2009.02 components release. It includes:
> - component-pom 4
> - jbi-maven-plugin 4.2
> These artifacts will be submit to a first vote.
> - all components 2009.02
> All components artifacts will be submit to a second vote.
>
> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using
> Karaf 1.2.0 and perform some test to check how it runs.
>
> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the smx
> 3 and smx 4 POMs to use the previously released components.
> Two votes will be submitted: one for SMX3 and another one for SMX4.
>
> What do you think about that ?
>
> Regards
> JB
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Charles Moulliard <cm...@gmail.com>.
I have prepare patch for karaf and servicemix in order to use same version
of servicemix jetty bundle between karaf, SMX and camel and use http vesion
of karaf instead of web, web-core of SMX based on old version of PAX-WEB
https://issues.apache.org/jira/browse/FELIX-1949
https://issues.apache.org/activemq/browse/SMX4-446
Feel free to use them in the next build
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Thu, Dec 17, 2009 at 7:35 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Thanks Gert,
>
> I'm on a customer site today but I will be able to help you this evening if
> you need.
>
> Regards
> JB
> -----Original Message-----
> From: Gert Vanthienen <ge...@gmail.com>
> Date: Thu, 17 Dec 2009 07:07:39
> To: <de...@servicemix.apache.org>
> Subject: Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
>
> L.S.,
>
> I have readied plugins and components for release in the meanwhile, so
> I'll try to do those two today so we only have nmr/features left to do
> once fileinstall is done.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/12/17 Guillaume Nodet <gn...@gmail.com>:
> > Yeah, I have fixed a few pending issues in fileinstall today.
> > Hopefully it can be released this week or early next week.
> >
> > On Wed, Dec 16, 2009 at 14:31, Gert Vanthienen
> > <ge...@gmail.com> wrote:
> >> L.S.,
> >>
> >> This sounds like a pretty important issue to me - wouldn't that impact
> >> anybody's who tries to run ServiceMix whenever the container gets
> >> restarted? Not sure if it is possible at the moment off course, but
> >> wouldn't it be better to at least do a new minor fileinstall + karaf
> >> release so we can tell people that run into this problem to switch to
> >> equinox - as soon as felix releases a new version of the framework, we
> >> can then upgrade that again.
> >>
> >> Regards,
> >>
> >> Gert Vanthienen
> >> ------------------------
> >> Open Source SOA: http://fusesource.com
> >> Blog: http://gertvanthienen.blogspot.com/
> >>
> >>
> >>
> >> 2009/12/15 Chris Custine <ch...@gmail.com>:
> >>> Without the fix, many of the example projects (or any other bundles
> that
> >>> import packages from a startlevel 60 bundle) will fail to resolve on
> restart
> >>> if you originally deployed using fileinstall. The reason is that some
> >>> recent changes to fileinstall cause it to start its managed bundles
> when
> >>> fileinstall starts, which is startlevel 11.
> >>>
> >>> The fix to fileinstall works with Equinox, but it uncovered a bug in
> Felix
> >>> framework bundle (https://issues.apache.org/jira/browse/FELIX-1929).
> Until
> >>> framework bundle is released with the fix, the only solution in Felix
> is to
> >>> refresh the fileinstall managed bundles after startlevel 60 bundles are
> >>> resolved. Another alternative is to switch to Equinox.
> >>>
> >>> If we don't release fileinstall with this fix, the only option for both
> >>> Equinox and Felix is the refresh option. I'm OK with releasing either
> way,
> >>> I just wanted to make sure everyone understood the issue before we go
> ahead.
> >>>
> >>> Chris
> >>>
> >>> --
> >>> Chris Custine
> >>> FUSESource :: http://fusesource.com
> >>> My Blog :: http://blog.organicelement.com
> >>> Apache ServiceMix :: http://servicemix.apache.org
> >>> Apache Directory Server :: http://directory.apache.org
> >>>
> >>>
> >>> On Tue, Dec 15, 2009 at 10:57 AM, Guillaume Nodet <gn...@gmail.com>
> wrote:
> >>>
> >>>> I don't think we should wait on this fix. It would also require a
> >>>> release of felix framework because Chris' patch raised a buf in the
> >>>> framework.
> >>>> What kind of problems would our users run into if we release without
> the
> >>>> fix ?
> >>>>
> >>>> On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen
> >>>> <ge...@gmail.com> wrote:
> >>>> > L.S.,
> >>>> >
> >>>> > For the SMX 4.1 release, I think we have a problem with
> >>>> > https://issues.apache.org/jira/browse/FELIX-1928. This issue in
> >>>> > FileInstall has been fixed after the Karaf 1.2.0 release had been
> cut,
> >>>> > but it could have quite a bit of impact on our users. It might make
> >>>> > more sense to work towards a new release of FileInstall and Karaf
> >>>> > first before cutting the SMX 4.1 release, but any suggestions or
> ideas
> >>>> > are welcome.
> >>>> >
> >>>> > For the plugins/components, we can still go ahead and release those.
> >>>> > I can release those tomorrow - I have a few hours available to cut
> the
> >>>> > release tomorrow afternoon, unless anyone knows about outstanding
> >>>> > issues that need to go into the release before we can go ahead.
> >>>> >
> >>>> > Regards,
> >>>> >
> >>>> > Gert Vanthienen
> >>>> > ------------------------
> >>>> > Open Source SOA: http://fusesource.com
> >>>> > Blog: http://gertvanthienen.blogspot.com/
> >>>> >
> >>>> >
> >>>> >
> >>>> > 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
> >>>> >> Gert,
> >>>> >>
> >>>> >> it makes sense yes :)
> >>>> >>
> >>>> >> I begin the process.
> >>>> >>
> >>>> >> Regards
> >>>> >> JB
> >>>> >>
> >>>> >> Gert Vanthienen wrote:
> >>>> >>>
> >>>> >>> Jean-Baptiste,
> >>>> >>>
> >>>> >>> How about doing a big, bulky 4.1 release this week with components
> +
> >>>> >>> nmr + features in it and then follow up with a servicemix 3.3.2
> >>>> >>> release next week, reusing the same component set? That way, we
> can
> >>>> >>> announce a new release both weeks ;)
> >>>> >>>
> >>>> >>> Regards,
> >>>> >>>
> >>>> >>> Gert Vanthienen
> >>>> >>> ------------------------
> >>>> >>> Open Source SOA: http://fusesource.com
> >>>> >>> Blog: http://gertvanthienen.blogspot.com/
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
> >>>> >>>>
> >>>> >>>> Hi gentlemen,
> >>>> >>>>
> >>>> >>>> Yesterday I have upgraded SMX resources (component, feature, etc)
> to
> >>>> use
> >>>> >>>> Apache Camel 2.1 as it has been released.
> >>>> >>>>
> >>>> >>>> I think that we are not so far from a new SMX 3.3.2 and 4.1
> release.
> >>>> >>>>
> >>>> >>>> I propose the following steps:
> >>>> >>>>
> >>>> >>>> 1/ I begin to prepare the 2009.02 components release. It
> includes:
> >>>> >>>> - component-pom 4
> >>>> >>>> - jbi-maven-plugin 4.2
> >>>> >>>> These artifacts will be submit to a first vote.
> >>>> >>>> - all components 2009.02
> >>>> >>>> All components artifacts will be submit to a second vote.
> >>>> >>>>
> >>>> >>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT
> assembly
> >>>> using
> >>>> >>>> Karaf 1.2.0 and perform some test to check how it runs.
> >>>> >>>>
> >>>> >>>> 2/ once these steps 1 and 1 bis have been performed, we can
> upgrade
> >>>> the
> >>>> >>>> smx
> >>>> >>>> 3 and smx 4 POMs to use the previously released components.
> >>>> >>>> Two votes will be submitted: one for SMX3 and another one for
> SMX4.
> >>>> >>>>
> >>>> >>>> What do you think about that ?
> >>>> >>>>
> >>>> >>>> Regards
> >>>> >>>> JB
> >>>> >>>>
> >>>> >>
> >>>> >> --
> >>>> >> Jean-Baptiste Onofré
> >>>> >> ---------------------------------
> >>>> >> HomePage
> >>>> >> http://www.nanthrax.net
> >>>> >> ---------------------------------
> >>>> >> Contacts
> >>>> >> jbonofre@apache.org
> >>>> >> jb@nanthrax.net
> >>>> >> ---------------------------------
> >>>> >> OpenSource
> >>>> >> BuildProcess/AutoDeploy
> >>>> >> http://buildprocess.sourceforge.net
> >>>> >> Apache ServiceMix
> >>>> >> http://servicemix.apache.org
> >>>> >> -----------------------------------
> >>>> >> PGP : 17D4F086
> >>>> >>
> >>>> >
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Cheers,
> >>>> Guillaume Nodet
> >>>> ------------------------
> >>>> Blog: http://gnodet.blogspot.com/
> >>>> ------------------------
> >>>> Open Source SOA
> >>>> http://fusesource.com
> >>>>
> >>>
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
> >
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks Gert,
I'm on a customer site today but I will be able to help you this evening if you need.
Regards
JB
-----Original Message-----
From: Gert Vanthienen <ge...@gmail.com>
Date: Thu, 17 Dec 2009 07:07:39
To: <de...@servicemix.apache.org>
Subject: Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
L.S.,
I have readied plugins and components for release in the meanwhile, so
I'll try to do those two today so we only have nmr/features left to do
once fileinstall is done.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/12/17 Guillaume Nodet <gn...@gmail.com>:
> Yeah, I have fixed a few pending issues in fileinstall today.
> Hopefully it can be released this week or early next week.
>
> On Wed, Dec 16, 2009 at 14:31, Gert Vanthienen
> <ge...@gmail.com> wrote:
>> L.S.,
>>
>> This sounds like a pretty important issue to me - wouldn't that impact
>> anybody's who tries to run ServiceMix whenever the container gets
>> restarted? Not sure if it is possible at the moment off course, but
>> wouldn't it be better to at least do a new minor fileinstall + karaf
>> release so we can tell people that run into this problem to switch to
>> equinox - as soon as felix releases a new version of the framework, we
>> can then upgrade that again.
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> Open Source SOA: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> 2009/12/15 Chris Custine <ch...@gmail.com>:
>>> Without the fix, many of the example projects (or any other bundles that
>>> import packages from a startlevel 60 bundle) will fail to resolve on restart
>>> if you originally deployed using fileinstall. The reason is that some
>>> recent changes to fileinstall cause it to start its managed bundles when
>>> fileinstall starts, which is startlevel 11.
>>>
>>> The fix to fileinstall works with Equinox, but it uncovered a bug in Felix
>>> framework bundle (https://issues.apache.org/jira/browse/FELIX-1929). Until
>>> framework bundle is released with the fix, the only solution in Felix is to
>>> refresh the fileinstall managed bundles after startlevel 60 bundles are
>>> resolved. Another alternative is to switch to Equinox.
>>>
>>> If we don't release fileinstall with this fix, the only option for both
>>> Equinox and Felix is the refresh option. I'm OK with releasing either way,
>>> I just wanted to make sure everyone understood the issue before we go ahead.
>>>
>>> Chris
>>>
>>> --
>>> Chris Custine
>>> FUSESource :: http://fusesource.com
>>> My Blog :: http://blog.organicelement.com
>>> Apache ServiceMix :: http://servicemix.apache.org
>>> Apache Directory Server :: http://directory.apache.org
>>>
>>>
>>> On Tue, Dec 15, 2009 at 10:57 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>>>
>>>> I don't think we should wait on this fix. It would also require a
>>>> release of felix framework because Chris' patch raised a buf in the
>>>> framework.
>>>> What kind of problems would our users run into if we release without the
>>>> fix ?
>>>>
>>>> On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen
>>>> <ge...@gmail.com> wrote:
>>>> > L.S.,
>>>> >
>>>> > For the SMX 4.1 release, I think we have a problem with
>>>> > https://issues.apache.org/jira/browse/FELIX-1928. This issue in
>>>> > FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
>>>> > but it could have quite a bit of impact on our users. It might make
>>>> > more sense to work towards a new release of FileInstall and Karaf
>>>> > first before cutting the SMX 4.1 release, but any suggestions or ideas
>>>> > are welcome.
>>>> >
>>>> > For the plugins/components, we can still go ahead and release those.
>>>> > I can release those tomorrow - I have a few hours available to cut the
>>>> > release tomorrow afternoon, unless anyone knows about outstanding
>>>> > issues that need to go into the release before we can go ahead.
>>>> >
>>>> > Regards,
>>>> >
>>>> > Gert Vanthienen
>>>> > ------------------------
>>>> > Open Source SOA: http://fusesource.com
>>>> > Blog: http://gertvanthienen.blogspot.com/
>>>> >
>>>> >
>>>> >
>>>> > 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>>> >> Gert,
>>>> >>
>>>> >> it makes sense yes :)
>>>> >>
>>>> >> I begin the process.
>>>> >>
>>>> >> Regards
>>>> >> JB
>>>> >>
>>>> >> Gert Vanthienen wrote:
>>>> >>>
>>>> >>> Jean-Baptiste,
>>>> >>>
>>>> >>> How about doing a big, bulky 4.1 release this week with components +
>>>> >>> nmr + features in it and then follow up with a servicemix 3.3.2
>>>> >>> release next week, reusing the same component set? That way, we can
>>>> >>> announce a new release both weeks ;)
>>>> >>>
>>>> >>> Regards,
>>>> >>>
>>>> >>> Gert Vanthienen
>>>> >>> ------------------------
>>>> >>> Open Source SOA: http://fusesource.com
>>>> >>> Blog: http://gertvanthienen.blogspot.com/
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>>> >>>>
>>>> >>>> Hi gentlemen,
>>>> >>>>
>>>> >>>> Yesterday I have upgraded SMX resources (component, feature, etc) to
>>>> use
>>>> >>>> Apache Camel 2.1 as it has been released.
>>>> >>>>
>>>> >>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>>> >>>>
>>>> >>>> I propose the following steps:
>>>> >>>>
>>>> >>>> 1/ I begin to prepare the 2009.02 components release. It includes:
>>>> >>>> - component-pom 4
>>>> >>>> - jbi-maven-plugin 4.2
>>>> >>>> These artifacts will be submit to a first vote.
>>>> >>>> - all components 2009.02
>>>> >>>> All components artifacts will be submit to a second vote.
>>>> >>>>
>>>> >>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
>>>> using
>>>> >>>> Karaf 1.2.0 and perform some test to check how it runs.
>>>> >>>>
>>>> >>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade
>>>> the
>>>> >>>> smx
>>>> >>>> 3 and smx 4 POMs to use the previously released components.
>>>> >>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>>> >>>>
>>>> >>>> What do you think about that ?
>>>> >>>>
>>>> >>>> Regards
>>>> >>>> JB
>>>> >>>>
>>>> >>
>>>> >> --
>>>> >> Jean-Baptiste Onofré
>>>> >> ---------------------------------
>>>> >> HomePage
>>>> >> http://www.nanthrax.net
>>>> >> ---------------------------------
>>>> >> Contacts
>>>> >> jbonofre@apache.org
>>>> >> jb@nanthrax.net
>>>> >> ---------------------------------
>>>> >> OpenSource
>>>> >> BuildProcess/AutoDeploy
>>>> >> http://buildprocess.sourceforge.net
>>>> >> Apache ServiceMix
>>>> >> http://servicemix.apache.org
>>>> >> -----------------------------------
>>>> >> PGP : 17D4F086
>>>> >>
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Guillaume Nodet
>>>> ------------------------
>>>> Blog: http://gnodet.blogspot.com/
>>>> ------------------------
>>>> Open Source SOA
>>>> http://fusesource.com
>>>>
>>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
I have readied plugins and components for release in the meanwhile, so
I'll try to do those two today so we only have nmr/features left to do
once fileinstall is done.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/12/17 Guillaume Nodet <gn...@gmail.com>:
> Yeah, I have fixed a few pending issues in fileinstall today.
> Hopefully it can be released this week or early next week.
>
> On Wed, Dec 16, 2009 at 14:31, Gert Vanthienen
> <ge...@gmail.com> wrote:
>> L.S.,
>>
>> This sounds like a pretty important issue to me - wouldn't that impact
>> anybody's who tries to run ServiceMix whenever the container gets
>> restarted? Not sure if it is possible at the moment off course, but
>> wouldn't it be better to at least do a new minor fileinstall + karaf
>> release so we can tell people that run into this problem to switch to
>> equinox - as soon as felix releases a new version of the framework, we
>> can then upgrade that again.
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> Open Source SOA: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> 2009/12/15 Chris Custine <ch...@gmail.com>:
>>> Without the fix, many of the example projects (or any other bundles that
>>> import packages from a startlevel 60 bundle) will fail to resolve on restart
>>> if you originally deployed using fileinstall. The reason is that some
>>> recent changes to fileinstall cause it to start its managed bundles when
>>> fileinstall starts, which is startlevel 11.
>>>
>>> The fix to fileinstall works with Equinox, but it uncovered a bug in Felix
>>> framework bundle (https://issues.apache.org/jira/browse/FELIX-1929). Until
>>> framework bundle is released with the fix, the only solution in Felix is to
>>> refresh the fileinstall managed bundles after startlevel 60 bundles are
>>> resolved. Another alternative is to switch to Equinox.
>>>
>>> If we don't release fileinstall with this fix, the only option for both
>>> Equinox and Felix is the refresh option. I'm OK with releasing either way,
>>> I just wanted to make sure everyone understood the issue before we go ahead.
>>>
>>> Chris
>>>
>>> --
>>> Chris Custine
>>> FUSESource :: http://fusesource.com
>>> My Blog :: http://blog.organicelement.com
>>> Apache ServiceMix :: http://servicemix.apache.org
>>> Apache Directory Server :: http://directory.apache.org
>>>
>>>
>>> On Tue, Dec 15, 2009 at 10:57 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>>>
>>>> I don't think we should wait on this fix. It would also require a
>>>> release of felix framework because Chris' patch raised a buf in the
>>>> framework.
>>>> What kind of problems would our users run into if we release without the
>>>> fix ?
>>>>
>>>> On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen
>>>> <ge...@gmail.com> wrote:
>>>> > L.S.,
>>>> >
>>>> > For the SMX 4.1 release, I think we have a problem with
>>>> > https://issues.apache.org/jira/browse/FELIX-1928. This issue in
>>>> > FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
>>>> > but it could have quite a bit of impact on our users. It might make
>>>> > more sense to work towards a new release of FileInstall and Karaf
>>>> > first before cutting the SMX 4.1 release, but any suggestions or ideas
>>>> > are welcome.
>>>> >
>>>> > For the plugins/components, we can still go ahead and release those.
>>>> > I can release those tomorrow - I have a few hours available to cut the
>>>> > release tomorrow afternoon, unless anyone knows about outstanding
>>>> > issues that need to go into the release before we can go ahead.
>>>> >
>>>> > Regards,
>>>> >
>>>> > Gert Vanthienen
>>>> > ------------------------
>>>> > Open Source SOA: http://fusesource.com
>>>> > Blog: http://gertvanthienen.blogspot.com/
>>>> >
>>>> >
>>>> >
>>>> > 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>>> >> Gert,
>>>> >>
>>>> >> it makes sense yes :)
>>>> >>
>>>> >> I begin the process.
>>>> >>
>>>> >> Regards
>>>> >> JB
>>>> >>
>>>> >> Gert Vanthienen wrote:
>>>> >>>
>>>> >>> Jean-Baptiste,
>>>> >>>
>>>> >>> How about doing a big, bulky 4.1 release this week with components +
>>>> >>> nmr + features in it and then follow up with a servicemix 3.3.2
>>>> >>> release next week, reusing the same component set? That way, we can
>>>> >>> announce a new release both weeks ;)
>>>> >>>
>>>> >>> Regards,
>>>> >>>
>>>> >>> Gert Vanthienen
>>>> >>> ------------------------
>>>> >>> Open Source SOA: http://fusesource.com
>>>> >>> Blog: http://gertvanthienen.blogspot.com/
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>>> >>>>
>>>> >>>> Hi gentlemen,
>>>> >>>>
>>>> >>>> Yesterday I have upgraded SMX resources (component, feature, etc) to
>>>> use
>>>> >>>> Apache Camel 2.1 as it has been released.
>>>> >>>>
>>>> >>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>>> >>>>
>>>> >>>> I propose the following steps:
>>>> >>>>
>>>> >>>> 1/ I begin to prepare the 2009.02 components release. It includes:
>>>> >>>> - component-pom 4
>>>> >>>> - jbi-maven-plugin 4.2
>>>> >>>> These artifacts will be submit to a first vote.
>>>> >>>> - all components 2009.02
>>>> >>>> All components artifacts will be submit to a second vote.
>>>> >>>>
>>>> >>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
>>>> using
>>>> >>>> Karaf 1.2.0 and perform some test to check how it runs.
>>>> >>>>
>>>> >>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade
>>>> the
>>>> >>>> smx
>>>> >>>> 3 and smx 4 POMs to use the previously released components.
>>>> >>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>>> >>>>
>>>> >>>> What do you think about that ?
>>>> >>>>
>>>> >>>> Regards
>>>> >>>> JB
>>>> >>>>
>>>> >>
>>>> >> --
>>>> >> Jean-Baptiste Onofré
>>>> >> ---------------------------------
>>>> >> HomePage
>>>> >> http://www.nanthrax.net
>>>> >> ---------------------------------
>>>> >> Contacts
>>>> >> jbonofre@apache.org
>>>> >> jb@nanthrax.net
>>>> >> ---------------------------------
>>>> >> OpenSource
>>>> >> BuildProcess/AutoDeploy
>>>> >> http://buildprocess.sourceforge.net
>>>> >> Apache ServiceMix
>>>> >> http://servicemix.apache.org
>>>> >> -----------------------------------
>>>> >> PGP : 17D4F086
>>>> >>
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Guillaume Nodet
>>>> ------------------------
>>>> Blog: http://gnodet.blogspot.com/
>>>> ------------------------
>>>> Open Source SOA
>>>> http://fusesource.com
>>>>
>>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Guillaume Nodet <gn...@gmail.com>.
Yeah, I have fixed a few pending issues in fileinstall today.
Hopefully it can be released this week or early next week.
On Wed, Dec 16, 2009 at 14:31, Gert Vanthienen
<ge...@gmail.com> wrote:
> L.S.,
>
> This sounds like a pretty important issue to me - wouldn't that impact
> anybody's who tries to run ServiceMix whenever the container gets
> restarted? Not sure if it is possible at the moment off course, but
> wouldn't it be better to at least do a new minor fileinstall + karaf
> release so we can tell people that run into this problem to switch to
> equinox - as soon as felix releases a new version of the framework, we
> can then upgrade that again.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/12/15 Chris Custine <ch...@gmail.com>:
>> Without the fix, many of the example projects (or any other bundles that
>> import packages from a startlevel 60 bundle) will fail to resolve on restart
>> if you originally deployed using fileinstall. The reason is that some
>> recent changes to fileinstall cause it to start its managed bundles when
>> fileinstall starts, which is startlevel 11.
>>
>> The fix to fileinstall works with Equinox, but it uncovered a bug in Felix
>> framework bundle (https://issues.apache.org/jira/browse/FELIX-1929). Until
>> framework bundle is released with the fix, the only solution in Felix is to
>> refresh the fileinstall managed bundles after startlevel 60 bundles are
>> resolved. Another alternative is to switch to Equinox.
>>
>> If we don't release fileinstall with this fix, the only option for both
>> Equinox and Felix is the refresh option. I'm OK with releasing either way,
>> I just wanted to make sure everyone understood the issue before we go ahead.
>>
>> Chris
>>
>> --
>> Chris Custine
>> FUSESource :: http://fusesource.com
>> My Blog :: http://blog.organicelement.com
>> Apache ServiceMix :: http://servicemix.apache.org
>> Apache Directory Server :: http://directory.apache.org
>>
>>
>> On Tue, Dec 15, 2009 at 10:57 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>>
>>> I don't think we should wait on this fix. It would also require a
>>> release of felix framework because Chris' patch raised a buf in the
>>> framework.
>>> What kind of problems would our users run into if we release without the
>>> fix ?
>>>
>>> On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen
>>> <ge...@gmail.com> wrote:
>>> > L.S.,
>>> >
>>> > For the SMX 4.1 release, I think we have a problem with
>>> > https://issues.apache.org/jira/browse/FELIX-1928. This issue in
>>> > FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
>>> > but it could have quite a bit of impact on our users. It might make
>>> > more sense to work towards a new release of FileInstall and Karaf
>>> > first before cutting the SMX 4.1 release, but any suggestions or ideas
>>> > are welcome.
>>> >
>>> > For the plugins/components, we can still go ahead and release those.
>>> > I can release those tomorrow - I have a few hours available to cut the
>>> > release tomorrow afternoon, unless anyone knows about outstanding
>>> > issues that need to go into the release before we can go ahead.
>>> >
>>> > Regards,
>>> >
>>> > Gert Vanthienen
>>> > ------------------------
>>> > Open Source SOA: http://fusesource.com
>>> > Blog: http://gertvanthienen.blogspot.com/
>>> >
>>> >
>>> >
>>> > 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>> >> Gert,
>>> >>
>>> >> it makes sense yes :)
>>> >>
>>> >> I begin the process.
>>> >>
>>> >> Regards
>>> >> JB
>>> >>
>>> >> Gert Vanthienen wrote:
>>> >>>
>>> >>> Jean-Baptiste,
>>> >>>
>>> >>> How about doing a big, bulky 4.1 release this week with components +
>>> >>> nmr + features in it and then follow up with a servicemix 3.3.2
>>> >>> release next week, reusing the same component set? That way, we can
>>> >>> announce a new release both weeks ;)
>>> >>>
>>> >>> Regards,
>>> >>>
>>> >>> Gert Vanthienen
>>> >>> ------------------------
>>> >>> Open Source SOA: http://fusesource.com
>>> >>> Blog: http://gertvanthienen.blogspot.com/
>>> >>>
>>> >>>
>>> >>>
>>> >>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>> >>>>
>>> >>>> Hi gentlemen,
>>> >>>>
>>> >>>> Yesterday I have upgraded SMX resources (component, feature, etc) to
>>> use
>>> >>>> Apache Camel 2.1 as it has been released.
>>> >>>>
>>> >>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>> >>>>
>>> >>>> I propose the following steps:
>>> >>>>
>>> >>>> 1/ I begin to prepare the 2009.02 components release. It includes:
>>> >>>> - component-pom 4
>>> >>>> - jbi-maven-plugin 4.2
>>> >>>> These artifacts will be submit to a first vote.
>>> >>>> - all components 2009.02
>>> >>>> All components artifacts will be submit to a second vote.
>>> >>>>
>>> >>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
>>> using
>>> >>>> Karaf 1.2.0 and perform some test to check how it runs.
>>> >>>>
>>> >>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade
>>> the
>>> >>>> smx
>>> >>>> 3 and smx 4 POMs to use the previously released components.
>>> >>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>> >>>>
>>> >>>> What do you think about that ?
>>> >>>>
>>> >>>> Regards
>>> >>>> JB
>>> >>>>
>>> >>
>>> >> --
>>> >> Jean-Baptiste Onofré
>>> >> ---------------------------------
>>> >> HomePage
>>> >> http://www.nanthrax.net
>>> >> ---------------------------------
>>> >> Contacts
>>> >> jbonofre@apache.org
>>> >> jb@nanthrax.net
>>> >> ---------------------------------
>>> >> OpenSource
>>> >> BuildProcess/AutoDeploy
>>> >> http://buildprocess.sourceforge.net
>>> >> Apache ServiceMix
>>> >> http://servicemix.apache.org
>>> >> -----------------------------------
>>> >> PGP : 17D4F086
>>> >>
>>> >
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>>
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
This sounds like a pretty important issue to me - wouldn't that impact
anybody's who tries to run ServiceMix whenever the container gets
restarted? Not sure if it is possible at the moment off course, but
wouldn't it be better to at least do a new minor fileinstall + karaf
release so we can tell people that run into this problem to switch to
equinox - as soon as felix releases a new version of the framework, we
can then upgrade that again.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/12/15 Chris Custine <ch...@gmail.com>:
> Without the fix, many of the example projects (or any other bundles that
> import packages from a startlevel 60 bundle) will fail to resolve on restart
> if you originally deployed using fileinstall. The reason is that some
> recent changes to fileinstall cause it to start its managed bundles when
> fileinstall starts, which is startlevel 11.
>
> The fix to fileinstall works with Equinox, but it uncovered a bug in Felix
> framework bundle (https://issues.apache.org/jira/browse/FELIX-1929). Until
> framework bundle is released with the fix, the only solution in Felix is to
> refresh the fileinstall managed bundles after startlevel 60 bundles are
> resolved. Another alternative is to switch to Equinox.
>
> If we don't release fileinstall with this fix, the only option for both
> Equinox and Felix is the refresh option. I'm OK with releasing either way,
> I just wanted to make sure everyone understood the issue before we go ahead.
>
> Chris
>
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Directory Server :: http://directory.apache.org
>
>
> On Tue, Dec 15, 2009 at 10:57 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>
>> I don't think we should wait on this fix. It would also require a
>> release of felix framework because Chris' patch raised a buf in the
>> framework.
>> What kind of problems would our users run into if we release without the
>> fix ?
>>
>> On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen
>> <ge...@gmail.com> wrote:
>> > L.S.,
>> >
>> > For the SMX 4.1 release, I think we have a problem with
>> > https://issues.apache.org/jira/browse/FELIX-1928. This issue in
>> > FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
>> > but it could have quite a bit of impact on our users. It might make
>> > more sense to work towards a new release of FileInstall and Karaf
>> > first before cutting the SMX 4.1 release, but any suggestions or ideas
>> > are welcome.
>> >
>> > For the plugins/components, we can still go ahead and release those.
>> > I can release those tomorrow - I have a few hours available to cut the
>> > release tomorrow afternoon, unless anyone knows about outstanding
>> > issues that need to go into the release before we can go ahead.
>> >
>> > Regards,
>> >
>> > Gert Vanthienen
>> > ------------------------
>> > Open Source SOA: http://fusesource.com
>> > Blog: http://gertvanthienen.blogspot.com/
>> >
>> >
>> >
>> > 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>> >> Gert,
>> >>
>> >> it makes sense yes :)
>> >>
>> >> I begin the process.
>> >>
>> >> Regards
>> >> JB
>> >>
>> >> Gert Vanthienen wrote:
>> >>>
>> >>> Jean-Baptiste,
>> >>>
>> >>> How about doing a big, bulky 4.1 release this week with components +
>> >>> nmr + features in it and then follow up with a servicemix 3.3.2
>> >>> release next week, reusing the same component set? That way, we can
>> >>> announce a new release both weeks ;)
>> >>>
>> >>> Regards,
>> >>>
>> >>> Gert Vanthienen
>> >>> ------------------------
>> >>> Open Source SOA: http://fusesource.com
>> >>> Blog: http://gertvanthienen.blogspot.com/
>> >>>
>> >>>
>> >>>
>> >>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>> >>>>
>> >>>> Hi gentlemen,
>> >>>>
>> >>>> Yesterday I have upgraded SMX resources (component, feature, etc) to
>> use
>> >>>> Apache Camel 2.1 as it has been released.
>> >>>>
>> >>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>> >>>>
>> >>>> I propose the following steps:
>> >>>>
>> >>>> 1/ I begin to prepare the 2009.02 components release. It includes:
>> >>>> - component-pom 4
>> >>>> - jbi-maven-plugin 4.2
>> >>>> These artifacts will be submit to a first vote.
>> >>>> - all components 2009.02
>> >>>> All components artifacts will be submit to a second vote.
>> >>>>
>> >>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
>> using
>> >>>> Karaf 1.2.0 and perform some test to check how it runs.
>> >>>>
>> >>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade
>> the
>> >>>> smx
>> >>>> 3 and smx 4 POMs to use the previously released components.
>> >>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>> >>>>
>> >>>> What do you think about that ?
>> >>>>
>> >>>> Regards
>> >>>> JB
>> >>>>
>> >>
>> >> --
>> >> Jean-Baptiste Onofré
>> >> ---------------------------------
>> >> HomePage
>> >> http://www.nanthrax.net
>> >> ---------------------------------
>> >> Contacts
>> >> jbonofre@apache.org
>> >> jb@nanthrax.net
>> >> ---------------------------------
>> >> OpenSource
>> >> BuildProcess/AutoDeploy
>> >> http://buildprocess.sourceforge.net
>> >> Apache ServiceMix
>> >> http://servicemix.apache.org
>> >> -----------------------------------
>> >> PGP : 17D4F086
>> >>
>> >
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Chris Custine <ch...@gmail.com>.
Without the fix, many of the example projects (or any other bundles that
import packages from a startlevel 60 bundle) will fail to resolve on restart
if you originally deployed using fileinstall. The reason is that some
recent changes to fileinstall cause it to start its managed bundles when
fileinstall starts, which is startlevel 11.
The fix to fileinstall works with Equinox, but it uncovered a bug in Felix
framework bundle (https://issues.apache.org/jira/browse/FELIX-1929). Until
framework bundle is released with the fix, the only solution in Felix is to
refresh the fileinstall managed bundles after startlevel 60 bundles are
resolved. Another alternative is to switch to Equinox.
If we don't release fileinstall with this fix, the only option for both
Equinox and Felix is the refresh option. I'm OK with releasing either way,
I just wanted to make sure everyone understood the issue before we go ahead.
Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Directory Server :: http://directory.apache.org
On Tue, Dec 15, 2009 at 10:57 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> I don't think we should wait on this fix. It would also require a
> release of felix framework because Chris' patch raised a buf in the
> framework.
> What kind of problems would our users run into if we release without the
> fix ?
>
> On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen
> <ge...@gmail.com> wrote:
> > L.S.,
> >
> > For the SMX 4.1 release, I think we have a problem with
> > https://issues.apache.org/jira/browse/FELIX-1928. This issue in
> > FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
> > but it could have quite a bit of impact on our users. It might make
> > more sense to work towards a new release of FileInstall and Karaf
> > first before cutting the SMX 4.1 release, but any suggestions or ideas
> > are welcome.
> >
> > For the plugins/components, we can still go ahead and release those.
> > I can release those tomorrow - I have a few hours available to cut the
> > release tomorrow afternoon, unless anyone knows about outstanding
> > issues that need to go into the release before we can go ahead.
> >
> > Regards,
> >
> > Gert Vanthienen
> > ------------------------
> > Open Source SOA: http://fusesource.com
> > Blog: http://gertvanthienen.blogspot.com/
> >
> >
> >
> > 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
> >> Gert,
> >>
> >> it makes sense yes :)
> >>
> >> I begin the process.
> >>
> >> Regards
> >> JB
> >>
> >> Gert Vanthienen wrote:
> >>>
> >>> Jean-Baptiste,
> >>>
> >>> How about doing a big, bulky 4.1 release this week with components +
> >>> nmr + features in it and then follow up with a servicemix 3.3.2
> >>> release next week, reusing the same component set? That way, we can
> >>> announce a new release both weeks ;)
> >>>
> >>> Regards,
> >>>
> >>> Gert Vanthienen
> >>> ------------------------
> >>> Open Source SOA: http://fusesource.com
> >>> Blog: http://gertvanthienen.blogspot.com/
> >>>
> >>>
> >>>
> >>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
> >>>>
> >>>> Hi gentlemen,
> >>>>
> >>>> Yesterday I have upgraded SMX resources (component, feature, etc) to
> use
> >>>> Apache Camel 2.1 as it has been released.
> >>>>
> >>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
> >>>>
> >>>> I propose the following steps:
> >>>>
> >>>> 1/ I begin to prepare the 2009.02 components release. It includes:
> >>>> - component-pom 4
> >>>> - jbi-maven-plugin 4.2
> >>>> These artifacts will be submit to a first vote.
> >>>> - all components 2009.02
> >>>> All components artifacts will be submit to a second vote.
> >>>>
> >>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly
> using
> >>>> Karaf 1.2.0 and perform some test to check how it runs.
> >>>>
> >>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade
> the
> >>>> smx
> >>>> 3 and smx 4 POMs to use the previously released components.
> >>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
> >>>>
> >>>> What do you think about that ?
> >>>>
> >>>> Regards
> >>>> JB
> >>>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> ---------------------------------
> >> HomePage
> >> http://www.nanthrax.net
> >> ---------------------------------
> >> Contacts
> >> jbonofre@apache.org
> >> jb@nanthrax.net
> >> ---------------------------------
> >> OpenSource
> >> BuildProcess/AutoDeploy
> >> http://buildprocess.sourceforge.net
> >> Apache ServiceMix
> >> http://servicemix.apache.org
> >> -----------------------------------
> >> PGP : 17D4F086
> >>
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Guillaume Nodet <gn...@gmail.com>.
I don't think we should wait on this fix. It would also require a
release of felix framework because Chris' patch raised a buf in the
framework.
What kind of problems would our users run into if we release without the fix ?
On Tue, Dec 15, 2009 at 18:14, Gert Vanthienen
<ge...@gmail.com> wrote:
> L.S.,
>
> For the SMX 4.1 release, I think we have a problem with
> https://issues.apache.org/jira/browse/FELIX-1928. This issue in
> FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
> but it could have quite a bit of impact on our users. It might make
> more sense to work towards a new release of FileInstall and Karaf
> first before cutting the SMX 4.1 release, but any suggestions or ideas
> are welcome.
>
> For the plugins/components, we can still go ahead and release those.
> I can release those tomorrow - I have a few hours available to cut the
> release tomorrow afternoon, unless anyone knows about outstanding
> issues that need to go into the release before we can go ahead.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>> Gert,
>>
>> it makes sense yes :)
>>
>> I begin the process.
>>
>> Regards
>> JB
>>
>> Gert Vanthienen wrote:
>>>
>>> Jean-Baptiste,
>>>
>>> How about doing a big, bulky 4.1 release this week with components +
>>> nmr + features in it and then follow up with a servicemix 3.3.2
>>> release next week, reusing the same component set? That way, we can
>>> announce a new release both weeks ;)
>>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>> Blog: http://gertvanthienen.blogspot.com/
>>>
>>>
>>>
>>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>>>
>>>> Hi gentlemen,
>>>>
>>>> Yesterday I have upgraded SMX resources (component, feature, etc) to use
>>>> Apache Camel 2.1 as it has been released.
>>>>
>>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>>>
>>>> I propose the following steps:
>>>>
>>>> 1/ I begin to prepare the 2009.02 components release. It includes:
>>>> - component-pom 4
>>>> - jbi-maven-plugin 4.2
>>>> These artifacts will be submit to a first vote.
>>>> - all components 2009.02
>>>> All components artifacts will be submit to a second vote.
>>>>
>>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using
>>>> Karaf 1.2.0 and perform some test to check how it runs.
>>>>
>>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the
>>>> smx
>>>> 3 and smx 4 POMs to use the previously released components.
>>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>>>
>>>> What do you think about that ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>
>> --
>> Jean-Baptiste Onofré
>> ---------------------------------
>> HomePage
>> http://www.nanthrax.net
>> ---------------------------------
>> Contacts
>> jbonofre@apache.org
>> jb@nanthrax.net
>> ---------------------------------
>> OpenSource
>> BuildProcess/AutoDeploy
>> http://buildprocess.sourceforge.net
>> Apache ServiceMix
>> http://servicemix.apache.org
>> -----------------------------------
>> PGP : 17D4F086
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
How can we help on this issue ?
Regards
JB
Gert Vanthienen wrote:
> L.S.,
>
> For the SMX 4.1 release, I think we have a problem with
> https://issues.apache.org/jira/browse/FELIX-1928. This issue in
> FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
> but it could have quite a bit of impact on our users. It might make
> more sense to work towards a new release of FileInstall and Karaf
> first before cutting the SMX 4.1 release, but any suggestions or ideas
> are welcome.
>
> For the plugins/components, we can still go ahead and release those.
> I can release those tomorrow - I have a few hours available to cut the
> release tomorrow afternoon, unless anyone knows about outstanding
> issues that need to go into the release before we can go ahead.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>> Gert,
>>
>> it makes sense yes :)
>>
>> I begin the process.
>>
>> Regards
>> JB
>>
>> Gert Vanthienen wrote:
>>> Jean-Baptiste,
>>>
>>> How about doing a big, bulky 4.1 release this week with components +
>>> nmr + features in it and then follow up with a servicemix 3.3.2
>>> release next week, reusing the same component set? That way, we can
>>> announce a new release both weeks ;)
>>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>> Blog: http://gertvanthienen.blogspot.com/
>>>
>>>
>>>
>>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>>> Hi gentlemen,
>>>>
>>>> Yesterday I have upgraded SMX resources (component, feature, etc) to use
>>>> Apache Camel 2.1 as it has been released.
>>>>
>>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>>>
>>>> I propose the following steps:
>>>>
>>>> 1/ I begin to prepare the 2009.02 components release. It includes:
>>>> - component-pom 4
>>>> - jbi-maven-plugin 4.2
>>>> These artifacts will be submit to a first vote.
>>>> - all components 2009.02
>>>> All components artifacts will be submit to a second vote.
>>>>
>>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using
>>>> Karaf 1.2.0 and perform some test to check how it runs.
>>>>
>>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the
>>>> smx
>>>> 3 and smx 4 POMs to use the previously released components.
>>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>>>
>>>> What do you think about that ?
>>>>
>>>> Regards
>>>> JB
>>>>
>> --
>> Jean-Baptiste Onofré
>> ---------------------------------
>> HomePage
>> http://www.nanthrax.net
>> ---------------------------------
>> Contacts
>> jbonofre@apache.org
>> jb@nanthrax.net
>> ---------------------------------
>> OpenSource
>> BuildProcess/AutoDeploy
>> http://buildprocess.sourceforge.net
>> Apache ServiceMix
>> http://servicemix.apache.org
>> -----------------------------------
>> PGP : 17D4F086
>>
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
For the SMX 4.1 release, I think we have a problem with
https://issues.apache.org/jira/browse/FELIX-1928. This issue in
FileInstall has been fixed after the Karaf 1.2.0 release had been cut,
but it could have quite a bit of impact on our users. It might make
more sense to work towards a new release of FileInstall and Karaf
first before cutting the SMX 4.1 release, but any suggestions or ideas
are welcome.
For the plugins/components, we can still go ahead and release those.
I can release those tomorrow - I have a few hours available to cut the
release tomorrow afternoon, unless anyone knows about outstanding
issues that need to go into the release before we can go ahead.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
> Gert,
>
> it makes sense yes :)
>
> I begin the process.
>
> Regards
> JB
>
> Gert Vanthienen wrote:
>>
>> Jean-Baptiste,
>>
>> How about doing a big, bulky 4.1 release this week with components +
>> nmr + features in it and then follow up with a servicemix 3.3.2
>> release next week, reusing the same component set? That way, we can
>> announce a new release both weeks ;)
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> Open Source SOA: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>>>
>>> Hi gentlemen,
>>>
>>> Yesterday I have upgraded SMX resources (component, feature, etc) to use
>>> Apache Camel 2.1 as it has been released.
>>>
>>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>>
>>> I propose the following steps:
>>>
>>> 1/ I begin to prepare the 2009.02 components release. It includes:
>>> - component-pom 4
>>> - jbi-maven-plugin 4.2
>>> These artifacts will be submit to a first vote.
>>> - all components 2009.02
>>> All components artifacts will be submit to a second vote.
>>>
>>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using
>>> Karaf 1.2.0 and perform some test to check how it runs.
>>>
>>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the
>>> smx
>>> 3 and smx 4 POMs to use the previously released components.
>>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>>
>>> What do you think about that ?
>>>
>>> Regards
>>> JB
>>>
>
> --
> Jean-Baptiste Onofré
> ---------------------------------
> HomePage
> http://www.nanthrax.net
> ---------------------------------
> Contacts
> jbonofre@apache.org
> jb@nanthrax.net
> ---------------------------------
> OpenSource
> BuildProcess/AutoDeploy
> http://buildprocess.sourceforge.net
> Apache ServiceMix
> http://servicemix.apache.org
> -----------------------------------
> PGP : 17D4F086
>
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Gert,
it makes sense yes :)
I begin the process.
Regards
JB
Gert Vanthienen wrote:
> Jean-Baptiste,
>
> How about doing a big, bulky 4.1 release this week with components +
> nmr + features in it and then follow up with a servicemix 3.3.2
> release next week, reusing the same component set? That way, we can
> announce a new release both weeks ;)
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
>> Hi gentlemen,
>>
>> Yesterday I have upgraded SMX resources (component, feature, etc) to use
>> Apache Camel 2.1 as it has been released.
>>
>> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>>
>> I propose the following steps:
>>
>> 1/ I begin to prepare the 2009.02 components release. It includes:
>> - component-pom 4
>> - jbi-maven-plugin 4.2
>> These artifacts will be submit to a first vote.
>> - all components 2009.02
>> All components artifacts will be submit to a second vote.
>>
>> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using
>> Karaf 1.2.0 and perform some test to check how it runs.
>>
>> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the smx
>> 3 and smx 4 POMs to use the previously released components.
>> Two votes will be submitted: one for SMX3 and another one for SMX4.
>>
>> What do you think about that ?
>>
>> Regards
>> JB
>>
--
Jean-Baptiste Onofré
---------------------------------
HomePage
http://www.nanthrax.net
---------------------------------
Contacts
jbonofre@apache.org
jb@nanthrax.net
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
Re: [PROPOSAL] Release SMX 3.3.2 and SMX 4.1 this month
Posted by Gert Vanthienen <ge...@gmail.com>.
Jean-Baptiste,
How about doing a big, bulky 4.1 release this week with components +
nmr + features in it and then follow up with a servicemix 3.3.2
release next week, reusing the same component set? That way, we can
announce a new release both weeks ;)
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/12/14 Jean-Baptiste Onofre <jb...@nanthrax.net>:
> Hi gentlemen,
>
> Yesterday I have upgraded SMX resources (component, feature, etc) to use
> Apache Camel 2.1 as it has been released.
>
> I think that we are not so far from a new SMX 3.3.2 and 4.1 release.
>
> I propose the following steps:
>
> 1/ I begin to prepare the 2009.02 components release. It includes:
> - component-pom 4
> - jbi-maven-plugin 4.2
> These artifacts will be submit to a first vote.
> - all components 2009.02
> All components artifacts will be submit to a second vote.
>
> 1 bis/ in the same time, I try to build a SMX 4.1-SNAPSHOT assembly using
> Karaf 1.2.0 and perform some test to check how it runs.
>
> 2/ once these steps 1 and 1 bis have been performed, we can upgrade the smx
> 3 and smx 4 POMs to use the previously released components.
> Two votes will be submitted: one for SMX3 and another one for SMX4.
>
> What do you think about that ?
>
> Regards
> JB
>