-
Bug
-
Resolution: Done
-
Critical
-
6.1.0
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
- is related to
-
RHBPMS-193 Unable to access Workbench Maven repository with Basic Authentication enabled
- Verified
-
RHBRMS-326 Ugly, unformatted error pop-ups with stacktraces
- Resolved
-
RHBRMS-845 Importing mavenized jar with parent pom specified is not handled correctly
- Closed
-
RHBRMS-219 Importing mavenized jar with parent is not handled correctly - version from parent's dep. management
- Closed
-
RHBRMS-1079 Importing mavenized jar is not handled correctly - pom import from custom repository
- Closed
- relates to
-
RHBPMS-193 Unable to access Workbench Maven repository with Basic Authentication enabled
- Verified
-
RHBRMS-326 Ugly, unformatted error pop-ups with stacktraces
- Resolved
-
RHBRMS-845 Importing mavenized jar with parent pom specified is not handled correctly
- Closed
-
RHBRMS-219 Importing mavenized jar with parent is not handled correctly - version from parent's dep. management
- Closed
-
RHBRMS-1079 Importing mavenized jar is not handled correctly - pom import from custom repository
- Closed