[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20764:
------------------------------------------
https://github.com/openshift/origin/issues/6109 was fixed and works in
{code}
oc v1.1.0.1
{code}
which is not available as official release yet, you have to manually build it for now
> Create Server Adapter for OpenShift 3 applications
> --------------------------------------------------
>
> Key: JBIDE-20764
> URL: https://issues.jboss.org/browse/JBIDE-20764
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: new_and_noteworthy, openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
> Attachments: server adapter wizard.bmml, server adapter wizard.png
>
>
> get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed.
> Server status= matching deployment pod status
> Possible menus:
> - Start/Stop
> - Show Web Console
> - Port Forwarding
> - Stream logs
> [~maxandersen] can you think of anything else?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21295) Server Adpater: implement Show in > Web Browser works
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21295?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21295:
----------------------------------------
Assignee: Andre Dietisheim
> Server Adpater: implement Show in > Web Browser works
> -----------------------------------------------------
>
> Key: JBIDE-21295
> URL: https://issues.jboss.org/browse/JBIDE-21295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta1
>
>
> Current code in OpenShiftServerExtendedProperties#getWelcomePage only takes the 1st route which will open the wrong page if there are several ones in the same page. It is therefore commented. We need to find a way to either give the user a chance to choose the route among the available ones or find a way to programmatically choose the right one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21295) Server Adpater: implement Show in > Web Browser works
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21295?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21295:
-------------------------------------
Fix Version/s: 4.3.1.Beta1
(was: 4.3.1.Beta2)
> Server Adpater: implement Show in > Web Browser works
> -----------------------------------------------------
>
> Key: JBIDE-21295
> URL: https://issues.jboss.org/browse/JBIDE-21295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta1
>
>
> Current code in OpenShiftServerExtendedProperties#getWelcomePage only takes the 1st route which will open the wrong page if there are several ones in the same page. It is therefore commented. We need to find a way to either give the user a chance to choose the route among the available ones or find a way to programmatically choose the right one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21261) Fix ECMA5 content assist JUnit test
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21261?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21261:
----------------------------------------
[~nickboldt] we have fixed this jst test in 4.3.x and master. So, 4.3.1.Beta1x branch is still failing but this is a pure test problem so I didn't merge it to the frozen beta1 branch to avoid jst rebuilding. Let me know if we will re-build jst for Beta1 anyway so we can push this fix there to have a nice blue build. Otherwise I would keep it fixed for Beta2 and Neon only.
> Fix ECMA5 content assist JUnit test
> -----------------------------------
>
> Key: JBIDE-21261
> URL: https://issues.jboss.org/browse/JBIDE-21261
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript
> Affects Versions: 4.3.1.Beta1
> Reporter: Denis Golovin
> Assignee: Victor Rubezhny
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> During CI build on jenkins JUnit I test fails. Filing test checks for ECMA5 related proposals in content assist for .js file in JavaScript project. With manually created project and .js file everything works as expected.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ]
Xavier Coulon resolved JBDS-3552.
---------------------------------
Resolution: Done
Docker tooling allows for container volumes configuration, which means that with Docker running natively on Linux or in Boot2Docker or Docker Machine, mounted volumes are shared with the host system and it is possible to deploy the application from DevStudio and let the container pick the exploded war file and then all subsequent/incremental changes, just as if the app server was running on the host.
> Developer - be able to incrementally deploy changes to docker containers
> -------------------------------------------------------------------------
>
> Key: JBDS-3552
> URL: https://issues.jboss.org/browse/JBDS-3552
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly.
> Acceptance Criteria:
> * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment.
> * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh.
> * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source)
> * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ]
Xavier Coulon updated JBDS-3551:
--------------------------------
Fix Version/s: 9.1.0.Beta2
(was: 9.1.0.Beta1)
> JavaEE Developer - be able to start/stop applications on docker with debug on/off
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3551
> URL: https://issues.jboss.org/browse/JBDS-3551
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> User Story:
> As a JavaEE Developer I should be able to start/stop applications with debug turned on or off
> Acceptance Criteria:
> * Developer can start/stop an application from a central place, no CLI operations needed.
> * Developer can start with or without debug enabled
> * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart
> * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ]
Xavier Coulon commented on JBDS-3551:
-------------------------------------
Server adapter should provide support for remote debugging a Java application deployed on WildFly in a Docker container.
> JavaEE Developer - be able to start/stop applications on docker with debug on/off
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3551
> URL: https://issues.jboss.org/browse/JBDS-3551
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a JavaEE Developer I should be able to start/stop applications with debug turned on or off
> Acceptance Criteria:
> * Developer can start/stop an application from a central place, no CLI operations needed.
> * Developer can start with or without debug enabled
> * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart
> * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months