[
https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin...
]
Tom Arnold commented on TEIID-3121:
-----------------------------------
Ramesh,
Is there any problem with providing both a Docker image (when it's ready), and a
standalone ZIP? My script would only add at most 10 minutes to the release process, but
would lower the barrier to entry for people looking to develop against Teiid. A Docker
image wouldn't be useful to me, but the standalone ZIP would simplify my build
process.
Starting the JBoss would also be a quick way to test out the JBoss kit to make sure
everything deploys. Occasionally translators fail to deploy when dependencies are updated
because the module descriptors are out of date or have typos (e.g. Accumulo, Apache POI,
Mongo, -redhat-redhat).
The precedence is there for other JBoss projects doing this. For example, the RHQ download
packages JBoss and Cassandra.
If you'd like to go a different direction though, I can change my script accordingly.
Teiid Standalone Server
-----------------------
Key: TEIID-3121
URL:
https://issues.jboss.org/browse/TEIID-3121
Project: Teiid
Issue Type: Feature Request
Components: Build/Kits
Reporter: Tom Arnold
Fix For: Open To Community
Perform the server installation steps as part of the build and add the result to the
downloads page. It seems like this is something that everyone who isn't using the
embedded kit has to do anyways, and would hopefully eliminate confusion caused by people
trying to deploy the runtime in unsupported versions of JBoss.
* Teiid Runtime
* Teiid Web Console
* JBoss EAP 6.1 Alpha
* Resteasy JAX-RS Patch
End result would simplify the installation process to:
1. Unzip Teiid server.
2. Run `bin/add-user.sh` script.
3. Deploy custom translators, VDB, etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)