I can't find the serializer.jar in 2.0.9 SNAPSHOT, but I found it in
2.1.3 SNAPSHOT.
After went through the commit log , I found there is one different between
rt/ws/security/pom.xml in 2.0.x and 2.1.x ,
the xalan's dependency scope is runtime in 2.0.x, and uses the default compile
scope in 2
On Thursday 09 October 2008 10:13:08 am Willem Jiang wrote:
> Does the java.lang.NoClassDefFoundError:
> org/apache/xml/serializer/TreeWalker relates to change of updating to
> using xalan 2.7.1 ?
Yea. Where are you seeing that?
There is a new jar (serializer.jar) in lib that contains that c
Does the java.lang.NoClassDefFoundError:
org/apache/xml/serializer/TreeWalker relates to change of updating to
using xalan 2.7.1 ?
Daniel Kulp wrote:
Willem,
Thanks for volunteering to do this. That's great.
I think it would be good to do 2.0.9 late this week and probably 2.1.3
middle o
Hi Dan,
I just deployed a new snapshot of CXF 2.0.9 according the wiki page for
testing my box's ssh and scp setting.
Every thing is working, I am ready for cutting CXF 2.0.9 this week :)
Willem
Daniel Kulp wrote:
Willem,
Thanks for volunteering to do this. That's great.
I think it would
Willem,
Thanks for volunteering to do this. That's great.
I think it would be good to do 2.0.9 late this week and probably 2.1.3
middle of next week. (need to do 2.0.x first due to an "issue" with
the maven stage plugin which will update the "latest" tag in the
metadata with 2.0.9 so 2.0
Hi Christian,
Can you list the cases in which the patches could change the old JMS
transport behavior?
Maybe we should add some wiki page for the upgrading of user.
Regards,
Willem
Christian Schneider wrote:
Hi Willem,
if you are allright with it then that is ok. I am sure there are some
Hi Willem,
if you are allright with it then that is ok. I am sure there are some
cases in which the implementations behave differently. But they are
probably not very common or important.
Greetings
Christian
Willem Jiang schrieb:
Hi Christian,
All your JMS refactoring patches are in the 2
Hi Christian,
All your JMS refactoring patches are in the 2.0.x branch and the test result
looks good :)
Willem
On Sat, Oct 4, 2008 at 8:30 AM, Willem Jiang <[EMAIL PROTECTED]> wrote:
> Hi Christian,
>
> Most of your JMS patches were merged into the 2.0.x branch , and there are
> not much diffe
Hi Christian,
Most of your JMS patches were merged into the 2.0.x branch , and there
are not much differences between the CXF 2.0.x JMS module and CXF 2.1.x
JMS module. I think it is easy to merge your latest change into the CXF
2.0.x.
Don't worry , I will keep on an eye on it ;)
Willem
Chri
Hi Dan,
I have got a question about the new releases. Should we include the
changes in the JMS transport in one of them?
Ron Gavlin asked to include the changes in the 2.0.x branch on the jira
issue https://issues.apache.org/jira/browse/CXF-1832.
I could imagine to include them into 2.1.3 but I
Willem,
Any chance you still talk to Bo Lin? Maybe take him out for a beer or
something and do a quick key signing.
Actually, you could do the same with Freeman as well. His key is signed
by Bo which is signed by me and others.
Dan
On Thursday 02 October 2008, Willem Jiang wrote:
> Hi D
You need a secure means of exchanging keys. In general email is not a
trustworthy mechanism, as it is clearly tamperable. A phone call is
marginally better. Though given the current news about skype, I'd
think twice about that, too ;)
Of course, you might even say face-to-face is not sec
Hi Dan,
I'd like to take charge of this CXF release.
Since you and me met a year before, I will send you my key for signing :)
Cheers,
Willem
On Fri, Oct 3, 2008 at 12:49 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> We're rappidly approaching time to do the 2.0.9 and 2.1.3 releases.
> It's b
We're rappidly approaching time to do the 2.0.9 and 2.1.3 releases.
It's been about 10 week since 2.0.9 and 7 weeks since 2.1.2. We have
33 issues resolved for 2.0.9, and 38 for 2.1.3. Thus, we probably
should consider doing some releases shortly.
HOWEVER, my hard drive crashed this week
14 matches
Mail list logo
