| Summary: | SOA Platform version strings - whether by an ant script at build time or by Java code at run time - should be identical. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Build Process | Assignee: | trev <tkirby> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 | CC: | ian.springer, jwulf |
| Target Milestone: | --- | ||
| Target Release: | 5.0.0 GA, 5.0.0 ER2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-465 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | SOA-465 | Environment: | |
| Last Closed: | 2010-01-28 13:04:12 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Len DiMaggio
2008-03-12 13:55:33 UTC
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 |