Bug 724085 (BRMS-29) - Investigate the possibility of using a brms maven profile to generate brms distribution for SOA-P release.
Summary: Investigate the possibility of using a brms maven profile to generate brms di...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-29
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Build Process
Version: 5.0.0 CR1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.0.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-01-09 15:27 UTC by Jervis Liu
Modified: 2013-11-07 22:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-10 00:54:55 UTC
Type: Feature Request


Attachments (Terms of Use)


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

Description Jervis Liu 2009-01-09 15:27:32 UTC
Date of First Response: 2009-01-12 04:40:48

Investigate the possibility of using a brms maven profile to generate brms distribution for SOA-P release.

<tkirby> jliu just grabbing the details
<tkirby> jliu ok the branch we are using is https://svn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.FP01_BRMS_5.0.EA
* JimMa (~jimma.redhat.com) has joined #jbosssoa
<jliu> i thought we are using branch: https://svn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.GA_IR1_JDK6
<tkirby> jliu, the difference between this branch and the main one at the moment is recorded at http://fisheye.jboss.org/changelog/JBossRules/?cs=24340
<tkirby> jliu what we would like to do is have a soa profile that reproduces the changes (mainly to pms and assemblies) with some extras
<tkirby> jliu the extras are things like rename the wars and bundle the zips up in the structure that Burr wants
<tkirby> jliu does that make sense?
<jliu> tkirby, ok, i guess whats happening here. so the commit 24340 is the only difference between soa_tags/4.3.0.GA_IR1_JDK6 and 4.3.0.FP01_BRMS_5.0.EA?  <tkirby> jliu for 4.3 we are but BRMS aka drools 5 is going to be the new supported standalone version of drools and will be in 4.3 FP01
* nmcl (~marklittl.redhat.com) has joined #jbosssoa
<jliu> what i do understand yet is where this 4.3.0.FP01_BRMS_5.0.EA comes from
<jliu> tkirby, what i do not understand
<tkirby> jliu soa_tags/4.3.0.GA_IR1_JDK is drools 4 and will be used in 4.2 and 4.3 CP streams
* elanghi (~elanghi.redhat.com) has left #jbosssoa
<tkirby> jliu BRMS will be used in the 4.3. FP streams and then in 4.4 etc.
* mic_neale has quit (Quit: mic_neale)
<tkirby> jliu does that make sense?
<jliu> tkirby, so this 4.3.0.FP01_BRMS_5.0.EA is tag on drools 5.0?
<tkirby> jliu that's correct
<jliu> tkirby, i see.
* darran (~darranl.redhat.com) has joined #jbosssoa
<tkirby> jliu I'll send you the information on what the other changes are in an email and if you could look and see if a soa profile can do this, that would be great
<jliu> ok. i ll take a deeper look. but my initial impression is that i cant be sure that if a maven profile can do this job
<tkirby> jliu ok I'm basically looking for a "this will work/this may work /you are completely insane" level of answer ie is a profile going to save work or do we just live with the overhead of having branches with the changes hardwired in and merge them
* tomjenkinson has quit (Quit: Leaving.)
* tomjenkinson (~tomjenkin.redhat.com) has joined #jbosssoa
<jliu> tkirby, is this for 4.3 fp01?
<tkirby> jliu, It's mainly for the BRMS which is the standalone version of drools5 but it will be included 4.3 FP01

Comment 1 Mark Little 2009-01-12 09:36:13 UTC
Security: Removed: Public 


Comment 2 Mark Little 2009-01-12 09:40:48 UTC
Moved here because it's really a BRMS issue.

Comment 3 Kris Verlaenen 2009-02-25 00:21:55 UTC
Rolling back change on drools-eclipse/drools-eclipse-build/pom.xml because it breaks normal eclipse build.
Also, it does not seem to make sense to have soa be the default profile and have the normal build define as a special profile with custom build.
Should also try to avoid duplication in the pom.xml.

Comment 4 Jervis Liu 2009-03-10 06:39:36 UTC
This should be done. Need a double-check. 


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