[JBoss JIRA] (JBIDE-13882) Allow users to easily "binary deploy" in the wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13882?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-13882:
----------------------------------------
Assignee: Max Rydahl Andersen (was: Andre Dietisheim)
[~maxandersen] please have a look at the mock and gimme some feedback.
> Allow users to easily "binary deploy" in the wizard
> ---------------------------------------------------
>
> Key: JBIDE-13882
> URL: https://issues.jboss.org/browse/JBIDE-13882
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta2
>
> Attachments: 2013-05-29 13.33.bmml, 2013-05-29 13.33.png
>
>
> We should have an option in the wizard that allows easy "binary only" deployment
> {quote}
> 'binary deployment only' option which will go disable the the build marker...but what do we do about the existing project content - just leave it in place I would say.{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13882) Allow users to easily "binary deploy" in the wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13882?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13882:
------------------------------------------
The suggested added option is a checkbox in the "Server Adapter" group for binary (archived) deployment. If this checkbox is checked then the existing project will get war'ed, added to the deployments(jbossas)/webapps(tomcat) folder and a marker to skip the maven build will be created. If the OpenShift project is then pushed the maven build wont get executed and war in the deployments folder will get deployed.
> Allow users to easily "binary deploy" in the wizard
> ---------------------------------------------------
>
> Key: JBIDE-13882
> URL: https://issues.jboss.org/browse/JBIDE-13882
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
> Attachments: 2013-05-29 13.33.bmml, 2013-05-29 13.33.png
>
>
> We should have an option in the wizard that allows easy "binary only" deployment
> {quote}
> 'binary deployment only' option which will go disable the the build marker...but what do we do about the existing project content - just leave it in place I would say.{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13882) Allow users to easily "binary deploy" in the wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13882?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13882:
------------------------------------------
initial suggestion for additional option for binary deployment
> Allow users to easily "binary deploy" in the wizard
> ---------------------------------------------------
>
> Key: JBIDE-13882
> URL: https://issues.jboss.org/browse/JBIDE-13882
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
> Attachments: 2013-05-29 13.33.bmml, 2013-05-29 13.33.png
>
>
> We should have an option in the wizard that allows easy "binary only" deployment
> {quote}
> 'binary deployment only' option which will go disable the the build marker...but what do we do about the existing project content - just leave it in place I would say.{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13958) OpenShift connection wizard forgets password on IDE restart
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13958?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-13958.
----------------------------------
Verified in JBoss Developer Studio 7.0.0.Beta1a
> OpenShift connection wizard forgets password on IDE restart
> ------------------------------------------------------------
>
> Key: JBIDE-13958
> URL: https://issues.jboss.org/browse/JBIDE-13958
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta1
>
> Attachments: Connection_withoutPassword_afterIDErestart.png, Connection_withPassword.png
>
>
> I created a new OpenShift connection and selected 'save password' (then was prompted to put in secure storage password). New connection is listed in OpenShift Explorer tab.
> If I then click 'Connect to OpenShift' icon, the newly connected connection info is shown together with the password in the password field and the 'save password' check box is selected [attached image - Connection_withPassword.png].
> All good up to this point.
> I then closed and reopened the IDE. If I then click 'Connect to OpenShift' icon, the newly connected connection info is shown but the password field is BLANK and the 'save password' check box is NOT selected [attached image - Connection_withoutPassword_afterIDErestart.png].
> This looks like a bug to me - the password field should be completed and the check box selected.
> This issue only occurs when clicking 'connect to OpenShift' after an IDE restart. If double-click or expand connection in OpenShift Explorer tab after restart then the connection wizard remembers the password and skips straight to prompting for secure storage password as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14324) OpenShift Application Wizard: connection that you use to import/create should get set as most recent connection
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14324?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-14324.
----------------------------------
Verified in JBoss Developer Studio 7.0.0.Beta1a
> OpenShift Application Wizard: connection that you use to import/create should get set as most recent connection
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14324
> URL: https://issues.jboss.org/browse/JBIDE-14324
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta1
>
>
> How to reproduce:
> # ASSERT: make sure you have at least 2 connections in OpenShift Explorer
> # EXEC: launch import/create application wizard and switch the preselected connection in the connection dialog
> # EXEC: import/create some OpenShift application
> # ASSERT: import/create works successfully
> # ASSERT: make sure no connection is selected in OpenShift Explorer (ctrl + click deselects)
> # EXEC: hit *Connect to OpenShift* in OpenShift Explorer toolbar
> Result:
> The connection that was preselected before executing your import/create is still the connection that's being preselected
> Expected result:
> Once you successfully import/create an application the connection that you used should get preselected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months