Sunday, December 30, 2012

Apache Karaf update Dec 23 - 29, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.11, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.11:


New Issues:
N/A

Resolved Issues:
Karaf-2087 add a testcase to cover the scenario that the AdminService can always load latest instance status which changed by external process

Updated Issues:
N/A

Apache Karaf 2.3.1:


New Issues:
N/A

Resolved Issues:
Karaf-2087 add a testcase to cover the scenario that the AdminService can always load latest instance status which changed by external process
Karaf-2088 Upgrade to Jetty 7.6.8.v20121106

Updated Issues:
N/A

Apache Karaf 3.0.0:


New Issues:
N/A

Resolved Issues:
Karaf-2084 Upgrade to Jetty 8.1.8.v20121106
Karaf-2085 Upgrade to Jetty 8.1.8.v20121106
Karaf-2086 Upgrade to Spring 3.1.3.RELEASE
Karaf-2087 add a testcase to cover the scenario that the AdminService can always load latest instance status which changed by external process
Karaf-2067 instance-script terminates with NoClassDefFoundError

Updated Issues:
N/A

Un-versioned Issues:

Karaf-2062 Add a spring3.2 feature
Karaf-2090 Mark module tab as active when needed

Sunday, December 23, 2012

Apache Karaf update Dec 16 - 22, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.11, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Announcements:


Apache Karaf 2.2.10 Released!

Apache Karaf 2.2.11:


New Issues:
Karaf-1327 Client: can't execute alias command
Karaf-2078 Create the shell:date command

Resolved Issues:
N/A

Updated Issues:
Karaf-2053 HTTP feature should install a default etc/org.ops4j.pax.web.cfg file
Karaf-933 War feature installation failed with Java 5
Karaf-1386 feature install war fails if http-whiteboard is already installed

Apache Karaf 2.3.1:


New Issues:
Karaf-2069 Provide less command
Karaf-2070 Add support of !$ to recall the last command argument
Karaf-2078 Create the shell:date command
Karaf-2035 Not able to clone the root instance

Resolved Issues:
Karaf-2065 Upgrade to Felix SCR 1.6.2
Karaf-1770 Unable to feature:install webconsole under apache-karaf minimal package
Karaf-2068 Upgrade to ASM 4.1
Karaf-2047 config:edit -f command doesn't work on Windows platform
Karaf-2071 Minimal distribution doesn't start
Karaf-2072 Spelling correction
Karaf-2009 Error on visualize Licences page
Karaf-2073 Progress bar sometimes goes backwards
Karaf-2074 ensure admin service always load storage file instance.properties before each operation
Karaf-2057 NOTICE and LICENSE files are not correct
Karaf-2079 upgrade to pax web 1.1.10
Karaf-2080 Upgrade to slf4j 1.7.2
Karaf-2081 Upgrade to JUnit 4.11
Karaf-2083 Remove icu4j dependency

Updated Issues:
Karaf-2053 HTTP feature should install a default etc/org.ops4j.pax.web.cfg file

Apache Karaf 3.0.0:


New Issues:
Karaf-2069 Provide less command
Karaf-2070 Add support of !$ to recall the last command argument
Karaf-2078 Create the shell:date command
Karaf-2035 Not able to clone the root instance

Resolved Issues:
Karaf-2065 Upgrade to Felix SCR 1.6.2
Karaf-2012 Upgrade to Pax Web 3.0.0.M1
Karaf-2068 Upgrade to ASM 4.1
Karaf-2072 Spelling correction
Karaf-2009 Error on visualize Licences page
Karaf-2074 ensure admin service always load storage file instance.properties before each operation
Karaf-2057 NOTICE and LICENSE files are not correct
Karaf-2080 Upgrade to slf4j 1.7.2
Karaf-2081 Upgrade to JUnit 4.11

Updated Issues:
Karaf-2053 HTTP feature should install a default etc/org.ops4j.pax.web.cfg file
Karaf-2011 dev:watch looks in an incorrect local maven repository
Karaf-1149 Karaf MBeanServer is not usable behind firewall

Un-versioned Issues:

Karaf-2059 Extend features:install command to support given a repository name as input
Karaf-2067 instance-script terminates with NoClassDefFoundError
Karaf-2075 Shutdown Karaf but the bundle stop is not follow the start-level
Karaf-1278 Comands: History does not work, can not edit current comand
Karaf-2076 Add a pojosr unit test to validate that we can use OSGI Config Admin with value encrypted (JAAS - Jasypt)
Karaf-2077 Exported package names cannot be zero length. when karaf 2.3 starts within unit test using openengsb
Karaf-2082 Jasypt unit tests fail
Karaf-1973 NullPointerException when performing log:clear then log:tail

Saturday, December 22, 2012

Apache Karaf 2.2.10 Released!

The Apache Karaf team is pleased to announce the availability of Apache Karaf 2.2.10.

