[
https://issues.apache.org/jira/browse/GUACAMOLE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper resolved GUACAMOLE-56.
-------------------------------------
Resolution: Invalid
Closing, as:
# Adding application-specific build profiles and metadata seems bad. It would
be better for integrations with third-party software to live downstream.
# OpenShift seems to use Docker anyway, which is something we already provide.
Feel free to comment if you think this issue should be re-opened.
> OpenShift 3.x Integration
> -------------------------
>
> Key: GUACAMOLE-56
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-56
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client
> Reporter: kevensen
> Priority: Minor
>
> [OpenShift|https://en.wikipedia.org/wiki/OpenShift] is a
> Platform-as-a-Service that enables rapid build and deploy workflows for
> applications. The guacamole-client is perfect for this use case. In order to
> correctly integrate the client, I see two tasks.
> # Configure the pom.xml in the guacamole-client/guacamole/pom.xml to have an
> "OpenShift" profile for OpenShift specific builds.
> # Add .s2i (source-to-image) scripts for automated build and execution
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
