Bug 1099553 - WAS: Building a project with mistaken dependency results in error screen with NoClassDefFoundError: com/ning/http/client/providers/netty/NettyAsyncHttpProvider
Summary: WAS: Building a project with mistaken dependency results in error screen with...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER3
: 6.0.2
Assignee: manstis
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-20 15:22 UTC by Radovan Synek
Modified: 2020-03-27 20:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:05:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
error screenshot (19.88 KB, image/png)
2014-05-20 15:22 UTC, Radovan Synek 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1290386 0 unspecified CLOSED WAS: Confusing build error message when project dependency doesn't exist 2021-02-22 00:41:40 UTC

Internal Links: 1290386

Description Radovan Synek 2014-05-20 15:22:05 UTC 
Created attachment 897639 [details]
error screenshot

Having a Business Central deployed on WebSphere AS, building a project containing mistaken dependency fails, showing an error screen with information that:
Unable to complete your request. The following exception occurred: java.lang.NoClassDefFoundError:com/ning/http/client/providers/netty/NettyAsyncHttpProvider.

Steps to Reproduce:
1. deploy business central to WebSphere AS
2. create a project
3. navigate to project dependencies
4. add any non existing dependency, e.g. "wrong:wrong:1.0"
5. save the project
6. build and deploy
Comment 2 Maciej Swiderski 2014-05-20 16:03:43 UTC 
confirmed on latest build of 6.0.x that the issue is not present any longer, current result is that build fails with error in Problems panel saying:
org.kie.scanner.embedder.MavenEmbedderException: Failed to read artifact descriptor for wrong:wrong:jar:1.0
Comment 3 Radovan Synek 2014-06-02 09:13:30 UTC 
Verified with BRMS-6.0.2.ER3
Note You need to log in before you can comment on or make changes to this bug.