[
https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3121:
---------------------------------------
For me bundling the libraries/frameworks seems ok, but bundling the
whole platform seems not correct
As Tom points out, other projects do offer monolithic downloads. But I do understand the
concern about yet another download / maven artifact etc.
look like they are done in a Unix shell.
Yes, but it is not a requirement.
I'm getting the feeling that what I'm asking for is in
conflict with the productization done for JBoss DV
Somewhat. Productization is a whole other thing, but no they would not what the usage of
unmanaged dependencies. Maven ensures that artifacts we pull in are managed and that
artifacts we produce are published (when nexus is working).
If that's the case then I totally understand and will back off.
This boils down to 3 options:
1. Have a first class artifact produced by the maven build.
2. Have a second class artifact produced after the build.
3. Post install script(s) on the downloads page.
I'm in favor of 1 and 3 or just having a development aid script.
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)