[JBoss JIRA] (JBIDE-19497) Use Jetty 9 in TP
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19497?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-19497:
---------------------------------------
FYI, here are the bundles that I use in LiveReload:
- org.eclipse.jetty.websocket
- org.eclipse.jetty.servlets
- org.eclipse.jetty.client
- org.eclipse.jetty.util
- org.eclipse.jetty.server
- org.eclipse.jetty.servlet
- org.eclipse.jetty.http
- org.eclipse.jetty.io
> Use Jetty 9 in TP
> -----------------
>
> Key: JBIDE-19497
> URL: https://issues.jboss.org/browse/JBIDE-19497
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
>
> *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles
> *Project page/sources:* https://www.eclipse.org/jetty/
> *Version:* 9.2.10.v20150310
> *License and owner:* Eclipse.org
> *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.9.v20150224
> *JBoss mirror:* TODO
> *Include Sources:* Yes
> *Affected projects:* Livereload, Cordovasim
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> TODO: suggested diff on the .target files/p2diff
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19497) Use Jetty 9 in TP
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-19497:
--------------------------------------
Summary: Use Jetty 9 in TP
Key: JBIDE-19497
URL: https://issues.jboss.org/browse/JBIDE-19497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform
Affects Versions: 4.3.0.Alpha1
Reporter: Mickael Istria
It seems like we are ready to move away from Jetty 8 and to use Jetty 9.
We should update TP to include all Jetty 9 bundles
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18861.
---------------------------------
Verified in JBDS 8.1.0.CR1 and 9.0.0.Alpha1.
In 9.0.0.Alpha1 there is still the problem with only showing [Synchronized] on the module though - this will be fixed in Alpha2 with this JIRA: JBIDE-19438
> module start action does not delete *.undeployed file
> -----------------------------------------------------
>
> Key: JBIDE-18861
> URL: https://issues.jboss.org/browse/JBIDE-18861
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Environment: Windows7 64bit, JDK 8u25
> Reporter: Darryl Miles
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> If you start Wildfly with all modules enabled and started.
> Now use STOP action on an EAR module.
> Now stop Wildfly.
> Now start Wildfly (debug or run).
> It will start up without the EAR module running, this is correct behavior at this point.
> Now use START on EAR module. It fails to start at all.
> This is because the file *.undeployed still exists. If you manually remove the file (using system file manager) the module will start up.
> If you perform a "full publish" on the module that appears to cause it to start up as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19496) docker run wizard
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19496:
-------------------------------------------
Summary: docker run wizard
Key: JBIDE-19496
URL: https://issues.jboss.org/browse/JBIDE-19496
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: docker
Reporter: Max Rydahl Andersen
should have a docker wizard to easily run images.
The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases.
For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3317) Basic Docker support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3317:
--------------------------------------
Component/s: docker
> Basic Docker support
> --------------------
>
> Key: JBDS-3317
> URL: https://issues.jboss.org/browse/JBDS-3317
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: docker, requirements
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.0.0.Beta1
>
>
> Basic docker support is to provide the following Docker features:
> * pull/add images from registry
> * list images
> * list containers
> * start containers from an image
> * stop/restart/kill containers
> * connect/disconnect from containers to show log/provide interactive console/terminal
> * build dockerfile (available via right click on DockerFile / project / file with DockerFile - this should support .dockerignore)
> * filter image/containers
> * provide details for image/containers
> * during launch be able to mount volumes, port forwards etc. in a simple UI (leave more advanced details to separate pages/different ui)
> * provide API for other tooling in eclipse to use it (like server launches etc.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months