This release of Apache Karaf is based off of the 2.2.x series branch, representing an update to Apache Karaf 2.2.9. It contains bug fixes identified in the prior release, and introduces improvements including; Making pom.xml eclipse 3.7 m2e friendly, updating Spring to 2.5.6.SEC03, improved terminal behavior when sshing from windows to unix, and improved lock logic to wait while start level change occurs. Several dependencies were also updated, bringing Felix Webconsole to 4.0.0, pax-logging to 1.6.10, pax-web to 1.0.12, and the Apache pom to version 12.

To help make the transition from previous Apache Karaf 2.2.x releases to 2.2.10 easier we've put together a table of changed dependencies which you can view here. For more information please see the release notes.

As discussed in my prior Apache Karaf 2.2.10 preparation post, I enjoyed listening to Alexisonfire albums throughout the release process and was delighted to try the Robert Skalli Reserve Cabernet Sauvignon 2009. I think the music and wine pairings are really working well for these releases, that being said if anyone has suggestions for future music or wine selections please post them below :)

Now that this patch release is out, I can't wait for the up coming 2.3.1 and 3.0.0.RC1 kits - both branches are rapidly coming close to being ready! Rest assured however that Karaf 2.2.11 is also in the works.

Happy developing!

Sunday, December 16, 2012

Apache Karaf update Dec 8 - 15, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:


New Issues:
Karaf-2053 HTTP feature should install a default etc/org.ops4j.pax.web.cfg file
Karaf-2057 NOTICE and LICENSE files are not correct

Resolved Issues:
Karaf-2050 Ability to configure ssh session idle timeout - currently hardcode as 5 minutes
Karaf-2055 Upgrade to Apache POM 12
Karaf-2028 org.apache.karaf.webconsole.console imports wrong version of org.osgi.service.deploymentadmin
Karaf-1745 Upgrade to Felix WebConsole 4.0.0
Karaf-2058 ensure find the root instance entry when update root karaf instance name in instances.properties

Updated Issues:


Apache Karaf 2.3.1:


New Issues:
Karaf-2053 HTTP feature should install a default etc/org.ops4j.pax.web.cfg file
Karaf-2057 NOTICE and LICENSE files are not correct

Resolved Issues:
Karaf-2050 Ability to configure ssh session idle timeout - currently hardcode as 5 minutes
Karaf-2052 Progress bar doesn't display properly on 80 char consoles
Karaf-2055 Upgrade to Apache POM 12
Karaf-1745 Upgrade to Felix WebConsole 4.0.0
Karaf-2058 ensure find the root instance entry when update root karaf instance name in instances.properties
Karaf-2061 Upgrade to commons-codec 1.7
Karaf-2063 Upgrade to Felix EventAdmin 1.3.2
Karaf-2064 Upgrade to Felix Metatype 1.0.6
Karaf-2065 Upgrade to Felix SCR 1.6.2

Updated Issues:
Karaf-222 mvn karaf:run plugin, like jetty:run

Apache Karaf 3.0.0:


New Issues:
Karaf-2053 HTTP feature should install a default etc/org.ops4j.pax.web.cfg file
Karaf-2057 NOTICE and LICENSE files are not correct

Resolved Issues:
Karaf-2050 Ability to configure ssh session idle timeout - currently hardcode as 5 minutes
Karaf-2052 Progress bar doesn't display properly on 80 char consoles
Karaf-2055 Upgrade to Apache POM 12
Karaf-1745 Upgrade to Felix WebConsole 4.0.0
Karaf-2058 ensure find the root instance entry when update root karaf instance name in instances.properties
Karaf-2061 Upgrade to commons-codec 1.7
Karaf-2063 Upgrade to Felix EventAdmin 1.3.2
Karaf-2064 Upgrade to Felix Metatype 1.0.6
Karaf-2065 Upgrade to Felix SCR 1.6.2

Updated Issues:
Karaf-222 mvn karaf:run plugin, like jetty:run

Un-versioned Issues:

Karaf-2054 Execute native commands from the shell
Karaf-2045 Support encrypted connection to the database for fail over configuration
Karaf-1925 Blueprint timeout exceptions after karaf startup
Karaf-2059 Extend features:install command to support given a repository name as input
Karaf-2060 Variables cannot be used in org.apache.karaf.features.cfg
Karaf-2062 Add a spring3.2 feature

Tuesday, December 11, 2012

Apache Karaf in the trenches @ OSGi DevCon / EclipseCon 2013


Exciting news! My talk session "Apache Karaf in the trenches" has been accepted to OSGi DevCon 2013 (co-located with EclipseCon Boston 2013). I've copied in below the outline for my talk.

Abstract:

Apache Karaf is a small, light weight server side OSGi runtime environment, that has been gaining in popularity in the Apache and OSGi community. The shift towards using OSGi environments has introduced new challenges to architects, developers, and operators in building and deploying these systems. In this session I will share some of my experiences in developing, deploying, and maintaining OSGi based software systems among Global 2000 companies targeting the Apache Karaf runtime environment.

 The talk will be broken down into three sections:

  •  A brief introduction to Apache Karaf 
  •  Best practices in deployment 
  •  Best practices for developing applications

