Bug 1263738 - Misleading error message on startup: Could not find artifact org.guvnor:guvnor-asset-mgmt-project:jar
Summary: Misleading error message on startup: Could not find artifact org.guvnor:guvno...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ER5
: 6.2.0
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
: 1254452 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-16 14:45 UTC by manstis
Modified: 2020-03-27 19:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:41:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1254452 0 high CLOSED guvnor-mgmt-projects first time startup error in BPMSuite 2021-02-22 00:41:40 UTC

Internal Links: 1254452

Description manstis 2015-09-16 14:45:02 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 manstis 2015-09-16 14:48:13 UTC
Sorry.. I thought I was going to be able to edit the "description" :(

When starting up kie-(drools)-wb the below error can be observed.

This is not an error, as AssetMgmtDeploymentUnitProvider tries to resolve the org.guvnor:guvnor-asset-mgmt-project:jar with Maven, if it cannot be found it deploys the JAR to the workbench's Maven Repository. 

The message is logged (as an ERROR) in GuvnorM2Repository.getArtifactFileFromRepository(). It should probably log as a warning and not an error.

15:44:07,330 ERROR [org.guvnor.m2repo.backend.server.GuvnorM2Repository] (MSC service thread 1-9) Could not find artifact org.guvnor:guvnor-asset-mgmt-project:jar:6.3.0.Final in guvnor-m2-repo (file:/home/manstis/Desktop/smoketest/eap/jboss-eap-6.4/bin/repositories/kie/): org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.guvnor:guvnor-asset-mgmt-project:jar:6.3.0.Final in guvnor-m2-repo (file:/home/manstis/Desktop/smoketest/eap/jboss-eap-6.4/bin/repositories/kie/)
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) [aether-impl-1.0.0.v20140518.jar:]
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) [aether-impl-1.0.0.v20140518.jar:]
	at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) [aether-impl-1.0.0.v20140518.jar:]
	at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294) [aether-impl-1.0.0.v20140518.jar:]
	at org.guvnor.m2repo.backend.server.GuvnorM2Repository.getArtifactFileFromRepository(GuvnorM2Repository.java:976) [guvnor-m2repo-editor-backend-6.3.0.Final.jar:6.3.0.Final]
	at org.guvnor.m2repo.backend.server.GuvnorM2Repository$Proxy$_$$_WeldClientProxy.getArtifactFileFromRepository(GuvnorM2Repository$Proxy$_$$_WeldClientProxy.java) [guvnor-m2repo-editor-backend-6.3.0.Final.jar:6.3.0.Final]
	at org.jbpm.console.ng.asset.backend.server.AssetMgmtDeploymentUnitProvider.deployToLocalMavenIfNeeded(AssetMgmtDeploymentUnitProvider.java:119) [jbpm-console-ng-asset-mgmt-backend-6.3.0.Final.jar:6.3.0.Final]
	at org.jbpm.console.ng.asset.backend.server.AssetMgmtDeploymentUnitProvider.getDeploymentUnits(AssetMgmtDeploymentUnitProvider.java:68) [jbpm-console-ng-asset-mgmt-backend-6.3.0.Final.jar:6.3.0.Final]
	at org.jbpm.console.ng.asset.backend.server.AssetMgmtDeploymentUnitProvider$Proxy$_$$_WeldClientProxy.getDeploymentUnits(AssetMgmtDeploymentUnitProvider$Proxy$_$$_WeldClientProxy.java) [jbpm-console-ng-asset-mgmt-backend-6.3.0.Final.jar:6.3.0.Final]

Comment 5 Jiri Locker 2015-10-22 16:46:59 UTC
This issue is in an invalid state. It can't be ON_QA when the fix hasn't been backported to 6.3.x branch.

Also, it is unclear if it is targeted for 6.2.0 when the release flag hasn't been granted. (I think it should be acked as the fix is trivial.)

Comment 8 Jiri Locker 2015-11-10 13:07:07 UTC
The exception is now logged on WARN level.

(Note: I am unable to get the message locally, but in Jenkins jobs which run with clean workspace.)

Comment 9 Jiri Locker 2015-11-10 13:34:36 UTC
*** Bug 1254452 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.