-
Feature Request
-
Resolution: Won't Do
-
Major
-
4.2.0.Final
Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear.
[JBIDE-18723] Binary deployment from current JBDS state
André Dietisheim
added a comment - bdecoste Hey Bill, can you check with your customer if this feature request is still important please? We plan to focus all efforts on the v3 tooling for June and only implement in v2 what's strictly required.
André Dietisheim
added a comment - bdecoste Hey Bill, can you check with your customer if this feature request is still important please? We plan to focus all efforts on the v3 tooling for June and only implement in v2 what's strictly required. 
William Decoste (Inactive)
added a comment - Is this sufficient? https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/User_Guide/index.html#About_Snapshots
William Decoste (Inactive)
added a comment - Is this sufficient? https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/User_Guide/index.html#About_Snapshots William Decoste (Inactive)
added a comment - Sounds reasonable to me! I'll work it from the OpenShift side and respond asap.
William Decoste (Inactive)
added a comment - Sounds reasonable to me! I'll work it from the OpenShift side and respond asap. 
Max Andersen
added a comment - the documentation we got states there is no welldefined format we can rely on to do this reliably since the format is highly dependent on the cartridge running on the server.
If you have info on how we can make these reliable and not having to implement multiple variations and updates every time an update is out for the cartridge we are definitely interested.
Max Andersen
added a comment - the documentation we got states there is no welldefined format we can rely on to do this reliably since the format is highly dependent on the cartridge running on the server.
If you have info on how we can make these reliable and not having to implement multiple variations and updates every time an update is out for the cartridge we are definitely interested. 
Resolving all OpenShift 2 issues since support for OpenShift 2 faded out.