Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1187068

Summary: Importing mavenized jar with parent pom specified is not handled correctly
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: manstis
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: lpetrovi, rrajasek
Target Milestone: CR1Keywords: Regression
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:38:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
server log none

Description Zuzana Krejčová 2015-01-29 09:54:51 UTC
Created attachment 985496 [details]
screenshot

Description of problem:
See also bug 1007437.
If you try to upload a mavenized jar with a parent pom (that is not in the maven central), you get an Error modal (see screenshot) and quite a few error messages in the server log.
The jar is uploaded though and can be used as a dependency.
User will get the same Error modal when trying to download the jar via the provided 'Download' button/link.

The business-central is set to use custom maven settings.xml, where we define the location of the 'local' repository, point to productization repo and kie-wb-m2-repo.

The error logs say things like:
[ERROR] Non-resolvable import POM: Could not find artifact org.drools:drools-bom:pom:6.2.0.CR4-redhat-1 in central (http://repo.maven.apache.org/maven2)
Though the artifact is present in both the 'local' repo and the productization repo.

The root of that might be this:
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/business-central].[M2Servlet]] ... JBWEB000236: Servlet.service() for servlet M2Servlet threw exception: java.lang.IllegalStateException: ServletConfig has not been initialized

(When fixing this issue, could you also please look at the format of the Error modal message in this area? See bug 999876.)


Version-Release number of selected component (if applicable):
6.1 ER4

Comment 1 Zuzana Krejčová 2015-01-29 09:59:35 UTC
Created attachment 985497 [details]
server log

The part of server log relevant to the issue - result of uploading a mavenized jar with parent pom.

Comment 6 Zuzana Krejčová 2015-04-15 11:24:11 UTC
Works with a simple pom project and submodule. For other issues, see linked bugs.