Hi JB,
thanx for the reminder :)
I didn't expect it to be an easy change ;)
regarding
1) I'll open an issue for it and will fix it tonight, or whoever is
going to be first ;)
2) well the naming change was just to be able to test the current
features.xml of pax web with Karaf 3.0 this can be changed in pax-web if
required (I actually think would make the transition more smoothly :) )
3) well instead of depending on the pax-web bundles it's now on the
features, so I guess this I can live with ;)
regards, Achim
Am 16.11.2011 18:55, schrieb Jean-Baptiste Onofré:
Hi Achim,
it makes sense for me.
However, we have some fixes/concerns to address first:
1/ Pax Web features doesn't define the namespace: it's now a
requirement to validation in Karaf 3.0
2/ the features name have changed: jetty is now pax-web-jetty, http is
pax-web-http, war is now pax-web-war. It means that we have to clearly
address the projects that use it (Cellar, Cave, Camel, SMX, Geronimo,
CXF, etc, etc) and upgrade it
3/ Same comment about the version: it means that the version of http,
war, etc features are not the same as Karaf. So it means that "others
projects" should now the Pax Web version in use, and define the right
version range.
Regards
JB
On 11/16/2011 06:35 PM, Achim Nierbeck wrote:
Hi all,
I added KARAF-1017 [1] as proposal to remove the war and http feature
definitions from the Karaf std. features file
and replace it with the features.xml provided by Pax web. This of course
just for Karaf 3.0 in conjunction with Pax Web 2.0
which I hope to release in the near future :)
Any comments, objections :)
Regards, Achim
[1] - https://issues.apache.org/jira/browse/KARAF-1017
--
--
*Achim Nierbeck*
Apache Karaf<http://karaf.apache.org/> Committer& PMC
OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer&
Project Lead
blog<http://notizblog.nierbeck.de/>
