Bug 724260 (BRMS-205) - SOA profile for Drools and BRMS build
Summary: SOA profile for Drools and BRMS build
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-205
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Build Process
Version: 5.0.2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.1.0 GA
Assignee: Jervis Liu
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-16 05:34 UTC by Jervis Liu
Modified: 2013-11-07 22:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-20 09:08:41 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-205 0 None None None Never

Description Jervis Liu 2009-07-16 05:34:50 UTC
securitylevel_name: Public

Currently we have a SOA profile in Drools pom. This needs to be changed when BRMS becomes a separate project. We will need a SOA profile for both Drools project and BRMS project. We also need to figure out how to publish libraries that are built by Drools SOA profile into a shared maven repository, so that these libraries can be picked up by BRMS build.

Comment 1 Jervis Liu 2009-11-20 09:08:41 UTC
Close this as https://jira.jboss.org/jira/browse/BRMS-204 has been closed. 

Comment 2 Dana Mison 2010-10-26 05:50:24 UTC
Writer: Added: Darrin


Comment 3 Dana Mison 2010-10-26 05:55:42 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 4 Dana Mison 2010-10-27 03:06:32 UTC
Release Notes Text: Added: test


Comment 5 Dana Mison 2010-10-27 03:13:38 UTC
Release Notes Text: Removed: test 


Comment 6 David Le Sage 2010-12-02 01:55:23 UTC
Labels: Removed: rn-dmison rn-open Added: rn-dlesage rn-not-needed


Comment 7 David Le Sage 2010-12-02 01:55:36 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required
Writer: Removed: Darrin Added: dlesage



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