[JBoss JIRA] (JBIDE-23127) blog about the improvements jboss tools team did to Neon
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-23127:
-----------------------------------
Description:
Neon is out and we did a lot of great stuff in the platform
around smart import, auto download of extensions, zoom, etc.
I thought it would be great to do a blog posting about this work
on tools.jboss.org for the Eclipse Neon release
Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made.
The target would be http://developers.redhat.com/blog
Topics:
* SWT
* Docker Tools
* JSDT & JS package
* Ctrl+/- on text
* Importer
* Disabling theming
was:
Neon is out and we did a lot of great stuff in the platform
around smart import, auto download of extensions, zoom, etc.
I thought it would be great to do a blog posting about this work
on tools.jboss.org for the Eclipse Neon release
Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made.
The target would be http://developers.redhat.com/blog
> blog about the improvements jboss tools team did to Neon
> --------------------------------------------------------
>
> Key: JBIDE-23127
> URL: https://issues.jboss.org/browse/JBIDE-23127
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> Neon is out and we did a lot of great stuff in the platform
> around smart import, auto download of extensions, zoom, etc.
> I thought it would be great to do a blog posting about this work
> on tools.jboss.org for the Eclipse Neon release
> Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made.
> The target would be http://developers.redhat.com/blog
> Topics:
> * SWT
> * Docker Tools
> * JSDT & JS package
> * Ctrl+/- on text
> * Importer
> * Disabling theming
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3981:
--------------------------------------
We depends on particular version of Xulrunner. If xulrunner is already installed via upstream rpm then we should not include it in our rpm but we need to test our VPE on that upstream xulrunner. It's not a blocker for us if the visual part of our VPE editor is not working on RHEL but we should make sure it at least doesn't crush.
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22051) Redesing route prompting in server adapter wizard, show in browser etc.
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22051?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22051:
------------------------------------
[~rob.stryker] can you tell me if this is still relevant ?
> Redesing route prompting in server adapter wizard, show in browser etc.
> -----------------------------------------------------------------------
>
> Key: JBIDE-22051
> URL: https://issues.jboss.org/browse/JBIDE-22051
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.2.AM1
>
>
> We currently allow the user NOT to choose a route for a server adapter. This might result in an adapter without proper host (since the host is derived from the route). In 4.3.1 we worked around it by always using the 1st available route as host, even though we possibly prompt the user and let it choose the route when he does Show In > Browser.
> According to [~rob.stryker] WTP adapters are designed to sit on a proper host. We should follow this pattern and use available WTP API to still allow the user to use different routes with an adapter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23029:
-------------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.4.x)
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.2.Final
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23150:
------------------------------------------
This is actually even critical for the integration tests because integration tests have to make sure to run with the JBoss OpenShift perspective - where Properties and OpenShift Explorer and in separate containers - to be able to look up resources (they look up resources via the Properties view)
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23150:
-------------------------------------
Attachment: properties-empty.png
openshift-explorer-and-properties-both-stacked.png
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23150:
-------------------------------------
Story Points: 8
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23150:
----------------------------------------
Summary: Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
Key: JBIDE-23150
URL: https://issues.jboss.org/browse/JBIDE-23150
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.Final
Reporter: Andre Dietisheim
If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
!openshift-explorer-and-properties-both-stacked.png!
and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
steps to reproduce:
# ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
# ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
# EXEC: make Properties view visible
# EXEC: make OpenShift explorer visible. Select an entry
# EXEC: switch back to Properties view
Result:
Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
!properties-empty.png!
Only moving Properties view to a different (visual) container helps.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk commented on JBDS-3981:
-----------------------------------
[~nickboldt] I am a bit out of the context, but we do rely on xulrunner in VPE. However, if it will not be included visual part of the editor will not work for for jsp / jsf but Studio will still be running fine
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3981:
----------------------------------
[~vkadlcik] The src rpm is build here [1] and deleted here [2].
I can change the build script [2] to retain that artifact if it's of use, rather than deleting it when it's no longer needed.
[1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/build....
[2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/build....
Not sure if we should be including xulrunner or assuming it's already installed via upstream rpm. Easy to blacklist that from the update site / rpm, if it should be removed. cc: [~ibuziuk] Do we still rely on xulrunner? Or do we just need gtk2/3/webkit/something else?
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months