[JBoss JIRA] (JBIDE-21861) Include Docker tooling 2.0.0 in JBT 4.4.x TP
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21861:
----------------------------------------
OK. Todd has approved the trello card.
But this jira is about JBoss Tools. Not devstudio.
[~akurtako] do you think it makes sense to include vagrant tools to devstudio installation as well?
Is it good/stable/useful enough?
> Include Docker tooling 2.0.0 in JBT 4.4.x TP
> --------------------------------------------
>
> Key: JBIDE-21861
> URL: https://issues.jboss.org/browse/JBIDE-21861
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
>
> Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20577) Allow setting exploded or zipped on per-module basis
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20577?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20577:
-------------------------------------
With JBIDE-22157 being fixed, what is needed now is a way to display the embedded modules in the deployment page.
Filtering is done "By deployable" by default, which hides embedded jar projects. At the very least the default filter should be "By Module Name".
As a side note, the UI os visually pretty confusing, in OSX at least, as the widgets appear active, but are effectively read-only, in the deployment page. You can't change the filter for instance. There's a tiny message about the server needing 0 modules, but it's really not obvious.
!http://content.screencast.com/users/fbricon/folders/Jing/media/e7e63f36-0962-4aea-a692-a45e217d5565/00000413.png|width=800!
> Allow setting exploded or zipped on per-module basis
> ----------------------------------------------------
>
> Key: JBIDE-20577
> URL: https://issues.jboss.org/browse/JBIDE-20577
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Fix For: 4.4.0.Alpha2
>
>
> While in the past, we automatically zipped up dependent utility projects, we recently switched to allowing exploded utility projects for appserver versions that suppoort it. Some users have determined this is slower for their usecase, and we should investigate giving users more control over this feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20577) Allow setting exploded or zipped on per-module basis
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20577?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-20577 at 5/9/16 4:48 PM:
-------------------------------------------------------------
With JBIDE-22157 being fixed, what is needed now is a way to display the embedded modules in the deployment page.
Filtering is done "By deployable" by default, which hides embedded jar projects. At the very least the default filter should be "By Module Name".
As a side note, the UI os visually pretty confusing, in OSX at least, as the widgets appear active, but are effectively read-only, in the deployment page. You can't change the filter for instance. There's a tiny message about the server needing 0 modules, but it's really not obvious.
!http://content.screencast.com/users/fbricon/folders/Jing/media/e7e63f36-0962-4aea-a692-a45e217d5565/00000413.png|width=750!
was (Author: fbricon):
With JBIDE-22157 being fixed, what is needed now is a way to display the embedded modules in the deployment page.
Filtering is done "By deployable" by default, which hides embedded jar projects. At the very least the default filter should be "By Module Name".
As a side note, the UI os visually pretty confusing, in OSX at least, as the widgets appear active, but are effectively read-only, in the deployment page. You can't change the filter for instance. There's a tiny message about the server needing 0 modules, but it's really not obvious.
!http://content.screencast.com/users/fbricon/folders/Jing/media/e7e63f36-0962-4aea-a692-a45e217d5565/00000413.png|width=800!
> Allow setting exploded or zipped on per-module basis
> ----------------------------------------------------
>
> Key: JBIDE-20577
> URL: https://issues.jboss.org/browse/JBIDE-20577
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Fix For: 4.4.0.Alpha2
>
>
> While in the past, we automatically zipped up dependent utility projects, we recently switched to allowing exploded utility projects for appserver versions that suppoort it. Some users have determined this is slower for their usecase, and we should investigate giving users more control over this feature.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22315) Application wizard: memory leak
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22315?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22315:
------------------------------------------
This should only be true for the wizard where it is used via the new server wizard framework of wst (when launching from New->Server in the Servers view or from File->New->...). The root cause is that the wst framework for wizard fragments loads extensions and caches them. That's actually also the core reason for them using a task model.
> Application wizard: memory leak
> -------------------------------
>
> Key: JBIDE-22315
> URL: https://issues.jboss.org/browse/JBIDE-22315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> Each instance of the wizard with pages, models, data binding contexts, and all referenced objects, including openshift model objects remains in memory. Disposed are only SWT widgets, but even they are not ready for the garbage collector since they remain referenced by data binding contexts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22315) Application wizard: memory leak
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22315?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22315:
--------------------------------
Story Points: 3
Sprint: devex #114 May 2016
> Application wizard: memory leak
> -------------------------------
>
> Key: JBIDE-22315
> URL: https://issues.jboss.org/browse/JBIDE-22315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> Each instance of the wizard with pages, models, data binding contexts, and all referenced objects, including openshift model objects remains in memory. Disposed are only SWT widgets, but even they are not ready for the garbage collector since they remain referenced by data binding contexts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22315) Application wizard: memory leak
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22315?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22315:
-------------------------------------
Labels: application_wizard openshift_v3 (was: )
> Application wizard: memory leak
> -------------------------------
>
> Key: JBIDE-22315
> URL: https://issues.jboss.org/browse/JBIDE-22315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> Each instance of the wizard with pages, models, data binding contexts, and all referenced objects, including openshift model objects remains in memory. Disposed are only SWT widgets, but even they are not ready for the garbage collector since they remain referenced by data binding contexts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22315) Application wizard: memory leak
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22315?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22315:
--------------------------------
Priority: Critical (was: Major)
> Application wizard: memory leak
> -------------------------------
>
> Key: JBIDE-22315
> URL: https://issues.jboss.org/browse/JBIDE-22315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
>
> Each instance of the wizard with pages, models, data binding contexts, and all referenced objects, including openshift model objects remains in memory. Disposed are only SWT widgets, but even they are not ready for the garbage collector since they remain referenced by data binding contexts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22315) Application wizard: memory leak
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-22315:
---------------------------------------------
Summary: Application wizard: memory leak
Key: JBIDE-22315
URL: https://issues.jboss.org/browse/JBIDE-22315
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.4.0.Alpha2
Each instance of the wizard with pages, models, data binding contexts, and all referenced objects, including openshift model objects remains in memory. Disposed are only SWT widgets, but even they are not ready for the garbage collector since they remain referenced by data binding contexts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months