I'm excited for this opportunity to share my Apache Karaf experiences with the OSGi community. If you're in the Boston, Massachusetts area in late March please consider registering for the conference.

EclipseCon 2013

Sunday, December 9, 2012

Apache Karaf update Dec 2 - 8, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:


New Issues:
Karaf-2047 config:edit -f command doesn't work on Windows platform

Resolved Issues:
Karaf-2043 Document caveats of Pax Url Wrap when used in Karaf Shell
Karaf-2049 Instructions in welcome screen is a bit misleading with hit

Updated Issues:
Karaf-1018 using auto-complete (TAB key) on commands that don't take Arguments/Options throws IndexOutOfBoundsException.

Apache Karaf 2.3.1:


New Issues:
Karaf-2047 config:edit -f command doesn't work on Windows platform

Resolved Issues:
Karaf-2043 Document caveats of Pax Url Wrap when used in Karaf Shell
Karaf-2049 Instructions in welcome screen is a bit misleading with hit
Karaf-1955 Upgrade to ServiceMix Specs 2.2.0

Updated Issues:
Karaf-2050 Ability to configure ssh session idle timeout - currently hardcode as 5 minutes


Apache Karaf 3.0.0:


New Issues:
Karaf-2044 Provide the ability to edit text resources from the Karaf shell
Karaf-2047 config:edit -f command doesn't work on Windows platform

Resolved Issues:
Karaf-2043 Document caveats of Pax Url Wrap when used in Karaf Shell
Karaf-2049 Instructions in welcome screen is a bit misleading with hit
Karaf-1955 Upgrade to ServiceMix Specs 2.2.0
Karaf-2051 Duplicate definition of org.ops4j.pax.url.mvn.localRepository in org.ops4j.pax.url.mvn.cfg

Updated Issues:
Karaf-1369 Shell history does not log all commands
Karaf-2050 Ability to configure ssh session idle timeout - currently hardcode as 5 minutes

Un-versioned Issues:

Karaf-2045 Support encrypted connection to the database for fail over configuration
Karaf-1823 Memory leak on windows in SSHD ServerSession
Karaf-2046 Deadlock on console refresh
Karaf-2048 Add ability to intercept CommandSession.close() to clean up shared resource before disconnect
Karaf-1180 Ability to exit karaf with a predictable exit code
Karaf-1968 Uninstalling jndi feature leads to hanging Karaf
Karaf-1278 Comands: History does not work, can not edit current comand
Karaf-2052 Progress bar doesn't display properly on 80 char consoles

Wednesday, December 5, 2012

Goodwill Gaming Marathon #5 in support of R.E.A.L. program.

We Play So They Can Play - Goodwill Gaming Marathon #5 In Support of REAL Program


When:
December 14th 12:00 PM - 17th 8:00 PM

Where:
http://www.goodwillgaming.org

So what is this all about?

"Goodwill Gaming is a non-profit organization that raises money for charity, but in a unique way—with video games. To date, we have raised over $7000 for different charitable organizations. We do gaming marathons that are streamed online which anyone can watch and chat with the players, as well as donate from the comfort of their own computer.

Besides marathons, we do public events, like appearing at St. John's Sci-Fi on the Rock. We have various events throughout the year that anyone can participate in. Stay tuned to the website, or check out our facebook page for all event information and coverage.

Be sure to tune in from Dec 14 at 12:00 PM (10:30 AM) until Dec 17 at 8:00 PM for our next charity marathon in support of the St. John's R.E.A.L. Program. Watch, chat and donate all on this [goodwillgaming.org] website!"

A small disclaimer; this site is not affiliated with Goodwill Gaming or its partner charities, however I think it's a novel way to help our community and wish GWG the best of luck with their marathon.

Saturday, December 1, 2012

Apache Karaf update Nov 25 - Dec 1, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:


New Issues:
N/A

Resolved Issues:
Karaf-2029 delete.user option missing from JDBCLoginModule
Karaf-1715 Occasional freeze on feature:install webconsole

Updated Issues:
N/A


Apache Karaf 2.3.1:


New Issues:
N/A

Resolved Issues:
Karaf-2029 delete.user option missing from JDBCLoginModule
Karaf-2036 Upgrade to Pax Web 1.1.9
Karaf-1715 Occasional freeze on feature:install webconsole
Karaf-2027 invalid password option for admin:connect command in documenation
Karaf-2026 Two broken links on remote console manual page

Updated Issues:
Karaf-1955 Upgrade to ServiceMix Specs 2.2.0

Apache Karaf 3.0.0:


New Issues:
Karaf-2037 karaf 3.0 with gemini blueprint

