-1: I don't really see any real benefit In changing the current approach to
DS.
There are minor pros and cons in each approach, but the less external
dependencies the better.
Also less is more :-)
--
*Ioannis Canellos*
*Blog: http://iocanel.blogspot.com <http://iocanel.blogspot.com/>*
*T
that the change you propose makes sense.
Other thoughts?
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
create an annotation processor that would help reducing the annotation
boilerplate in commands it could take a little less.
This has been scheduled for 4.x. I don't know when 4.x is planned.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
OK then 4.x it is.
And when do u feel its the right time to create a 4.x branch?
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
of the projects of the eco
system to pickup those features, were necessary.
When camel, cxf, activemq have picked up the changes in our features
and have performed a release or two, we can proceed to the final step
and have Blueprint not installed by default
Thoughts?
--
Ioannis Canellos
Blog: http
if as you said, you should not have impact).
This is another good reason, for not rushing a 4.x release.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
overhead). We could use this time and
follow Dan's suggestion about letting other projects adopt the feature
changes. But still it does sound like a long time which is meant to
become even longer as new features will pile up for 4.x.
Thoughts?
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
for a pure
OSGi api solution, since you gain (i) (ii) but still loose all the
others and also have the burden of maintenance.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
to be extra careful to prevent
concurrency issues and the resulting code will be hard to deal with
(tons of boilerplate all over the place).
And of course, transparency and control wise we wouldn't even be as
near as DS can get us ;-)
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
with different versions/implementations of
Blueprint etc.
So this is actually a step forward.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
no Blueprint should be an option.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
imho.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
If the distribution only starts framework, config admin, scr pax-url
karaf features, then minimal = net.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
-1
The minimal distribution does not work, which sounds like a show stopper?
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
offline without issues. This seems to be
broken post 3.0.0.RC1.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
internet connection ( a net installer distro ), if its
size justifies the effort.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
will have to bear the burden of maintaining 2.3, 3.x 4.x
for a while. If 3.0 is something that is going to happen next week or
the week after I could do some late nights to rebase to 3.0 (helping
hands are more than welcome).
wdyt?
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter
I would like to clarify, that DS is not an alternative DI framework.
It's more like a component framework that shines at managing the
lifecycle/dependencies of components than anything else.
Karaf itself hardly ever use traditional DI. So far it has been using
Blueprint in order to wire services
(e.g. 2.4).
We don't want to stall 3.0.0 any longer. We also don't want to
maintain 3 different major branches. Since moving it to 3.1 totally
respects semantic versioning, I think that we could go with that.
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
. But that
doesn't mean that we should use the same things that the users will
do. The users are building apps and they can pick the most fitting
tool and we on the other hand are building a runtime and we need to
pick the best tool for our job. It doesn't have to be the same tool.
--
Ioannis Canellos
Blog
feature in it).
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
(2.3.4.SNAPSHOT)
[ 11] [Active ] [ 30] Apache Karaf :: Shell :: Log Commands
(2.3.4.SNAPSHOT)
[ 12] [Active ] [ 30] Apache Karaf :: Shell :: OSGi Commands
(2.3.4.SNAPSHOT)
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
+1
Conceptually, since parent and children share the same system folder,
they should also share the same startup.properties and most probably
config.properties too.
--
Ioannis Canellos
to JMX:
https://github.com/bosschaert/karaf/commit/bfee2d1b2c736c9b54cbfce8e4b07c8cfadf980f
Best regards,
David
dav...@apache.org
da...@redhat.com
david.bosscha...@gmail.com
--
Ioannis Canellos
Blog: http://iocanel.blogspot.com
Twitter: iocanel
://blog.nanthrax.net
Talend - http://www.talend.com
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
/display/paxweb/Pax+Web/ Committer
Project Lead
OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home
Commiter Project Lead
blog http://notizblog.nierbeck.de/
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
in any case I think this shows we should have a good concept for
package versioning for API packages.
What do you think?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
*Ioannis
to share what you did, I would be glad to review it with you.
Regards
JB
On 2013-04-24 14:41, roedll wrote:
More than a year ago Ioannis Canellos posted that he added a
rudimentary scheduler as a new module to trunk. (See
http://karaf.922171.n3.nabble.com/Introducing-a-task-scheduler
The more complex the wiring is, the largest the number of potential issues.
Let's keep things as simple as possible.
Moreover, I find the large number of bundles, as a result of unwinding libs
intimidating to the new users.
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
+1
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
The minimal distribution fails to start because its missing
the org.apache.karaf.jaas.authz-2.3.1.jar from the system repo.
Having one of two flavor not being able to start, seems like a show
stopper, but I am not sure. What do you thing?
--
*Ioannis Canellos*
*
**
Blog: http
that we should maybe start with this point but maybe
also grant the user the power to do things like i) and ii).
I hope I didn't miss anything.
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Currently we are at 2.3.0 and 2.2.10. Does it mean that if we get out 2.4
to provide new features to our users, we will stop working on 2.2.x?
How would this work when we get 3.0.0 out?
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
+1 on creating a 2.4 branch.
Personally I am ok at adding new features on micro releases as long as they
don't change the API, especially considering the speed at which we bring
out new major and minor ones.
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
I've update issue: https://issues.apache.org/jira/browse/KARAF-2044
with 2 patches, one for trunk and one for 2.3.x.
If there are no objections I'd like to commit those and maybe also for
2.2.x.
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
I moved the project to https://github.com/jledit/jledit and cut a first
release. So we can finally add a command for editing.
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
For now I have pushed it at: https://github.com/iocanel/vial
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
.
Of course, there is always the maintenance burden of an extra subproject
which we should take into consideration.
Thoughts?
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
and a lot of space for improvements and
I was wondering which would be the ideal home for this project.
Thoughts?
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
+1
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
etc.
Thoughts?
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
+ 1 for the 2.2.10 RC.
We can discuss about 3.0.0 in an other thread.
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
descriptor natively (spring for instance).
Yeah, we took the discussion a bit far... :-D
So for spring, since there are now actual ties to Karaf we could do that. I
don't know for the enterprise features.
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
to be the versions of fileinstall and karaf that the deployer will be built
against?
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Tried with various projects that provide Karaf features.
Here's my +1
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
I agree with JB at all points.
I feel that holding back 2.3 in favor of 3.0.0 was a bad idea and I
wouldn't want to see the same happening to future 2.x versions.
If there is need for a 2.4 let's get it done regardless of when we'll do
3.0.0.
--
*Ioannis Canellos*
*
**
Blog: http
I don't like the aliases either for the same reasons (completion).
+1
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
already have, isn't it?
--
*Ioannis Canellos*
*
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
we release karaf 3 or until we have an other target platform than karaf
2.2.x. This will reduce the maintainance.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
I've no problem with either of those since the 4.3 release of the core
does not break backward compatibility (compared to 5.0) -- also fine
with that approach (BUT, AFAIK 2.3.x had been ported to 4.3 already)
Then our views are completely aligned :-)
--
*Ioannis Canellos*
*
FuseSource http
+1
in mind.
Thoughts?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
and not something based on objective criteria).
I couldn't oversee however the fact that the felix webconsole is widely
used, people have built stuff on top of it, etc.
Would it be possible to reuse/wrap/bridge felix webconsole stuff in
karaf-webconsole?
--
*Ioannis Canellos*
*
FuseSource http
, service etc) and have everyone configure it
however he wishes.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
that are meet.
I think that this would be really usefull, especially for the management,
diagnostic, webconsole related features.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Ideally, a micro release should guarantee forward and backward
compatibility.
I'd say though that the particular issue doesn't sound like a show stopper
to me.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
class that uses a System.exit as a workaround.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
JB, I was about to bring this proposal forward myself!
A huge +1.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
though :-)
Totally agree, the question is do we care if the threads are cleaned up
properlly when using bin/shell. From what I understand the purpose is to
execute commands outside OSGi, so that they can be used in scripts etc. In
such case exiting fast seems really important.
--
*Ioannis Canellos
Hi Brian,
thanks for the contribution. Whatever, option you choose it will be highly
appreciated :-)
I'll try to find some cycles and review your patch.
Keep it up!
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Guys, why don't we use maven filtering capabilities and have different
filters per profile?
We could then use a release profile with clean repo configuration while the
rest of profile use snapshots to aid development.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http
I may lost some bits, but couldn't we just reuse the users keys and
authorized hosts, instead of creating, adding or removing?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
should leave them as they are.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Why not having jdk 1.7 support in the 2.2.x branch?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
urls, some other have broken features etc.
I am giving it a +1, as it is definitely not a show stopper, but we do need
to improve this.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
True, but releasing 3.0.0 should not block us from delivering functionality
to 2.2.x or even 2.3.x.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Agree, it something that even us got really confused about, imagine the
impact that will have on the users.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Great news!
I'd like to make a really trivial aesthetic comment. Could the sub
shell prompt have no parenthesis when no sub shell is active:
karaf@root region
karaf@root(region) exit
karaf@root
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
I think we also have a new committer, don't we?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
+1 for the GSOC and Andreas idea.
I have said in the past, that we have a lot of sub projects for our size.
Maybe we need to come with more ideas about sub projects.
Any idea how are we going to draw the students attention?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog
I don't know if its up to date. I was under the impression that you can use
the bouncy castle jce provider just by installing it as bundle.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
(please provide specific comments)
This vote will be open for 72 hours.
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
Yes, it makes sense to me. My main point was that since it was such an old
request it should be propably ported to 2.x.something too. A 2.2.3 sounds
great to me!
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http
rather than built inside the distro, so that its easier to add,
remove update urls or even have different ranges for different karaf
versions.
Since the user will need to have internet access in order to install those
urls, I think it really makes sense. What do you think?
--
*Ioannis Canellos
Karaf. But I really
don't think that this would be a problem.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http
I agree with Andreas here. I think that they are beyond Karaf's scope.
Maybe they should be part of ServiceMix or an other project.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel
and that's the purpose of my email. Can
you please confirm if its ok to do so?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix
Thanks for the responses! I'll give it a shot.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http://servicemix.apache.org
of, that goes the other way around (building EE features on top of
OSGi).
I am really curious to see how it will evolve.
Really interesting stuff.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer
Hi,
is it just me or the error messages have been messed up? I
was experimenting on a fresh trunk and I noticed that bundle:install
feature:add-url commands, no longer display what went wrong (e.g.
unresolved constraints etc). Is this something that is done on purpose?
--
*Ioannis Canellos
.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http://servicemix.apache.org/ Committer
Apache Gora http://incubator.apache.org/gora
license at apache. So it stays available for us in the future?
It does for me. I really like this idea.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org
An other glitch I found is that the code completion on the config:list
--pid is not working (it works for the rest of the config commands). Not a
show stopper.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org
+ 1
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http://servicemix.apache.org/ Committer
Apache Gora http
is becoming a
trend ... )
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http://servicemix.apache.org/ Committer
Apache Gora http
had the time. An archetype for gwt that will include those patterns
would be awesome.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache
projects and Karaf can
register to a features Cave repository (like a Maven repo).
Regards
JB
On 12/15/2011 11:52 AM, Ioannis Canellos wrote:
I think that we all are +1 on the effort Charles put to integrate Karaf
with OpenEJB. Different views has been expressed on where and how (I
, that I am not against a KarafEE subproject, I am
just not sure if we have the numbers to support it. From my experience with
Cellar, I see that the maintenance of a subproject requires a lot of effort.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
Kudos to Charles for the work with the OpenEJB community.
My only slight concern is that the number of sub projects is getting big
compared to the size of the community.
On 14 Δεκ 2011, at 4:35 μ.μ., j...@nanthrax.net wrote:
Hi Glen
SMX doesn't include OpenEJB. It's an integration oriented
As we are marching towards 3.0.0 release and we haven't done anything about
it (its still in primitive state) maybe its a good idea to remove it from
trunk and maybe put it in the sandbox or something.
What do you think?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http
Yes, I was thinking something like this.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http://servicemix.apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http
installed, since the resolver
belives that the dependency is already met (which is not true).
I am doing something retarded here, or is this package command/admin thingy?
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http
I would assume that it only needs it for associating sh extention with
cygwin. But I can't know for sure, I haven't used a directx container for a
while :-P
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org
Awesome !!!
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http://servicemix.apache.org/ Committer
Apache Gora http
Awesome!
Let's start focusing for mid December and see how it goes!
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http
can see that blobstore core
bundle can't get attached to jclouds-core.
Thanks.
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix
+1
Note: Since we have put in several jaas improvements, I would like also
like to see a backing engine for ldap, so that jaas commands can be used
with the ldap login module. So if anyone has a few cycles for it, that
would be great!
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
1 - 100 of 196 matches
Mail list logo
