Re: [VOTE] Release Apache Karaf 2.2.9
+1 (non binding) Tested with my tutorials and some Talend examples. Looks all good besides one problem with JTA and JMS but it is probably rather a problem in my example. Christian Am 15.08.2012 14:28, schrieb Jamie G.: Hi, We resolved 50 issues in this release (web page will be published post RC promotion): https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.2.9-release.page Staging repository: https://repository.apache.org/content/repositories/orgapachekaraf-013/ Release tags: https://svn.apache.org/repos/asf/karaf/tags/karaf-2.2.9/ 2.2.x Dependencies table: https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.2.x.page Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: Change webconsole context path
+1 On Wed, Aug 15, 2012 at 3:06 PM, Jean-Baptiste Onofré j...@nanthrax.netwrote: +1 On 08/15/2012 02:25 PM, Łukasz Dywicki wrote: Hey, I would like ask you (and notify) about change of webconsole context path. Current /cns path was with us since begining of prototype. It's short but not intuitive. As the Felix WebConsole uses /system/console we can use /console without conflicts. What do you think? Do you have other proposals we could use? Best regards, Lukasz -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Charles Moulliard Apache Committer / Sr. Pr. Consultant at FuseSource.com Twitter : @cmoulliard Blog : http://cmoulliard.blogspot.com
Re: Change webconsole context path
+1 Freeman － Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042 On 2012-8-15, at 下午8:25, Łukasz Dywicki wrote: Hey, I would like ask you (and notify) about change of webconsole context path. Current /cns path was with us since begining of prototype. It's short but not intuitive. As the Felix WebConsole uses /system/console we can use /console without conflicts. What do you think? Do you have other proposals we could use? Best regards, Lukasz
Re: [VOTE] Release Apache Karaf 2.2.9
+1 On Wed, Aug 15, 2012 at 2:28 PM, Jamie G. jamie.goody...@gmail.com wrote: Hi, We resolved 50 issues in this release (web page will be published post RC promotion): https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.2.9-release.page Staging repository: https://repository.apache.org/content/repositories/orgapachekaraf-013/ Release tags: https://svn.apache.org/repos/asf/karaf/tags/karaf-2.2.9/ 2.2.x Dependencies table: https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.2.x.page Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. -- Charles Moulliard Apache Committer / Sr. Pr. Consultant at FuseSource.com Twitter : @cmoulliard Blog : http://cmoulliard.blogspot.com
JIRA, old webconsole new webconsole collision
Hey, We have one component in JIRA for both consoles. This may lead problems in future. Shouldn't we split it for two different eg. felix-webconsole for older console and karaf-webconsole for newer? Also we don't have any version for webconsole in JIRA. Current version in SCM points to 0.3.0-SNAPSHOT. Best regards, Lukasz
Re: Change webconsole context path
+1 On Thu, Aug 16, 2012 at 6:04 AM, Freeman Fang freeman.f...@gmail.com wrote: +1 Freeman － Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042 On 2012-8-15, at 下午8:25, Łukasz Dywicki wrote: Hey, I would like ask you (and notify) about change of webconsole context path. Current /cns path was with us since begining of prototype. It's short but not intuitive. As the Felix WebConsole uses /system/console we can use /console without conflicts. What do you think? Do you have other proposals we could use? Best regards, Lukasz
Re: JIRA, old webconsole new webconsole collision
Done, Regards JB On 08/16/2012 06:26 PM, Łukasz Dywicki wrote: Please do that, components are following: - webconsole-core - webconsole-osgi - webconsole-karaf - webconsole-war (for embedding in WAR) - webconsole-docs Cheers, Lukasz Wiadomość napisana przez Jean-Baptiste Onofré w dniu 16 sie 2012, o godz. 16:14: Hi Lukasz, Agree, as WebConsole is a subproject, it should have its own component (like cellar, cave, etc). I can create the components if you want. Regards JB On 08/16/2012 11:03 AM, Łukasz Dywicki wrote: Hey, We have one component in JIRA for both consoles. This may lead problems in future. Shouldn't we split it for two different eg. felix-webconsole for older console and karaf-webconsole for newer? Also we don't have any version for webconsole in JIRA. Current version in SCM points to 0.3.0-SNAPSHOT. Best regards, Lukasz -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
WebConsole versioning
Once again I back with WebConsole topic. As we plan to support bot 2.x and 3.x line. Current trunk (0.3.0-SNAPSHOT) of webconsole supports 2.x and I am about to start 3.x branch to get karaf trunk also supported. The problem is that we can not have the same version for both Karaf versions due changes in package names and so on. So the WebConsole must have two different versions, one for Karaf 2.x and second for 3.x. Another option is to make *core* of webconsole Karaf version agnostic, but then we still have submodules which have to support different versions of Karaf OSGi runtime. Currently thing which breaks compability of 2.x vs 3.x is JAAS stuff and move of some packages to jaas.boot. In my opinion it's easier to manage release process with one version per branch, not like Aries does - a version per module. On IRC we had few options, one was classifier, another was to start with 2.x version for Karaf 2.x and 3.x for Karaf 3.x - just like we have with Cellar. What do you think? Cheers, Lukasz
Re: [VOTE] Release Apache Karaf 2.2.9
I've finally downloaded, built and test the resources (on my projects) and everything looks fine -- +1 Kind regards, Andreas On Thu, Aug 16, 2012 at 10:40 AM, Charles Moulliard ch0...@gmail.com wrote: +1 On Wed, Aug 15, 2012 at 2:28 PM, Jamie G. jamie.goody...@gmail.com wrote: Hi, We resolved 50 issues in this release (web page will be published post RC promotion): https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.2.9-release.page Staging repository: https://repository.apache.org/content/repositories/orgapachekaraf-013/ Release tags: https://svn.apache.org/repos/asf/karaf/tags/karaf-2.2.9/ 2.2.x Dependencies table: https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.2.x.page Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. -- Charles Moulliard Apache Committer / Sr. Pr. Consultant at FuseSource.com Twitter : @cmoulliard Blog : http://cmoulliard.blogspot.com
Re: Change webconsole context path
+1 for console Kind regards, Andreas On Thu, Aug 16, 2012 at 1:21 PM, Ioannis Canellos ioca...@gmail.com wrote: +1 -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: JIRA, old webconsole new webconsole collision
maybe we should also add a webconsole-3party (or something similar) for various third party support we may provide in the beginning? On Thu, Aug 16, 2012 at 6:26 PM, Łukasz Dywicki l...@code-house.org wrote: Please do that, components are following: - webconsole-core - webconsole-osgi - webconsole-karaf - webconsole-war (for embedding in WAR) - webconsole-docs Cheers, Lukasz Wiadomość napisana przez Jean-Baptiste Onofré w dniu 16 sie 2012, o godz. 16:14: Hi Lukasz, Agree, as WebConsole is a subproject, it should have its own component (like cellar, cave, etc). I can create the components if you want. Regards JB On 08/16/2012 11:03 AM, Łukasz Dywicki wrote: Hey, We have one component in JIRA for both consoles. This may lead problems in future. Shouldn't we split it for two different eg. felix-webconsole for older console and karaf-webconsole for newer? Also we don't have any version for webconsole in JIRA. Current version in SCM points to 0.3.0-SNAPSHOT. Best regards, Lukasz -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: WebConsole versioning
I'm with Lukasz on that one; we should keep our releases as simple as possible, even if this means some more cherry-picking between the various branches. Independently, after getting some good portion of sleep and some more time to think about this issue I think we should walk down the same road as cellar: using 2.x for karaf 2.x support and 3.x for karaf 3 support (although this limits our version range according to semver.org). An option around this problem might be to add an additional version behind; e.g. starting with 2.0.0.0 and 3.0.0.0 for the first releases; or in other words KARAF.WC_MAJOR.WC_MINOR.WC_MICRO. WDYT? Kind regards, Andreas On Thu, Aug 16, 2012 at 10:26 PM, Łukasz Dywicki l...@code-house.org wrote: Once again I back with WebConsole topic. As we plan to support bot 2.x and 3.x line. Current trunk (0.3.0-SNAPSHOT) of webconsole supports 2.x and I am about to start 3.x branch to get karaf trunk also supported. The problem is that we can not have the same version for both Karaf versions due changes in package names and so on. So the WebConsole must have two different versions, one for Karaf 2.x and second for 3.x. Another option is to make *core* of webconsole Karaf version agnostic, but then we still have submodules which have to support different versions of Karaf OSGi runtime. Currently thing which breaks compability of 2.x vs 3.x is JAAS stuff and move of some packages to jaas.boot. In my opinion it's easier to manage release process with one version per branch, not like Aries does - a version per module. On IRC we had few options, one was classifier, another was to start with 2.x version for Karaf 2.x and 3.x for Karaf 3.x - just like we have with Cellar. What do you think? Cheers, Lukasz
Re: svn commit: r1372333 - in /karaf/trunk: main/src/main/java/org/apache/karaf/main/ shell/console/src/main/java/org/apache/karaf/shell/console/impl/jline/
well, we can't release 3.x as long as there are any commits with -1 votes on them -- we either need to revert this commit or add some extensions. I just don't want to let this lay around suppressing any 3.x releases... Kind regards, Andreas On Mon, Aug 13, 2012 at 5:47 PM, Christian Schneider ch...@die-schneider.net wrote: I use Tortoise SVN. Not the one in eclipse. The problems I stated only started some weeks ago. No idea why. Christian Am 13.08.2012 17:44, schrieb Jean-Baptiste Onofré: No worries, thanks for the update. My advice would be to stop using svn into Eclipse and use directly svn/git command line ;) Regards JB On 08/13/2012 05:42 PM, Christian Schneider wrote: Of course I tested my code .. the problem was that I then omitted one file in the commit. So in fact what I committed was not what I tested :-( I was really sure it should work as I had done the build and test several times. I thought he might only have seen the true in the code and taken it as a sign that I set the default to true. The config should have overridden this. This was because of problems I currently have with my svn that shows a lot of changed files that are not changed at all. Perhaps you can take a look at it at some point. Sorry about that. Christian Am 13.08.2012 17:19, schrieb Jean-Baptiste Onofré: Christian, it's not fair. I think that Jamie votes -1 with strong arguments and you can be sure he tested it. Just kidding: Have YOU tested YOUR code ? ;) It's always the question I asked to myself before committing (do I cover all test case, do I make a complete build, do I consider all remarks coming from the team, from the users, etc). Our work is not so easy ;) Regards JB -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: [VOTE] Release Apache Karaf 2.2.9
+1
Thoughts on KARAF-1718
Hi, I have created and attached a patch for: https://issues.apache.org/jira/browse/KARAF-1718 I have it scheduled for 3.1.0, but if you agree we could also have it in 3.0.0. It pretty much works as is, but if we agree to have it in 3.0.0 I could work on a couple more improvements that I have in mind. Thoughts? -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Thoughts on KARAF-1718
+1 if can make it to catch 3.0.0 release train. Freeman － Freeman Fang FuseSource Email:ff...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042 On 2012-8-17, at 下午1:34, Ioannis Canellos wrote: Hi, I have created and attached a patch for: https://issues.apache.org/jira/browse/KARAF-1718 I have it scheduled for 3.1.0, but if you agree we could also have it in 3.0.0. It pretty much works as is, but if we agree to have it in 3.0.0 I could work on a couple more improvements that I have in mind. Thoughts? -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
