Bug 1260929 - weld-servlet missing for product version.
Summary: weld-servlet missing for product version.
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Build and Assembly
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ER3
: 6.2.0
Assignee: Vladimir Dosoudil
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On: 1254964
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-08 09:00 UTC by Ryan Zhang
Modified: 2020-03-27 19:03 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description Ryan Zhang 2015-09-08 09:00:41 UTC
Description of problem:
I spot that weld-servlet is missing from EAP build in https://brewweb.devel.redhat.com/buildinfo?buildID=441732

The weld-servlet are using by layered products (eg: BRMS BPMSuite).
I think full build is expected to includes all modules in weld as decided before.
Could anyone from EAP rebuild the weld project in order to produce the weld-servelt artifact?

This is important to BRMS 6.2.x release because we can't use the redhat produced jboss weld components due to the weld-servlet missing issue.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ryan Zhang 2015-09-08 09:09:10 UTC
This is a build issue. I will be responsible to verify it after EAP team fix it.

Comment 2 Ryan Zhang 2015-09-18 07:36:06 UTC
As I can see from BZ 1254964, this issue has been resolved. 
The partial build has been fixed by EAP team.  And the expected artifact  can be downloaded from bxms MEAD repository: http://download.eng.bos.redhat.com/brewroot/repos/jb-bxms-6.2-build/latest/maven/org/jboss/weld/servlet/weld-servlet-core/1.1.31.Final-redhat-1/ (for example)
Since this is simply a build issue, I put it into VERIFY.


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