Resolved Issues:
Karaf-2029 delete.user option missing from JDBCLoginModule
Karaf-1715 Occasional freeze on feature:install webconsole
Karaf-2027 invalid password option for admin:connect command in documenation
Karaf-2026 Two broken links on remote console manual page

Updated Issues:
Karaf-1955 Upgrade to ServiceMix Specs 2.2.0

Un-versioned Issues:

Karaf-2034 Support of Gemini Blueprint
Karaf-2035 Not able to clone the root instance
Karaf-1692 Deployment of unpacked WAR does not work
Karaf-1724 Blueprint bundle deadlocks in "Stopping" status when update-ing/dev:watch bundle 
Karaf-2043 Document caveats of Pax Url Wrap when used in Karaf Shell

Sunday, November 25, 2012

Apache Karaf Update Nov 18 - 24, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:


New Issues:
Karaf-2028 org.apache.karaf.webconsole.console imports wrong version of org.osgi.service.deploymentadmin

Resolved Issues:
Karaf-2017 Service wrapper should use and populate JAVA_HOME in conf file 
Karaf-1936 LDAPLoginModule not working in 2.3.0 due to missing import of javax.net.SocketFactory
Karaf-1911 Wrong version of camel-example-osgi in Getting Started/Quickstart Guide - 2.7.0 doesn't work

Updated Issues:
N/A

Apache Karaf 2.3.1:


New Issues:
N/A

Resolved Issues:
Karaf-2017 Service wrapper should use and populate JAVA_HOME in conf file 
Karaf-1936 LDAPLoginModule not working in 2.3.0 due to missing import of javax.net.SocketFactory
Karaf-2024 add @id for org.ops4j.pax.url.mvn.repositories urls

Updated Issues:

Un-versioned Issues:

Monday, November 19, 2012

NLWebDevs: Web Services - Behind the scenes with server side Apache projects.


Web Services - Behind the scenes with server side Apache projects.

November 22, 2012. 7-8pm.
Memorial University of Newfoundland (EN-2022)

A lot of sites rely on highly scalable, robust services. In this talk, I will touch upon several Apache projects that are being used to provide web services, and how these projects can be mixed and matched to provide the infrastructure today's applications demand. This will be a high level talk aimed towards exposing developers and network admins to the Apache SOA technology stack. Projects that will be discussed include Apache CXF, ActiveMQ, Camel, Cassandra, Hadoop, Karaf, and Servicemix.

Sunday, November 18, 2012

Apache Karaf Update Nov 11 - 17, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:


New Issues:
Karaf-2011 dev:watch looks in an incorrect local maven repository

Resolved Issues:
Karaf-2013 Bug in Karaf 2.3.0 Maven2 Features Plugin Documentation
Karaf-1936 LDAPLoginModule not working in 2.3.0 due to missing import of javax.net.SocketFactory

Updated Issues:
Karaf-1715 Occasional freeze on feature:install webconsole

Apache Karaf 2.3.1:


New Issues:
Karaf-2011 dev:watch looks in an incorrect local maven repository
Karaf-2015 Upgrade to Pax Web 1.1.7

Resolved Issues:
Karaf-2013 Bug in Karaf 2.3.0 Maven2 Features Plugin Documentation
Karaf-1936 LDAPLoginModule not working in 2.3.0 due to missing import of javax.net.SocketFactory
Karaf-2010 Cannot install application-without-isolation feature : Could not start bundle mvn:org.apache.felix/org.apache.felix.bundlerepository/1.6.6 in feature(s) obr-2.3.0: Activator start error in bundle org.apache.felix.bundlerepository [3086].

Updated Issues:


Un-versioned Issues:

Sunday, November 11, 2012

Apache Karaf Update Nov 4 - 10, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10: 


New Issues:
Karaf-2009 Error on visualize Licences page

Resolved Issues:
Karaf-1992 PropertiesLoginModule handles usernames with backslash not correct

Updated Issues:
N/A

Apache Karaf 2.3.1:

New Issues:

Karaf-2009 Error on visualize Licences page

Resolved Issues:
Karaf-1992 PropertiesLoginModule handles usernames with backslash not correct
Karaf-2002 Upgrade to Pax Web 1.1.6
Karaf-1981 Upgrade to Felix ConfigAdmin 1.6.0
Karaf-1977 Upgrade to OSGi 4.3.1
Karaf-2007 features without start-level in features.xml are always started first

Updated Issues:
N/A

Apache Karaf 3.0.0:

New Issues:

Karaf-2003 Interrupt a running command in shell 
Karaf-2009 Error on visualize Licences page

Resolved Issues:
Karaf-1992 PropertiesLoginModule handles usernames with backslash not correct
Karaf-1981 Upgrade to Felix ConfigAdmin 1.6.0
Karaf-1977 Upgrade to OSGi 4.3.1
Karaf-2007 features without start-level in features.xml are always started first
Karaf-2008 respectStartLvlDuringFeatureStartup does not respect feature-start-levels (only bundles)

