I fixed the MinimalPomParser by resetting the InputStream as follows:
static PomModel parse(String path, InputStream is) {
MinimalPomParser handler = new MinimalPomParser();
try {
*if(is.markSupported()){
is.reset();
}*
Hi,
the MinimalPomParser is an xml parser we developed internally to cover the
most common and straightforward cases, but very likely it is unable to parse
the multi-module pom you're using.
However adding the kie-ci module to your dependencies (
The problem is that the OP is uploading the JAR to kie-wb.
This is where the error is thrown:
https://github.com/droolsjbpm/guvnor/blob/master/guvnor-m2repo-editor/guvnor-m2repo-editor-backend/src/main/java/org/guvnor/m2repo/backend/server/FileServlet.java#L154
Would this use the Maven Native
Yes, I'm trying to upload the JAR to the kie-wb maven repository via the
kie-wb Artifact Repository page. Since the kie-ci module is already on the
webapps classpath, I assume there are no other work-arounds to try.
I debugged the MinimalPomParser method below and found the InputStream
passed in
Can you provide your JAR?
On 18 December 2013 22:23, jguenth jgue...@co.pierce.wa.us wrote:
Yes, I'm trying to upload the JAR to the kie-wb maven repository via the
kie-wb Artifact Repository page. Since the kie-ci module is already on the
webapps classpath, I assume there are no other
Unfortunately, I cannot. I will try to create a bogus multi-module project to
replicate the problem and send it instead.
From: rules-users-boun...@lists.jboss.org
[mailto:rules-users-boun...@lists.jboss.org] On Behalf Of Michael Anstis
Sent: Wednesday, December 18, 2013 2:28 PM
To: Rules Users
Here is a simple multi-module maven project that causes the error.
test-import.tar.gz
http://drools.46999.n3.nabble.com/file/n4027360/test-import.tar.gz
Do a mvn clean install in the test-import directory and then try to upload
the test-import-domain-0.0.1-SNAPSHOT.jar from your local maven
I'm trying to upload a maven jar artifact using the Artifact Repository and
getting the parse error below.
Here is my maven project structure...
parent_pom (packaging: pom)
|_module1_parent_pom (packaging: pom)
| |_module1a (packaging: jar)
| |_module1b (packaging: jar)
| |_module1c (packaging:
it’s hard to see what the problem is. The parser is failing, but it’s now
showing where a bouts - i.e. inside of the wrapped exception.
Here is the MinimalPomParser:
