With Tom's fix and my commit for fixing license header issues, what
should we do next? Shall we cut a new build out of mainline, or shall we
migrate those fixes to M1 tag and build new kit from M1 tag? I am ok to
cut a new build from mainline, since it includes several fixes for
Eclipse tooling in the last week and also includes some servlet
transport improvement/fixes.
Any thoughts?
Cheers,
Bo
Li, Tao (Tom) wrote:
Hi Dan.D,
Sorry for the issues brought by mtom module.
I've commited a fix for mtom, now it only has systest & demo
for xop, the swa case has been discarded.
If we using import from the location set to network, the demo can
also support the swa feature without involve license issues.
But previousely we have already made efforts to let the build &
demo working in offline mode.
It's better that not break the offline support. So I discard the swa
cases even our system support it.
Please help to review and give your comments.
Thanks.
Tom
-----Original Message-----
From: Dan Diephouse [mailto:[EMAIL PROTECTED]
Sent: 2006?11?23? 17:48
To: [email protected]
Subject: WS-I license issues, MTOM sample from JAXWS-RI
I've removed all copies of the wsi-swa.xsd under the WS-I
license per the
request from Robert on [EMAIL PROTECTED] as it is not legal
for us to have
them in SVN. If anyone knows of other files please speak up.
We should go
through and double check that all the files which use licenses from
standards organizations are OK. Yes, this breaks the build,
but immediate
action needed to be taken.
ALSO, the MTOM sample and the MTOM WSDL/XSD in testutils appears to be
directly copied from the JAX-WS RI. It may have ultimately
originated from
somewhere else, but I can't figure out where. If this it did
come from the
JAX-WS RI, it is VERY not cool. CDDL sources can not be
included in Apache
SVN. If there are any other things that people have copied,
speak up now and
get them removed ASAP.
- Dan
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
