[
https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin...
]
Tom Arnold commented on TEIID-3121:
-----------------------------------
Maven might be cleaner, but I wasn't sure where to start.
The steps in the release procedure
(
https://developer.jboss.org/wiki/TeiidReleaseProcedure) look like they are done in a Unix
shell. The download URLs would need to be maintained in the script, but how often do they
change? I think the only one that has changed recently is the Teiid Web Console URL.
I was thinking that "install.sh" would be run sometime after the Maven build.
I'm not too familiar with the maven release plugin, so maybe there would be an extra
step of checking out the tag so that the correct version is used (Final instead of Beta).
I'm getting the feeling that what I'm asking for is in conflict with the
productization done for JBoss DV. If that's the case then I totally understand and
will back off.
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)