Updated Issues:
Karaf-1369 Shell history does not log all commands

Un-versioned Issues:


Thursday, November 8, 2012

OSGi Starter - The essential guide to modular development with OSGi for the serious application developer.

Earlier this year Johan and I were approached by Packt Publishing to submit an outline on OSGi for their Starter series. Both Johan and I have been working with modular java frameworks and runtime environments for years - so being given an opportunity to share our experiences and help developers quickly come up to speed was a fortuity.

Our goal was write the book such that a java developer could pick it up on a Friday afternoon and come Monday morning be ready to join a team project based in OSGi, with an already established software architecture, and be productive. 

To this end some of the points our book focuses on are:

  • Discover the basic tenets of the OSGi and modular programming. 
  • Deploy and manage your OSGi applications in a runtime container. 
  • Gain familiarity with OSGi tooling 
  • Understand the Bundle as the most basic layer of OSGI modularity. 
  • Master the OSGi Lifecycle model for modular code. 
  • Learn about Services - producer and consumer bundles are demonstrated.
  • Gain exposure to key OSGi patterns such as Whiteboard and Extender. 
  • Find more information and supporting communities for OSGi developers.

Our book is expected to be available in December 2012 pending any unforeseen production issues.

Sunday, November 4, 2012

Apache Karaf Update Oct 28 - Nov 3, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:


New Issues:
N/A

Resolved Issues:
Karaf-1978 if use script to start a child instance then using karaf console admin:list can't get the instance correct status
Karaf-1938 Lock logic should wait for start level change to occur
Karaf-1986 instance.properties file doesn't get updated if karaf.name is changed
Karaf-1989 Add CXF DOSGi feature uri to org.apache.karaf.features.repos.cfg

Updated Issues:
N/A

Apache Karaf 2.3.1:


New Issues:
Karaf-1981 Upgrade to Felix ConfigAdmin 1.6.0

Resolved Issues:
Karaf-1978 if use script to start a child instance then using karaf console admin:list can't get the instance correct status
Karaf-1938 Lock logic should wait for start level change to occur
Karaf-581 Also make rmiRegistryHost configurable
Karaf-1129 Allow configuring rmi Registry host as well as port
Karaf-1986 instance.properties file doesn't get updated if karaf.name is changed

Updated Issues:
N/A

Apache Karaf 3.0.0:


New Issues:
Karaf-1981 Upgrade to Felix ConfigAdmin 1.6.0

Resolved Issues:
Karaf-1978 if use script to start a child instance then using karaf console admin:list can't get the instance correct status
Karaf-1938 Lock logic should wait for start level change to occur
Karaf-581 Also make rmiRegistryHost configurable
Karaf-1129 Allow configuring rmi Registry host as well as port
Karaf-1986 instance.properties file doesn't get updated if karaf.name is changed
Karaf-1282 Remove osgi sources from karaf main
Karaf-1989 Add CXF DOSGi feature uri to org.apache.karaf.features.repos.cfg

Updated Issues:
Karaf-1966 Upgrade to Pax Web 3.0

Un-versioned Issues:

Karaf-1954 NullPointerException on custom Karaf shell command: ClassNotFoundException: org.apache.felix.service.command.Function not found
Karaf-1991 NPE during blueprint deployment with two factory beans 
Karaf-1992 PropertiesLoginModule handles usernames with backslash not correct

Software Methodologies Guest lecture on November 9th, 2012

I've been asked to provide a guest lecture for CS3716 Software Methodologies at Memorial University this Fall 2012 semester.

Usually I talk about various subjects including a brief introduction to the Apache Way, the projects I've worked on, my views on technology (locally grown and in general), and project management (specifically talking about Apache Karaf). This time around I'll also try to discuss modular programming, in specific OSGi.

My talk will be on November 9th, in room EN1051. If you're on or near campus please feel free to drop in - seating is limited however with priority given to the class's registered students.

Sunday, October 28, 2012

Apache Karaf Update Oct 21 - Oct 27, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:


New Issues:
Karaf-1965 Release Apache Karaf 2.2.10

Resolved Issues:
Karaf-1963 incorrect statement in developers-guide/branding-console.html

Updated Issues:
N/A

Apache Karaf 2.3.1:


New Issues:
Karaf-1977 Upgrade to OSGi 4.3.1

Resolved Issues:
Karaf-1963 incorrect statement in developers-guide/branding-console.html
Karaf-1930 Upgrade to Pax Web 1.1.5

Updated Issues:
Karaf-1955 Upgrade to ServiceMix Specs 2.2

Apache Karaf 3.0.0:


New Issues:
Karaf-1966 Upgrade to Pax Web 3.0
Karaf-1977 Upgrade to OSGi 4.3.1

Resolved Issues:
Karaf-1963 incorrect statement in developers-guide/branding-console.html
Karaf-1334 Use the new servicemix spec to allow the use of both the JRE implementations and implementations from bundles

