You might consider giving current add-ons trunk version a spin. I added the workaround from Marshall there (at least temporarily) and most of the errors are gone (there's still some stuff about missing JSON classes in the Alchemy module that's not nailed down yet).
For the XML stuff, there is a plugin to m2e which generates the Java classes to access the XML files as part of the build process. On Kepler and with the svn trunk version, Eclipse should be able to find this plugin as a quick-fix measure. Otherwise, you can try to install it manually from - Eclipse -> Preferences -> Maven -> Discovery -> Open Catalog - Install "m2e connector for xmlbeans" An additional Eclipse plugin that might be required is the "Tycho Project Configurators" which interface the OSGi-aspects of the POMs with m2e. -- Richard On 01.11.2013, at 03:26, digital paula <[email protected]> wrote: > First of all, thanks Marshall and Richard for the prompt reply. I started a > new import for maven project from SCM for the regex annotator in eclipse. > When the maven screen appeared stating a problem with > uima-build-helper-maven-pluginmaven-dependency-plugin, I just selected to > resolve later then in the project I pasted Marshall's update to the POM file. > The two errors that showed in the Problem area disappeared leaving one > error which just required a maven update project to resolve. > > However when I tried to execute CVD again, I got the same error: > Caused by: java.lang.ClassNotFoundException: > schemaorg_apache_xmlbeans.system.s4DE0C4BDB0BE7CAF27A97C2453FE4641.TypeSystemHolder > > What I didn't check last time was the log file in CVD, which is pretty much > most of the same error however it states this one below which only shows if > the log is set to show everything. > > org.apache.uima.tools.cvd.MainFrame.handleException(528): SEVERE: Could not > initialize class org.apache.incubator.uima.regex.ConceptSetDocument > java.lang.NoClassDefFoundError: Could not initialize class > org.apache.incubator.uima.regex.ConceptSetDocument > Based on some of the research I've done on xmlbeans it appears that two jars > are required: xml-beans and jsr173_1.0_api. The maven dependencies folder > only have the first one. In addition, the generated CLASS and XSB files > seem to also need to be bundled into a jar (done using SCOMP tool that comes > with xmlbeans). Note that I had to include xml-beans2.4.0 on the runtime > classpath or else I got an xmlbeans class error and never would have got to > the error I encountered if I hadn't included the xmlbeans jar on runtime > classpath. I just added it as an external jar and pointed to the one in the > regex annotator maven dependency folder. If I could get the jsr173_1.0_api > and class/XSB jar, I would put them in the maven dependency folder as well > and add toruntime classpath......could I give that a try? > > I'm not sure if this is the solution but I would love to give it a try, if > you guys could provide me the Class/XSB jar and jsr173_1.0 jar(I think i > would need it for xml 2.4.0) and I'll add to the maven dependencies folder > and runtime classpath. I'll be willing to test out and if it works you > guys can add it to the maven dependencies and add revision to the regex > install web page so other users don't run into the same problem that I did > when trying to install/use the regex annotator. > Regards,Paula
