If there was a backward compatibility issue, then the build would have informed you about it. Operators that are marked evolving can be modified, see the compatibility section in the documentation.
The bugs need to be addressed of course. -- sent from mobile On May 11, 2016 6:44 AM, "Munagala V. Ramanath (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/APEXMALHAR-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280132#comment-15280132 > ] > > Munagala V. Ramanath commented on APEXMALHAR-2083: > -------------------------------------------------- > > Additionally the argument to DocumentBuilder.parse() needs to be fixed > since that method does not take an XML string; easiest is to make an > InputSource out of the tuple. > > > Revert breaking changes to XmlParser in release 3.3 > > --------------------------------------------------- > > > > Key: APEXMALHAR-2083 > > URL: > https://issues.apache.org/jira/browse/APEXMALHAR-2083 > > Project: Apache Apex Malhar > > Issue Type: Bug > > Components: utilities > > Affects Versions: 3.3.1 > > Reporter: Munagala V. Ramanath > > > > XmlParser was changed in 3.3 in a way that is not backwards compatible. > We need to revert this change in both 3.3 and 3.4. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
