Awesome, thanks!! :)
--
View this message in context:
http://karaf.922171.n3.nabble.com/Cellar-3-0-0-SNAPSHOT-tp4028863p4029075.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Good call! I just assumed it would use whatever followed as the command and
just didn't care about quotes. So I'm guessing by the s at the end of
features? I think I almost finished up the work I wanted to do on that
fork. One quick fix to make and check in which should fix a random error I
Will -p be added to 3.0.0 as well? Otherwise unit tests using 3.0.0 that
create and connect to a child instance won't be able to in an integration
test.
Ryan
--
View this message in context:
http://karaf.922171.n3.nabble.com/Cellar-3-0-0-SNAPSHOT-tp4028863p4029056.html
Sent from the Karaf -
Hi Ryan,
exactly, it's the plan. I gonna update 3.0.0 that way.
Regards
JB
On 06/17/2013 04:56 PM, rkmoquin wrote:
Will -p be added to 3.0.0 as well? Otherwise unit tests using 3.0.0 that
create and connect to a child instance won't be able to in an integration
test.
Ryan
--
View this
Ok, cool, I figured but just wanted to make sure. Is there an rough estimate
on on that feature? Just trying to plan ahead :)
Thanks!
--
View this message in context:
http://karaf.922171.n3.nabble.com/Cellar-3-0-0-SNAPSHOT-tp4028863p4029058.html
Sent from the Karaf - User mailing list
Let say tonight (my time) ;)
I reopen the Jira and work on that ;)
Regards
JB
On 06/17/2013 05:12 PM, rkmoquin wrote:
Ok, cool, I figured but just wanted to make sure. Is there an rough estimate
on on that feature? Just trying to plan ahead :)
Thanks!
--
View this message in context:
By the way, I checked the Cellar itests and I saw an issue in the
destroyCellarChild method.
We properly uninstall the cellar feature using:
System.err.println(executeCommand(admin:connect + name +
features:uninstall cellar));
but it's not correct as features:uninstall and cellar are
wrote:
So I finally am getting close to getting the Cellar 3.0.0-SNAPSHOT
integration tests working, but a bunch of the tests, after they create a
new instance, will cause a Login prompt to appear in the console. The
command to start the instance(s) eventually times out as a result
I tried -p and it complains it's not a valid parameter, is there anyway to
turn off security temporarily so I can see if I was able to fix 3.0.0? I'm
still crossing my fingers, but I'm thinking I might have.
--
View this message in context:
AFAIR, I introduce -p for backward compatibility only in 2.x series.
Let me check for the trunk.
Regards
JB
On 05/30/2013 12:58 AM, rkmoquin wrote:
I tried -p and it complains it's not a valid parameter, is there anyway to
turn off security temporarily so I can see if I was able to fix 3.0.0?
the Cellar 3.0.0-SNAPSHOT
integration tests working, but a bunch of the tests, after they create a
new instance, will cause a Login prompt to appear in the console. The
command to start the instance(s) eventually times out as a result.. is
there a way to handle that? or is there a parameter I could
Sounds great to me. So out of curiosity, if I'm checking out the source,
is it better for me to get it from github.com, git.apache.org, or apache
svn? It looks like JB checked in some changes when I look at the
git.apache.org karaf-cellar repo, which I tried merging with my checkout
from github.
Hi Ryan,
it's always nice to have some code contribution. And even nicer if those
are attached to Jira Issues ;)
Would be great if you could add some of the missing pieces as patches to
jiras.
thanks, Achim
2013/1/22 Ryan Moquin fragility...@gmail.com
Awesome, OK, I figured but I wanted to
That's my intention :-) I did submit a couple the other day linked to
Cellar pull requests regarding a discontinued Hazelcast component (JB
already took care of that one), an issue with the version of the
pax-mvn-url artifact and creating a kar for cellar as well as moving the
config files
Great to hear, and as I already said we love Contributions :D
Yeah those pull requests from Github don't really work out well with
projects hosted at Apache.
So Patches is much easier and afaik also better for IP clearances :)
thanks and regards, Achim
2013/1/22 Ryan Moquin
I don't know if you are interested by my apache cellar fork has all the
changes necessary to update the tests to use the apache karaf 3.0.0
commands which are different. I also added a group manager property in a
couple blueprint files to prevent NPEs during startup. Unfortunately, even
though
Hi Ryan,
I already fixed that on my local working copy. FYI, you may see an issue
with Cellar Features which pollutes the Karaf features service.
For now, I'm focus on Cellar 2.3.x (fixes, itests, etc). I will commit
both on Cellar 2.3.x and Cellar trunk in the middle of this week.
Regards
Awesome, OK, I figured but I wanted to check since I hadn't seen any check
ins yet. It was a good exercise in getting more familiar with the Cellar
code, glad you already have it dealt with.
I don't think I've seen that one yet, but I guess I'll find out. :-)
No prob, when you check in those
Hi Ryan,
yes, I started to work on both Cellar 2.3.x and trunk yesterday.
It should be better by the end of this week.
Regards
JB
On 01/16/2013 05:12 AM, Ryan Moquin wrote:
I know I was told that this version isn't stable yet, but I still wanted
to see if the build should be able to complete
No problem, I just want to figure out what the state of things are so I
know if it's just me or if it's possible it doesn't build. If it's
possible it doesn't I can file a couple jiras with suggested fixes for
you. The is also an enhancement request to file along with the suggested
fixes.
I know I was told that this version isn't stable yet, but I still wanted to
see if the build should be able to complete successfully or not. I want to
determine if some issues I'm having are something on my end or not.
Currently the itests always seem to fail with cellar trunk, is that the
21 matches
Mail list logo
