Tracking trunk commits blocked wrt to the 2.0.x_fixes branch

2008-07-17 Thread Eoghan Glynn
Folks, Does anyone know if svnmerge.py can be used to report on the commits to trunk that have been "blocked" wrt to merging out to the 2.0.x_fixes branch? Its sortta like a retrospective "avail" option that I'm after, i.e. gimme all the commits that were available for merging, but were sele

Re: Tracking trunk commits blocked wrt to the 2.0.x_fixes branch

2008-07-17 Thread Freeman Fang
Hi Eoghan, I guess what you want is "svnmerge.py avail -B", which will showthe blocked revision list. Regards Freeman Eoghan Glynn wrote: Folks, Does anyone know if svnmerge.py can be used to report on the commits to trunk that have been "blocked" wrt to merging out to the 2.0.x_fixes b

Re: Tracking trunk commits blocked wrt to the 2.0.x_fixes branch

2008-07-17 Thread Daniel Kulp
It's all stored as properties on the directory. Thus: svn propget svnmerge-blocked . would give you the list of revisions. THAT said, the stuff gnodet, Freeman, and Willem have merged without using svnmerge.py may appear in that list. On a related note: I'm not using subversion 1.5

Re: Tracking trunk commits blocked wrt to the 2.0.x_fixes branch

2008-07-17 Thread Eoghan Glynn
Thanks Dan & Freeman, Both suggested methods give exactly the same results. A total of well over blocked 500 commits ... ouch, that's a lot to go thru manually. BTW what's general feeling on the completeness of the 2.1 Migration Guide[1] wrt capturing potential compatibility issues? Cheer

A CXF 2.1 CPU consumption question

2008-07-17 Thread David Soroko
Hello all I apologise for cross posting, but I was not getting much traction in the users-list and I do think that my question is worth asking and answering. Here is what I have so far: Hello Daniel I had another profiling session and this time saved the snapshot so we ca

Re: A CXF 2.1 CPU consumption question

2008-07-17 Thread Glen Mazza
David, the very same developers are on both lists. Best to follow up on the User's list to keep the archives clean for future searching. Glen David Soroko wrote: > > Hello all > > > > I apologise for cross posting, but I was not getting much traction in > the users-list and I do think tha

RE: Tracking trunk commits blocked wrt to the 2.0.x_fixes branch

2008-07-17 Thread Johnson, Eric
I was wondering the same thing about the migration guide -Original Message- From: Eoghan Glynn [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2008 10:10 AM To: dev@cxf.apache.org Subject: Re: Tracking trunk commits blocked wrt to the 2.0.x_fixes branch Thanks Dan & Freeman, Bo

Re: A CXF 2.1 CPU consumption question

2008-07-17 Thread Daniel Kulp
On Jul 17, 2008, at 10:10 AM, David Soroko wrote: Hello all I apologise for cross posting, but I was not getting much traction in the users-list and I do think that my question is worth asking and answering. Doesn't really matter, although I do disagree with Glen on this. This really is a "

Re: A CXF 2.1 CPU consumption question

2008-07-17 Thread Glen Mazza
dkulp wrote: > > > On Jul 17, 2008, at 10:10 AM, David Soroko wrote: >> Hello all >> I apologise for cross posting, but I was not getting much traction in >> the users-list and I do think that my question is worth asking and >> answering. > > Doesn't really matter, although I do disagree with

Re: Tracking trunk commits blocked wrt to the 2.0.x_fixes branch

2008-07-17 Thread Daniel Kulp
For the most part, the migration guide covers everything that I've seen people comment on in the forums. That's not saying it's 100% complete, but it's probably a good start. Feel free to add to it as you audit the commits. :-) Dan On Jul 17, 2008, at 10:22 AM, Johnson, Eric wrote

(moved from cxf-user) Re: configuring password for services via Spring in Apache CXF 2.1.1 (so that username, password, endpoint, etc. can be set on client bean via Spring)

2008-07-17 Thread Glen Mazza
Oh I see--I think you already merged the WSS4JInInterceptor one in 2.0.x, it's just the WSS4JOutInterceptor we're talking about. I'm OK either way about changing the code because regardless, I think I can rephrase the CXF documentation anyway and make that SAAJInterceptor notice somewhat more mino