You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "David Johnson (JIRA)" <no...@atlassian.com> on 2007/07/01 18:04:31 UTC
[Roller-JIRA] Resolved: (ROL-1379) Upgrade to Apache XMLRPC 3.0
[ http://opensource.atlassian.com/projects/roller/browse/ROL-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Johnson resolved ROL-1379.
--------------------------------
Resolution: Fixed
Work complete in trunk
> Upgrade to Apache XMLRPC 3.0
> ----------------------------
>
> Key: ROL-1379
> URL: http://opensource.atlassian.com/projects/roller/browse/ROL-1379
> Project: Roller
> Issue Type: Improvement
> Components: Web Services
> Affects Versions: 4.0
> Reporter: David Johnson
> Assignee: David Johnson
> Fix For: 4.0
>
>
> The Apache XMLRPC project made a major new release in August 2006, it's first in over two years.
> Why should we upgrade?
> 1) Numerous bug fixes and improvements, see full list:
> http://ws.apache.org/xmlrpc/changes-report.html
> 2) We've been using a Beta release of Apache XMLRPC 1.2 and there are some open issues that cause problem with some character encodings (I notice them when I repost my del.icio.us links to my blog via XMLRPC).
> 3) Brings us in alignment with Apache XMLRPC project. By using their latest release, we make it easier for them to support us.
> I've got XMLRPC 3.0 running with Roller in my workspace and I haven't found any problems yet.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira