installZanata script bound to a version of jboss-eap (6.3)
Activity
Show:
Former user 20 April 2018 at 00:24
We are closing all the old issues to have more clarity in our backlog for Zanata project. Feel free to re-open or leave a comment if you require our attention on your Jira.
Bugzilla Migration 31 July 2015 at 01:47
Carlos Munoz commented on 2015-01-20 01:10:26 -0500:
Since this is a new component, and since EAP 6.3 has already been released, I'm happy to restrict compatibility of this package to EAP 6.3+.
Not Applicable
Details
Details
Assignee
Carlos Munoz
Carlos MunozReporter
Former user
Former user(Deactivated)Labels
Components
Priority
MediumMore fields
Time tracking
More fields
Time trackingCreated 31 July 2015 at 01:47
Updated 20 April 2018 at 00:27
Resolved 21 March 2018 at 07:54
Description of problem:
The InstallZanata script generates a standalone.xml that will only work on jboss-eap6.3, the major issue being that it makes a working version of JBoss stop working.
Version-Release number of selected component (if applicable):
3.6-snapshot
How reproducible:
Easy always
Steps to Reproduce:
1. Unzip JBoss EAP 6.2 somewhere
2. Unzip a created zanata deployment/overlay package on top of it
3. Run the bin/zanata-installer/install.sh script
4. Answer the questions truthfully
Actual results:
Parse error on jboss start, Unexpected element {urn:jboss:domain:1.6}server
Expected results:
Zanata starts
Additional info:
JBoss EAP does not recognise domain:1.6, only domain:1.4