Thank you for checking this out. I think if you find the same to be true of the 1.1.1 release candidate, you could consider giving it your +1. ;-)
Karl On Tue, Feb 12, 2013 at 7:42 AM, Maciej Liżewski <[email protected]> wrote: > great. today I wiped out maven cache, exported fresh sources from trunk and > everything went ok. probably after your changes :) > jetty-runner also runs with maven without problems. > > > 2013/2/12 Karl Wright <[email protected]> > >> I wound up adding a new dependency wherever xerces was found: >> xml-apis, version 1.4.01. It seems like the xerces pom should contain >> a dependency on this but doesn't. We already download this version >> for ant, so that is why it worked there. >> >> Karl >> >> On Mon, Feb 11, 2013 at 9:46 PM, Karl Wright <[email protected]> wrote: >> > On a trunk checkout, I tried "ant make-core-deps clean build test" and >> > that was fine. Running "mvn clean install" right now to see if that >> > too is fine. Both should use the same version of xerces (2.10.0), so >> > unless there is a screwed-up maven dependency, this ought to work too. >> > >> > Karl >> > >> > On Mon, Feb 11, 2013 at 9:04 AM, Karl Wright <[email protected]> wrote: >> >> "mvn clean instal"l worked fine for me yesterday on trunk. So it's a >> mystery. >> >> >> >> I'd suggest blowing away your maven repository and trying again, but I >> >> can't think of any reason why that might help, unless you've got a >> >> partly-installed jar in there or something. >> >> >> >> I can't do further maven tests until this evening. But if you want to >> >> be clever you can try changing the xerces version in the master pom to >> >> either 2.9.1 or 2.9.1-mcf and see if that makes the problem go away. >> >> >> >> Karl >> >> >> >> >> >> On Mon, Feb 11, 2013 at 8:30 AM, Maciej Liżewski >> >> <[email protected]> wrote: >> >>> I am doing build on trunk, if that matters... >> >>> >> >>> >> >>> 2013/2/11 Maciej Liżewski <[email protected]> >> >>> >> >>>> do I have to do something more that "mvn clean install"? because >> without >> >>>> adding xerces dependancy to IT tests I still see errors like this: >> >>>> >> >>>> Results : >> >>>> >> >>>> Tests in error: >> >>>> >> >>>> >> sanityCheck(org.apache.manifoldcf.filesystem_tests.APISanityCombinedHSQLDBIT): >> >>>> *org/w3c/dom/ElementTraversal* >> >>>> >> sanityCheck(org.apache.manifoldcf.filesystem_tests.APISanityDerbyIT): >> >>>> API http >> >>>> error; expected 201, saw 500: >> >>>> >> sanityCheck(org.apache.manifoldcf.filesystem_tests.APISanityHSQLDBIT): >> >>>> API htt >> >>>> p error; expected 201, saw 500: >> >>>> >> >>>> >> >>>> 2013/2/11 Karl Wright <[email protected]> >> >>>> >> >>>>> I did not see this here when I ran it. I am at work now and won't be >> >>>>> able to run maven tests again until this evening. >> >>>>> >> >>>>> However, I will say this: >> >>>>> >> >>>>> - ant downloads 2.10.0 just like Maven should >> >>>>> - I don't see missing classes here under ant when I run IT's >> >>>>> >> >>>>> If you think it has something to do with the xerces dependency, >> >>>>> remember that the only thing I changed for Maven was the master >> >>>>> pom.xml to change the version from 2.9.1-mcf to 2.10.0. >> >>>>> >> >>>>> Karl >> >>>>> >> >>>>> On Mon, Feb 11, 2013 at 6:56 AM, Maciej Liżewski >> >>>>> <[email protected]> wrote: >> >>>>> > 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 >> >>>>> >> >> >> >>>>> >> >> >>>>> >> >>>> >> >>>> >>
