[jbpm-issues] [JBoss JIRA] Created: (JBPM-2276) net.sf.xframe.xsddoc.ProcessorException in jBPM4 with maven 2.1.0

net.sf.xframe.xsddoc.ProcessorException in jBPM4 with maven 2.1.0 ----------------------------------------------------------------- Key: JBPM-2276 URL: https://jira.jboss.org/jira/browse/JBPM-2276 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.0.Beta2 Reporter: Jeff Yu By installing the maven 2.1.0, and then run: mvn clean install -Pschemadoc, you will have following exceptions: (With maven 2.0.9, I don't see this error) Caused by: java.io.FileNotFoundException: /local/works/jbpm4-idm/modules/api/local/works/jbpm4-idm/modules/api/src/main/resources/jpdl-4.0.xsd (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146) at net.sf.xframe.xsddoc.Processor.getDocument(Processor.java:1253) at net.sf.xframe.xsddoc.Processor.processImport(Processor.java:990) at net.sf.xframe.xsddoc.Processor.processComponent(Processor.java:779) at net.sf.xframe.xsddoc.Processor.processComponents(Processor.java:747) at net.sf.xframe.xsddoc.Processor.process(Processor.java:719) at net.sf.xframe.xsddoc.Processor.process(Processor.java:691) at net.sf.xframe.xsddoc.Processor.execute(Processor.java:525) ... 25 more Caused by: java.io.FileNotFoundException: /local/works/jbpm4-idm/modules/api/local/works/jbpm4-idm/modules/api/src/main/resources/jpdl-4.0.xsd (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146) at net.sf.xframe.xsddoc.Processor.getDocument(Processor.java:1253) at net.sf.xframe.xsddoc.Processor.processImport(Processor.java:990) at net.sf.xframe.xsddoc.Processor.processComponent(Processor.java:779) at net.sf.xframe.xsddoc.Processor.processComponents(Processor.java:747) at net.sf.xframe.xsddoc.Processor.process(Processor.java:719) at net.sf.xframe.xsddoc.Processor.process(Processor.java:691) at net.sf.xframe.xsddoc.Processor.execute(Processor.java:525) ... 25 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira