Hi,
Yes, this issue is reproducible even in Karaf 3.0.x.
After looking into the org.apache.karaf.client.Main class of 2.4.x/3.0.x, it
somehow try to read the ssh port from org.apache.karaf.shell.cfg at the
beginning.
Properties shellCfg = loadProps(new
File(System.getProperty("karaf.e
Hi,
I will do the fix (and the Jira). The purpose is to "automatically" get
the port, but it should not be a blocking statement (a try/catch with a
fallback would be better).
Regards
JB
On 02/02/2015 10:09 AM, XiLai Dai wrote:
Hi,
Yes, this issue is reproducible even in Karaf 3.0.x.
After
Hello,
My question is in the title : for a new project, which version of karaf
should we choose ?
When I read the blog post from Christian (
http://www.liquid-reality.de/display/liquid/2013/12/28/10+reasons+to+switch+to+Apache+Karaf+3).
I should use the version 3.
But on the official web site, i
Hi,
actually version 3 is "older" compared to version 2.4.
2.4 is there to have an easier transition phase between 2.3. and 3.0 since
we changed APIs in those versions.
So right now I'd go for 3.0.3 which has a good support.
OSGi 5 is only because the 3.0.3 line uses Felix 4.2.1, cause at that ti
Hi,
I second Achim there.
Again, the Karaf 2.4.x purpose is for migration: it's for the user that
wants to easily move from 2.3 to 3.0.
For a new project, from scratch, I would advice 3.x for GA.
Regards
JB
On 02/02/2015 10:56 AM, Achim Nierbeck wrote:
Hi,
actually version 3 is "older" co
Hi everyone,
can someone give me a hint about the best way to play with Karaf 4 and
Cellar please?
I triad installing Cellar 3.0.1 on Karaf 4.0.0.M1 and I got some weird
error:
>feature:install cellar
> Error executing command: Unable to resolve root: missing requirement
> [root] osgi.identity; o
Hi Milen,
Cellar 3.0.x is designed to work on Karaf 4.0.x.
I updated the Cellar master (4.0.0-SNAPSHOT) to work on Karaf 4.
I will push today and release Cellar 4.0.0.M1.
Regards
JB
On 02/02/2015 12:15 PM, Milen Dyankov wrote:
Hi everyone,
can someone give me a hint about the best way to pla
Short answer, yes to both.
Long answer, cellar master isn't optimized for Karaf Master right now. It's
for Karaf 3, as this is the latest release version. For Karaf 4 there will
be a new milestone release available. But again don't expect cellar to run
on it right away.
Regards, Achim
sent from
I already something "optimized" for Karaf master/4.0.0.M2 (refactoring
of the command, etc).
Let me push decanter and a couple of Karaf fixes, and I will push that ;)
Regards
JB
On 02/02/2015 12:19 PM, Achim Nierbeck wrote:
Short answer, yes to both.
Long answer, cellar master isn't optimized
By the way, in the mean time, I would advise you to use Karaf 3.0.x with
Cellar 3.0.x (if you want to experiment Cellar), waiting my push.
regards
JB
On 02/02/2015 12:15 PM, Milen Dyankov wrote:
Hi everyone,
can someone give me a hint about the best way to play with Karaf 4 and
Cellar please?
Thanks for your quick answers guys.
I already got Karaf 3.0.1 with Cellar 3.0.1 running.
I'm just trying to see how my app behaves on Karaf 4, thus the question.
I'm looking forward for your push ;)
Thanks again,
Milen
On Mon, Feb 2, 2015 at 12:23 PM, Jean-Baptiste Onofré
wrote:
> By the way
hurray an early adopter \o/
2015-02-02 12:29 GMT+01:00 Milen Dyankov :
> Thanks for your quick answers guys.
> I already got Karaf 3.0.1 with Cellar 3.0.1 running.
> I'm just trying to see how my app behaves on Karaf 4, thus the question.
> I'm looking forward for your push ;)
>
> Thanks again,
Hello,
I create a small project to provide a reasonable way to include support for
Eclipselink 2.5.2 in KARAF 3.0.3. This project provide a feature to install
Eclipselink 2.5.2 with JPA 2.1 support and example of modification needed in
persistence.xml. This modification are needed because Eclip
Could you provide an updated ETA for Apache Karaf 2.3.10?
We are interested in KARAF-3218 (KARAF-3075, KARAF-3417) and appreciate your
help on the ETA.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-10-release-ETA-tp4038215.html
Sent from the Karaf - User
Hi Xilai, hi JB,
thanks for looking into this. Will you consider backporting the fix to the
karaf 2.4 line as well ?
Thanks and Regards,
Michael
2015-02-02 10:14 GMT+01:00 Jean-Baptiste Onofré :
> Hi,
>
> I will do the fix (and the Jira). The purpose is to "automatically" get
> the port, but it
Thanks Rodrigo,
I will review and include the feature in Karaf.
Thanks again,
Regards
JB
On 02/02/2015 01:44 PM, Rodrigo Serra wrote:
Hello,
I create a small project to provide a reasonable way to include support
for Eclipselink 2.5.2 in KARAF 3.0.3. This project provide a feature to
install
Absolutely, I will fix on master, karaf-3.0.x, and karaf-2.x branches.
Regards
JB
On 02/02/2015 02:41 PM, Michael Täschner wrote:
Hi Xilai, hi JB,
thanks for looking into this. Will you consider backporting the fix to
the karaf 2.4 line as well ?
Thanks and Regards,
Michael
2015-02-02 10:14
Hi,
as you can see there:
http://karaf.apache.org/index/community/releases-schedule.html
the release was expected for this week end but we are a bit late.
I will deal with Jamie to release it tomorrow.
Thanks,
Regards
JB
On 02/02/2015 02:23 PM, Veerendra Vayyeti wrote:
Could you provide an
Sounds good :)
-J
On Mon, Feb 2, 2015 at 10:19 AM, Jean-Baptiste Onofré wrote:
> Hi,
>
> as you can see there:
>
> http://karaf.apache.org/index/community/releases-schedule.html
>
> the release was expected for this week end but we are a bit late.
>
> I will deal with Jamie to release it tomorro
Hi ServiceMix Users,
I ran into the "SpringProxy is not visible from class loader" issue
discussed a couple years ago in a different context were I configure a
JndiObject to be resolved later (when the contained reference is resolved).
Here the example config (excerpt):
The following impor
Hi All,
I'm using karaf-maven-plugin to create a customized distribution tar file.
The final tar.gz file name always following the artifact name. I did try to
use "finaName" and "targetFile" in configuration, but didn't work.
Looking at plugin source code, it seems that it's ignoring the "targetF
Hi
Could you please enable dynamic imports for your bundle, refresh it and
check which packages have been imported?
dev:dynamic-import xyz
osgi:refresh xyz
osgi:headers xyz
where xyz is id of your bundle. Compare it with your current imports.
Regards
Krzysztof
On 02.02.2015 14:53, Michael Täs
I just upgraded from karaf 3.0.1 to karaf 3.0.3.
With 3.0.3 I were not able to install the war feature:
karaf@root()> feature:install -v war
Installing feature war 3.0.2
Installing feature http 3.0.2
Installing feature pax-http 3.1.2
Installing feature pax-jetty 8.1.15.v20140411
Found installed
Hi Richard,
No, I didn't know this. Let me create a Jira to fix that.
Regards
JB
On 02/02/2015 05:18 PM, Richard Hierlmeier wrote:
I just upgraded from karaf 3.0.1 to karaf 3.0.3.
With 3.0.3 I were not able to install the war feature:
karaf@root()> feature:install -v war
Installing feature w
Hi,
I don't think it's a bug :-)
Most likely your local repository (the temp_repository) doesn't contain the
expected bundles.
Especially, it looks like it's missing the jettyconfig.xml
regards, Achim
2015-02-02 17:18 GMT+01:00 Richard Hierlmeier :
>
> I just upgraded from karaf 3.0.1 to kara
Hi Mohammad,
which goal are you using ? I guess just install-kar, right ?
You have to specify the instance-create-archive goal, which take the
result of the install-kar goal (target/assembly), and package as an
archive (zip/tar.gz archives).
This goal accepts a targetFile parameter.
So you c
By the way, is your local repository correctly populated ?
I mean, do you have all artifacts, features XML, jetty XML, config
files, etc located in your repo (from dependencies) ?
Regards
JB
On 02/02/2015 05:18 PM, Richard Hierlmeier wrote:
I just upgraded from karaf 3.0.1 to karaf 3.0.3.
W
Maybe you didn't do full mvn clean install to populate your repo, or
your pom.xml doesn't contain all required .
Regards
JB
On 02/02/2015 05:18 PM, Richard Hierlmeier wrote:
I just upgraded from karaf 3.0.1 to karaf 3.0.3.
With 3.0.3 I were not able to install the war feature:
karaf@root()>
Hi,
I am using karaf-assembly, following the documentation here :
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
Following you suggested solution, the result still is the same. maven
artifact name and version is used for tar.gz file.
As I mentioned in the email,
The MOJO uses the targetFile:
artifact.setFile(targetFile);
but you are right, it doesn't use the targetFile configuration and
construct the filename using artifactId + "-" + version.
Let me create the Jira to fix that.
Sorry about that.
Regards
JB
On 02/02/2015 06:12 PM, Mohammad Shamsi w
I created the Jira and I'm fixing it:
https://issues.apache.org/jira/browse/KARAF-3493
Regards
JB
On 02/02/2015 06:12 PM, Mohammad Shamsi wrote:
Hi,
I am using karaf-assembly, following the documentation here :
http://karaf.apache.org/manual/latest/developers-guide/custom-distribution.html
F
I created the Jira:
https://issues.apache.org/jira/browse/KARAF-3494
I'm working on it.
Regards
JB
On 01/29/2015 11:43 AM, Michael Täschner wrote:
Hi,
recently we upgraded ServiceMix from 5.1.3 to 5.3.0 based on Karaf 2.3.x
and 2.4.x respectively. We manage our own customized container where
Hi,
Have you had a chance to look into this?
Thank you!
--
Stephen Kahmann
Software Engineer
iNovex Information Systems, Inc.
937-321-1923
stephen.kahm...@inovexcorp.com
Confidentiality Notice: This message is intended for the sole use of the
individual to whom it is addressed and may contai
Hi Stephen,
yes, I started a enhancement on the MOJO about that. I have to push that.
Regards
JB
On 02/02/2015 07:09 PM, Stephen Kahmann wrote:
Hi,
Have you had a chance to look into this?
Thank you!
--
Stephen Kahmann
Software Engineer
iNovex Information Systems, Inc.
937-321-1923
stephen
Great. thanks
On Mon Feb 02 2015 at 6:43:56 PM Jean-Baptiste Onofré
wrote:
> I created the Jira and I'm fixing it:
>
> https://issues.apache.org/jira/browse/KARAF-3493
>
> Regards
> JB
>
> On 02/02/2015 06:12 PM, Mohammad Shamsi wrote:
> > Hi,
> >
> > I am using karaf-assembly, following the doc
35 matches
Mail list logo
