Bug 778639 (SOA-1116) - Set ESB server name from SOA build scripts
Summary: Set ESB server name from SOA build scripts
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1116
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.3 CP01
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-12 07:30 UTC by nwallace
Modified: 2009-05-01 16:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-12 12:31:25 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778564 0 urgent CLOSED Set ESB server name from SOA build scripts 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 778862 0 urgent CLOSED Set ESB server name from SOA build scripts 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1116 0 None None None Never

Internal Links: 778564 778862

Description nwallace 2009-01-12 07:30:27 UTC
Link type: Superset, Source: SOA-1116, Destination: SOA-1138
Date of First Response: 2009-01-20 06:17:52
project_key: SOA

See SOA-854.

The ESB "version" and "esb.server.name" properties need to be set in the SOA build.
Note that for the SOA 4.2 branch, the ESB CP number is not the same as the SOA CP
number.

Comment 1 nwallace 2009-01-12 07:32:35 UTC
Link: Added: This issue is related to SOA-1036


Comment 2 Mark Little 2009-01-20 11:13:51 UTC
Link: Added: This issue incorporates SOA-1138


Comment 3 Mark Little 2009-01-20 11:17:52 UTC
We will go with:

<Project Name>_<Project version>_<Platform name>_<Version>

So ...

JBossESB_4.4_CP01_SOA_4.3

and

JBossESB_4.4_CP02_SOA_4.3_CP01

Comment 4 Mark Little 2009-01-20 11:28:43 UTC
Drop the <Project Name> as it should be implied by the jar anyway, e.g.,:

4.4_CP01_SOA_4.3

Comment 6 trev 2009-01-27 15:31:09 UTC
variable not being passed through initial macro, need to create new esb.properties filewhich contains the variables  and point ${org.jboss.esb.properties} at it

Comment 7 trev 2009-02-02 09:52:52 UTC
build file modified to create updated properties file, porperties now being passed through

Comment 8 Jiri Pechanec 2009-03-12 12:31:25 UTC
Verified in CR4

Comment 9 nwallace 2009-05-01 16:15:47 UTC
Link: Added: This issue is related to SOA-1305



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