Never mind, I misread the dates on the checkins from the one mirror... I
didn't fully read it and made an assumption.. so that explains that.. I'll
keep waiting :)
Ryan
On Jan 25, 2013 6:18 PM, "Ryan Moquin" wrote:
> Ah, interesting. OK. Yeah it doesn't look like everything in got is as
> up
Ah, interesting. OK. Yeah it doesn't look like everything in got is as up
to date as svn. So then the question becomes why I still can't build even
when I check out of svn. The pax mvn URL artifact can't be resolved, the
pax whether URL artifact only can if I add the pax snapshots repo and the
Right now svn is still the only "valid" source. Git-hub is just a mirror
and karaf isn't available at git.apache.org yet, this would require us to
transition the sources there which we haven't fully discussed yet. :-)
Regards, Achim
sent from mobile device
Am 25.01.2013 22:27 schrieb "Ryan Moquin
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.
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
> That's my intent
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 around
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
> Awesome, OK, I figured but I wanted to check since I hadn't s
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 fix
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.
Regard
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 thos
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. Anyhow
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 s
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
current
13 matches
Mail list logo