Updated Issues:
Karaf-1955 Upgrade to ServiceMix Specs 2.2

Un-versioned Issues:

Karaf-1938 Lock logic should wait for start level change to occur
Karaf-1968 Uninstalling jndi feature leads to hanging Karaf
Karaf-1972 karaf-maven-plugin should respect scope
Karaf-1973 NullPointerException when performing log:clear then log:tail
Karaf-1976 Shell attempts to execute sub-shell actions as commands

Saturday, October 27, 2012

Preparing for Apache Karaf 2.3.1

The first patch release of the Apache Karaf 2.3.x branch will be soon entering the planning phase (no immediate need patch, 2.3.0 is performing wonderfully!), as such I'm preparing for the release management role.

To prepare I've selected a bottle of Marques de Casa Concha 2010 Pinot Noir to decant while listening to some Death From Above 1979 albums.

Current high lights of this patch include a multitude of updates to dependencies, such as updating to OSG 4.3.1Apache pom 11, Spring 3.1Pax-web 1.1.5, and Servicemix Specs 2.2. A complete change log will be created for the Release Candidate once the community is ready to put it to vote.

The wine will of course only be sampled after being gave proper time to breath in its container, after the first release candidate has be up loaded for voting (see our release guide for more details on our process).

Unfortunately I can't share the wine with you, but I can share a few links to some DFA 1979 videos. I'm looking forward to starting the 2.3.1 release process soon.

I'll be posting updates to our Twitter stream (#karaf) and on our IRC channel (irc.codehaus.org #karaf).

Sunday, October 21, 2012

Apache Karaf Update Oct 14 - Oct 20, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.1, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Announcements:

Apache Karaf 2.3.0 Released!

Apache Karaf 2.2.10:


New Issues:
N/A

Resolved Issues:
N/A

Updated Issues:
N/A

Apache Karaf 2.3.1:


New Issues:
Karaf-1921 Upgrade to Spring 3.1.x for Karaf 2.3.x
Karaf-1934 Release Apache Karaf 2.3.1
Karaf-1936 LDAPLoginModule not working in 2.3.0 due to missing import of javax.net.SocketFactory
Karaf-1939 ssh bundles should not be in startup.properties
Karaf-1940 admin/instance should be provided as a feature
Karaf-1941 Management bundles should not be in the startup.properties
Karaf-1952 Allow Karaf monitoring using host:port
Karaf-1955 Upgrade to ServiceMix Specs 2.2

Resolved Issues:
Karaf-1801 slf4j 1.7.0
Karaf-1924 Fix the WARN logs from starting a vanilla Karaf 2.3.0
Karaf-1933 Add id for Maven repository
Karaf-1117 Remove workaround for KARAF-1117
Karaf-1949 console shutdown -f hang

Updated Issues:
Karaf-1930 Upgrade to Pax Web 1.1.5


Apache Karaf 3.0.0:


New Issues:
Karaf-1512 enhancement: add self to generated feature in "features-generate-descriptor" goal
Karaf-1936 LDAPLoginModule not working in 2.3.0 due to missing import of javax.net.SocketFactory
Karaf-1940 admin/instance should be provided as a feature
Karaf-1952 Allow Karaf monitoring using host:port
Karaf-1955 Upgrade to ServiceMix Specs 2.2

Resolved Issues:
Karaf-1801 slf4j 1.7.0
Karaf-1893 Upgrade to Jetty 8.1.7.v20120910
Karaf-1903 Refactore osgicore and osgicompendium modules
Karaf-1900 create project for private compendium build for java 7
Karaf-1933 Add id for Maven repository
Karaf-1117 Remove workaround for KARAF-1117
Karaf-1655 ManagementCfg configuratoinPointers in tooling-exam are incorrect
Karaf-1489 Add an itest showing how to correctly use tinybundles with provision in paxexam-karaf

Updated Issues:
Karaf-1835 NPE in jaas:realm-manage command when multiple realm with the same name are present and not login module name is provided.
Karaf-1897 Use dynamic port allocation of integration tests

Un-versioned Issues:

Karaf-1925 Blueprint timeout exceptions after karaf startup
Karaf-1926 Web Console should show Blueprint status
Karaf-1928 Coloring in list shell command
Karaf-1927 Web Console bundles should be color coded
Karaf-1932 Color output in file logs
Karaf-1938 Lock logic should wait for start level change to occur
Karaf-1943 Add support to paxexam-karaf for testng
Karaf-1944 Add support to paxexam-karaf to attach jvm weavers to the process started
Karaf-1945 Add support to paxexam-karaf to support scanDir option for KarafTestContainer
Karaf-1946 Add pax-scanner & full pax-url support to paxexam-karaf
Karaf-1947 paxexam-karaf doesn't support to customize test probe
Karaf-1954 NullPointerException on custom Karaf shell command: ClassNotFoundException: org.apache.felix.service.command.Function not found
Karaf-1957 Allow to mark features as 'aggregate' features
Karaf-1902 Add a friendly option to point karaf-pax-exam to a already unpacked directory

