++ This bug is a clone of bug 777936 ++ Date of First Response: 2008-04-02 04:21:49 project_key: SOA SOA Platform version strings - whether by an ant script at build time or by Java code at run time - should be identical.
fixed the bit that we can influence and changed string as per jsants email. The rest is a AS issue.
moving out to cp02, will link to AS issue
It's close - but not the same. Is this a 'major' priority problem? JMX Console: 4.2.0.GA_CP02_SOA (build: SVNTag=SOA_4.2.0.GA_CP02 date=200806090827) run.jar: Implementation-Version: SOA_4.2.0.GA_CP02 (build: SVNTag=SOA_4.2.0.GA_CP02 date=200806090827)
If this is blocked by an AS issue then let's create an issue in AS and cross-link.
Moving out of 4.3GA cycle. Trev to create the JBAPP JIRA and cross-link.
Link: Added: This issue is related to SOA-911
From Jar Implementation-Version: 4.3.0.GA-CP01_SOA_STANDALONE (build: SVNTag=4. 3.0.GA-CP01_SOA_STANDALONE date=200901281318) From JMX-console 4.3.0.GA-CP01_SOA_STANDALONE (build: SVNTag=4.3.0.GA-CP01_SOA_STANDALONE date=200901281318)
superseded by https://jira.jboss.org/jira/browse/SOA-911
Closing - the issue is covered in SOA-911