[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19335:
-------------------------------------
> It shows dialog "Cannot create default browser No more handles" and then asks to exit workbench.
[~vpakan] The question is why FoundationUIPlugin.pluginLog().logError(etc) is showing a dialog and asking to exit the workspace... how is that even happening?
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19335
> URL: https://issues.jboss.org/browse/JBIDE-19335
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'.
> Steps to tests the issue:
> 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify)
> 2. Run JBT and try to download WildFly using Runtime Download dialog;
> 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one
> 4. Close eclipse
> 5. Install libwebkit
> 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20100:
---------------------------------------------
[~mickael_istria] any chance you can just screencast this since I can't get a build working that shows what is done
and reading from the above the main concerns don't seem to be covered and now the talk is about the About dialog so i'm a bit confused what this change actually *do*
> how to make users aware of fuse and other tooling only being available from earlyaccess?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20100
> URL: https://issues.jboss.org/browse/JBIDE-20100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
> Attachments: JBIDE-20100-2.png
>
>
> [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page.
> Some comments:
> "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list."
> "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."
> Suggestion:
> "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature."
> I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ?
> and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ?
> But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9)
> [~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-20528) Need to cover Bower Tools with RedDeer Tests
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20528?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-20528:
-------------------------------------
[~maxandersen], have just discussed this issue with [~psrna]. I'm afraid I missed the point of the last Californication a bit :/ (think that we can use RedDeer tests as a part of the build). Basically, the plan is 1) write more SWTBot tests for a build 2) write & contribute Bower RedDeer tests to jbosstools-integration-tests. I was thinking about RedDeer tests cause during the discussion it was said that in comparison with SWTBot those are more stable and easier to write
> Need to cover Bower Tools with RedDeer Tests
> --------------------------------------------
>
> Key: JBIDE-20528
> URL: https://issues.jboss.org/browse/JBIDE-20528
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: javascript-bower
> Affects Versions: 4.3.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.CR1
>
> Attachments: Bower Init.png, Bower Update.png
>
>
> The test scenarios:
> # "Bower Init" Wizard flow
> #* File -> New -> Other... -> New -> Bower -> Bower Init
> #* Test default value in the Wizard (Name / Version etc.)
> # "Bower Update" Launch Shortcut Availability
> #* on IProject (with bower.json)
> #* on IFolder (with bower.json)
> #* on bower.json
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19948:
---------------------------------------------
A) our code freeze is soon - I do not think we can fit this into JBDS 9 in any form.
B) due to A and JBDS 7 and JBDS 8 the old way still need to work
C) the system we have is even simpler but we still manage to have breakages - so this suggestion is by definition complicated ;)
> Reimplement Eclipse Download plugin to allow dynamic work flow
> --------------------------------------------------------------
>
> Key: JBIDE-19948
> URL: https://issues.jboss.org/browse/JBIDE-19948
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.3.0.Alpha2
> Reporter: David Hladky
> Assignee: Rob Stryker
> Fix For: 4.3.0.CR1
>
>
> We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones.
> Under this issue I will create the tasks we need to achieve this goal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-20528) Need to cover Bower Tools with RedDeer Tests
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20528?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20528:
---------------------------------------------
This will be stored where ? we can't use reddeer in our unit tests yet unfortunately. Only available for QE's semi-manual integration tests.
Just to be aware.
> Need to cover Bower Tools with RedDeer Tests
> --------------------------------------------
>
> Key: JBIDE-20528
> URL: https://issues.jboss.org/browse/JBIDE-20528
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: javascript-bower
> Affects Versions: 4.3.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.CR1
>
> Attachments: Bower Init.png, Bower Update.png
>
>
> The test scenarios:
> # "Bower Init" Wizard flow
> #* File -> New -> Other... -> New -> Bower -> Bower Init
> #* Test default value in the Wizard (Name / Version etc.)
> # "Bower Update" Launch Shortcut Availability
> #* on IProject (with bower.json)
> #* on IFolder (with bower.json)
> #* on bower.json
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months
[JBoss JIRA] (JBIDE-20343) Processing easymport cannot be stopped in reasonable time
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20343?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20343:
----------------------------------------
[~fbricon] I went into more details, and here is what I think is the issue with this job: it is a workspace job (that locks workspace changes) in which one the download of dependencies happen for some time. A better approach would be to resolve dependencies in one job, and then to update project in the WorkspaceJob (if even necessary).
Should I open a Bugzilla ticket for that?
> Processing easymport cannot be stopped in reasonable time
> ---------------------------------------------------------
>
> Key: JBIDE-20343
> URL: https://issues.jboss.org/browse/JBIDE-20343
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2, L64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
>
> During Easyimport operation it's unable to stop it. There is red stop box but it doesn't do anything in reasonable time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 2 months