Monday, October 15, 2012

Apache Karaf 2.3.0 Released!

The Apache Karaf team is pleased to announce the availability of Apache Karaf 2.3.0.


This release of Apache Karaf sets the stage for the 3.0.x line, introducing OSGi rev 4.3 support, new commands, features, improvements, and a multitude of dependency updates. At Karaf's core you'll find Equinox 3.8.0.v20120529-1548 and Apache Felix framework 4.0.3. New additions such as Karaf-pax-exam, commands back ported from Karaf 3.x, and command aliases to help make migrating between 2.3.x and 3.x easier, and a multitude of supporting libraries updates.

All of the updates seen in this kit would have broke compatibility if applied to the Karaf 2.2.x line, hence this new branch (command syntax remains the same however, so its part of the 2.x family - see Karaf 3.x for major changes).


For more information please see the release notes.

As discussed in my prior Apache Karaf 2.3.0 preparation post, I enjoyed listening to Esthero albums throughout the release process and was delighted to try the La Cour Pavillon Bordeaux Merlot - Cabernet Sauvignon 2009. I think the music and wine pairings are really working well for these releases, that being said if anyone has suggestions for future music or wine selections please post them below :)

Now that this 'dot oh' release is out, I can't wait for the up coming 3.0.0.RC1! Rest assured that patches for 2.2.x and 2.3.x will continue (and in the later case begin) on a regular basis.

Happy developing!

Sunday, October 14, 2012

Apache Karaf Update Oct 7 - Oct 13, 2012

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.10, 2.3.0, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.10:

New Issues:
N/A

Resolved issues:
Karaf-1911 Wrong version of camel-example-osgi in Getting Started/Quickstart Guide - 2.7.0 doesn't work
Karaf-1915 ClassCastException when uninstalling war feature
Karaf-1853 Attached kar deploys to a different snapshot build number than the main artifact
Karaf-1917 upgrade to pax-web 1.0.12

Updated issues:
N/A

Apache Karaf 2.3.0:


New Issues:
N/A

Resolved issues:
Karaf-1226 Karaf Client cannot run a script
Karaf-1904 Upgrade to Mina 2.0.7
Karaf-1878 Feature bundle start up order by startLvl
Karaf-1905 ASM4 causes the Proxy/Weaving of Xerces, but that then causes validation factories to fail.
Karaf-1906 Compile error using IBM JDK on JAAS module.
Karaf-1907 Compile error: type ServiceReference does not take parameters on OSGi Shell ListBundleServices using JDK 7
Karaf-1354 SSH Log-In failes with "Authentication failed" with valid credentials
Karaf-1908 Upgrade to XBean 3.12
Karaf-1909 Compile error using IBM JDK on management mbeans SystemMBeanImpl
Karaf-1907 Compile error: type ServiceReference does not take parameters on OSGi Shell ListBundleServices using JDK 7
Karaf-1910 Provide Spring 3.1.2.RELEASE features
Karaf-1911 Wrong version of camel-example-osgi in Getting Started/Quickstart Guide - 2.7.0 doesn't work
Karaf-1912 Test failures in itest.OsgiTest as aries proxy api is not bundle id 10 anymore
Karaf-1853 Attached kar deploys to a different snapshot build number than the main artifact

Updated issues:
Karaf-1336 Release Apache Karaf 2.3.0
Karaf-1563 Support clean-all & clean-cache directly in karaf main jar

Apache Karaf 3.0.0:

New Issues:
Karaf-1903 Refactore osgicore and osgicompendium modules

Resolved issues:
Karaf-1226 Karaf Client cannot run a script
Karaf-1904 Upgrade to Mina 2.0.7
Karaf-1878 Feature bundle start up order by startLvl
Karaf-1905 ASM4 causes the Proxy/Weaving of Xerces, but that then causes validation factories to fail.
Karaf-1354 SSH Log-In failes with "Authentication failed" with valid credentials
Karaf-1908 Upgrade to XBean 3.12
Karaf-1914 SSH client authentication randomly fails
Karaf-1853 Attached kar deploys to a different snapshot build number than the main artifact

Updated issues:
Karaf-1900 create project for private compendium build for java 7
Karaf-1563 Support clean-all & clean-cache directly in karaf main jar
Karaf-1887 Make integration tests more reliable by making sure the boot is finished

Un-versioned Issues:

Karaf-1901 Camel stream:out route destination freezes console if you try to stop or uninstall it
Karaf-1913 https://issues.apache.org/jira/browse/KARAF-1913

Friday, October 12, 2012

Preparing for Apache Karaf 2.2.10

The tenth maintenance release of the Apache Karaf 2.2.x branch will be soon entering the planning phase, as such I'm preparing for the release management role.

To prepare I've selected a bottle of Robert Skalli Reserve Cabernet Sauvignon 2009 to decant while listening to some Alexisonfire albums.

