I just did: svn update mvn clean install and during integration tests I see: java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal (which is part of xerces).
2013/2/11 Karl Wright <[email protected]> > Xerces dependency is still present; it's just a stock 2.10.0 > xercesImpl dependency. So this is a puzzle to me - especially since I > see no failure here when I run mvn clean install. > > Karl > > > On Mon, Feb 11, 2013 at 5:00 AM, Maciej Liżewski > <[email protected]> wrote: > > removing xerces dependancy makes elasticsearch integration tests fail > when > > building with maven. Testing if adding this dependency just to IT will > > solve the issue. > > > > > > 2013/2/10 Karl Wright (JIRA) <[email protected]> > > > >> > >> [ > >> > https://issues.apache.org/jira/browse/CONNECTORS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575565#comment-13575565 > ] > >> > >> Karl Wright commented on CONNECTORS-633: > >> ---------------------------------------- > >> > >> r1444628 > >> > >> > >> > Look into using simple tag parser, from Web Connector, for RSS parsing > >> needs > >> > > >> > ---------------------------------------------------------------------------- > >> > > >> > Key: CONNECTORS-633 > >> > URL: > >> https://issues.apache.org/jira/browse/CONNECTORS-633 > >> > Project: ManifoldCF > >> > Issue Type: Task > >> > Components: RSS connector, Web connector > >> > Affects Versions: ManifoldCF 1.2 > >> > Reporter: Karl Wright > >> > Assignee: Karl Wright > >> > Fix For: ManifoldCF 1.2 > >> > > >> > > >> > Our last major custom dependency is on a hacked version of xerces. > This > >> was done initially to fix a memory leak, and to allow parsing of > "sloppy" > >> RSS feeds. We might be able to eliminate this if we verify that the > memory > >> leak has been fixed in a more modern xerces, and we move towards using > our > >> homegrown sloppy tag parser developed for the Web connector, for RSS > feed > >> processing. > >> > >> -- > >> This message is automatically generated by JIRA. > >> If you think it was sent incorrectly, please contact your JIRA > >> administrators > >> For more information on JIRA, see: > http://www.atlassian.com/software/jira > >> >
