mhm, maybe we would like to keep
"http://karaf.apache.org/xmlns/features/v1.0.0"; in some constants file
to avoid future changes at multiple locations?
On Sat, Apr 9, 2011 at 12:00 AM, wrote:
> Author: anierbeck
> Date: Fri Apr 8 22:00:13 2011
> New Revision: 1090462
>
> URL: http://svn.apache.
Karaf is complete atomic and standalone OSGi container.
It should run by itself (and it's still the case).
I think it's more logic for the projects to be build on top. Anyway, I'm
not against this new change as it could get life easy in the project.
David, did you launch a thread in the past on
I'd like to suggest that it would be more appropriate for other projects such
as servicemix to have one or more karaf-assembly packaging projects similar to
the apache-karaf-framework or apache-karaf-full assemblies but including
exactly the content wanted, rather than starting with a distribute
Before, I will check the impact on some other projects, especially
around the groupId/artifactId used.
We made a mistake by changing the groupId/artifactId of features, I
don't wanna to have the same issue with the distribution assemblies.
Projects like ServiceMix use the Karaf distribution in
I'd like to suggest that we remove the old assemblies/apache-karaf and use
instead the assemblies/apache-karaf-minimal and apache-karaf-full assemblies
constructed using the new mojos. I think we can also remove a lot of mojos
from the karaf-maven-plugin.
With the exception of some configurati
OK, I restored the transitive dependency o.a.k.shell.ssh >> sshd-core and
removed the o.a.k.shell.ssh from the framework kar ( and thus the
apache-karaf-minimal assembly) so all the bundles in minimal can start OK.
thanks
david jencks
On Apr 7, 2011, at 10:16 PM, Guillaume Nodet wrote:
> No, y
Hi
Is it accidental that Karaf expose the internal package?
The following 'headers' output shows
headers 13
Apache Karaf :: JAAS :: Config (13)
---
Manifest-Version = 1.0
Bnd-LastModified = 1298641818794
Tool = Bnd-1.15.0
Built-By = jgoodyea
Build-Jdk = 1.6.0_2