Current high lights of this patch include better Windows client support, improved SSH support on certain *nix systems, and an improvement to the features install sequence (install, install, install... start, start, start). Of course there will also be dependency updates such as moving to pax-logging 1.6.10, Spring 2.5.6.SEC03, and pax-web 1.0.12. A complete change log will be created for the Release Candidate once the community is ready to put it to vote.

The wine will of course only be sampled after being gave proper time to breath in its container, after the first release candidate has be up loaded for voting (see our release guide for more details on our process).

Unfortunately I can't share the wine with you, but I can share a few links to some Alexisonfire videos. I'm looking forward to starting the 2.2.10 release process soon.

I'll be posting updates to our Twitter stream (#karaf) and on our IRC channel (irc.codehaus.org #karaf).

Sunday, October 7, 2012

Anatomy of an Apache vulnerability report

Working with Savoir Technologies I get the opportunity to travel around the world helping companies, institutions, and other organizations design, implement and deploy large scale software systems. A large aspect of these deployments is introducing Apache projects as the underlying infrastructure. In general these projects are in Apache Servicemix, Karaf, ActiveMQ, CXF, and Camel as well as many other supporting libraries and frameworks. As part of this practice I've also taken to offering less formalized but highly attended lunch and learn opportunities to the sites I've visited. A pair of these talks I've bundled into a presentation I delivered at the BSides St Johns Security Conference 2012. In this post I'd like to share with you the first half of that talk "Anatomy of an Apache vulnerability report" - all of the information in this talk is available at the Apache Software Foundation's Security page (http://www.apache.org/security/), this talk's purpose is to raise awareness of the process for users and project communities alike.

Anatomy of an Apache vulnerability report

The Apache Software Foundation is the home of over 190 as of this post's writing, among them are some of the most widely deployed and relied upon software packages in the world. Chances are that you probably have some Apache software running somewhere with in your organization. This leads to an important question that all organizations must ask - what do we do if we find a security vulnerability within one of these projects? Luckily all Apache projects have a common process that they follow for addressing such situations, producing a report that other users may follow to mitigate or resolve known issues.

There is an established process for reporting security vulnerabilities to an Apache project, of which I'll now break down into it's component parts:
  1. The reporter reports the vulnerability privately to security@project.apache.org or to security@apache.org.
  2. Messages that do not relate to the reporting or management of an undisclosed security vulnerability in Apache software are ignored and no further action is required.
  3. If reported to security@apache.org the security team will forward the report (without acknowledging it) to the project’s security list or to the PMC private list if no security email list exists.
  4. The project team sends an email to the original reporter to acknowledge the report.
  5. The project team investigates the report and either rejects it or accepts it. 
  6.  If the report is rejected, the project team writes the reporter to explain why.
  7. If the report is accepted, the project team writes to reporter to let them know it is accepted and that they are working on a fix.
  8. The project team requests a Common Vulnerability and Exposures (CVE) number from security@apache.org by sending them an email with the subject “CVE request for...” and providing a short description of the vulnerability.
  9. The project team agrees the fix on their private list.
  10. The project team provides the reporter with a copy of the fix and a draft vulnerability announcement for comment.
  11. The project team agrees the fix, the announcement and the release schedule with the reporter.
  12. The project team commits the fix.
  13. The project team creates a release that includes the fix.
  14. The project team announces the release and the vulnerability: 
    • Typically this is sent to the reporter, project user, dev, and announce list. 
    • security@apache.org, full-disclosure@lists.grok.org.uk, and bugtrak@securityfocus.com are notified. 
    • Project security page is updated. 
    • This is the first point that any information is made public.
  15. The log for the svn commit that applied the fix is updated to include the CVE number.
Following this process a Common Vulnerability and Exposures report is recorded for the project. So what does a CVE include? Let's take a look at an example (click image on left for sample report - http://httpd.apache.org/security/CVE-2011-3192.txt):

  • Project website includes page titled: ${Project Name} Security Advisory
  • Header: Title, CVE #, Last change, Date created, Product, Versions affected.
  • Change log: Brief updates on verification, resolution.
  • Description: Describes the vulnerability, and how it behaves on different versions.
  • Type of Attack: DDOS, Permissions escalation, etc.
  • Background of vulnerability.
  • The Fix: What version does the fix appear in.
  • Caveats: Changes in behaviour.
  • Mitigation: Approaches to mitigating vulnerability in absence of fix.
  • OS and Vendor specific information: Platform specific reports/patches.
  • Actions: What users should do, and how to verify if susceptible.
  • Planning: future work regarding this CVE.

Each CVE will contain the sections as above, which should allow your organization to safely handle the challenges presented by any known issue.

I hope by reviewing the reporting process, and the contents of a CVE that users, developers, administrators, and operators in all organizations gain more confidence in their use of Apache projects, knowing that the community have planned for the worst case scenario and are prepared with processes and standards for addressing them in a timely manner.