[JBoss JIRA] (JBIDE-19985) Tooltips in Central get stuck easily
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19985?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19985:
----------------------------------
Attachment: central-tooltips.png
> Tooltips in Central get stuck easily
> ------------------------------------
>
> Key: JBIDE-19985
> URL: https://issues.jboss.org/browse/JBIDE-19985
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Priority: Minor
> Attachments: central-tooltips.png
>
>
> When I opened Central today, the tooltip over the first project in Central got shown (after I hovered my mouse over) and subsequently it would get stuck there and other tooltips would show up over it.
> Radim said this happened in your demo also, so I think you know this bug. (It seems there is no JIRA yet.)
> I tried to replicate this several times, always closing and opening Central, and I was able to replicate every time. You just need to hover your mouse over the items pretty quickly and sooner or later one of the tooltips will get stuck.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19985) Tooltips in Central get stuck easily
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19985?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-19985:
----------------------------------
Issue Type: Bug (was: Feature Request)
> Tooltips in Central get stuck easily
> ------------------------------------
>
> Key: JBIDE-19985
> URL: https://issues.jboss.org/browse/JBIDE-19985
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Priority: Minor
> Attachments: central-tooltips.png
>
>
> When I opened Central today, the tooltip over the first project in Central got shown (after I hovered my mouse over) and subsequently it would get stuck there and other tooltips would show up over it.
> Radim said this happened in your demo also, so I think you know this bug. (It seems there is no JIRA yet.)
> I tried to replicate this several times, always closing and opening Central, and I was able to replicate every time. You just need to hover your mouse over the items pretty quickly and sooner or later one of the tooltips will get stuck.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19985) Tooltips in Central get stuck easily
by Martin Malina (JIRA)
Martin Malina created JBIDE-19985:
-------------------------------------
Summary: Tooltips in Central get stuck easily
Key: JBIDE-19985
URL: https://issues.jboss.org/browse/JBIDE-19985
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Affects Versions: 4.3.0.Beta1
Reporter: Martin Malina
Priority: Minor
When I opened Central today, the tooltip over the first project in Central got shown (after I hovered my mouse over) and subsequently it would get stuck there and other tooltips would show up over it.
Radim said this happened in your demo also, so I think you know this bug. (It seems there is no JIRA yet.)
I tried to replicate this several times, always closing and opening Central, and I was able to replicate every time. You just need to hover your mouse over the items pretty quickly and sooner or later one of the tooltips will get stuck.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19951) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19951?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19951.
---------------------------------
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]
> ---------------------------------------------------------------
>
> Key: JBIDE-19951
> URL: https://issues.jboss.org/browse/JBIDE-19951
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Central Discovery]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19980) (New HTML5) Central search results have low contrast
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19980?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19980:
---------------------------------------
[~fbricon], hmm, I asked rhopp and psrna, they're both fine with the current layout. But I would at least like to see the text a bit darker. To me, the tags seem similar to the rest, so perhaps a bit darker text there too? Is there a way I can try it out just for myself? To see what looks good to me?
> (New HTML5) Central search results have low contrast
> ----------------------------------------------------
>
> Key: JBIDE-19980
> URL: https://issues.jboss.org/browse/JBIDE-19980
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Attachments: central-results.png
>
>
> When you search for something in the new html5 central, the results seem pretty low contrast to me, it almost seems like they are disabled or something.
> Got a +1 from Max, too ;)
> {quote}
> [max] agreed - I would go for a darker black there
> {quote}
> !central-results.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19984) Wrong version of playground components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19984?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19984:
-----------------------------------
Component/s: central
easymport
updatesite
> Wrong version of playground components
> --------------------------------------
>
> Key: JBIDE-19984
> URL: https://issues.jboss.org/browse/JBIDE-19984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, easymport, updatesite
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.Beta1
>
>
> JBDS 9.0.0.beta1 build contains alpha2 easymport plugins
> org.jboss.tools.playground.easymport.javascript_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.jee_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.Alpha2-v20150417-1604-B3.jar
> Also org.eclipse.e4.ui.importer.java_0.1.0.v20150414-1856.jar
> looks quite old but maybe nothing changed there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-19738:
------------------------------------
Yes, it disappeared.
Replication is pretty easy right now (because of JBIDE-19970). Just try to download for example EPA 6.2 and that's it ;-)
> Failed runtime download offers no error message
> -----------------------------------------------
>
> Key: JBIDE-19738
> URL: https://issues.jboss.org/browse/JBIDE-19738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19984) Wrong version of playground components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19984?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19984:
----------------------------------------
Since the easymport plugins are currently included in a feature which is part of jbosstools-central, we need to respin jbosstools-central (without any change) in order to pull the latest bits of easymport.
> Wrong version of playground components
> --------------------------------------
>
> Key: JBIDE-19984
> URL: https://issues.jboss.org/browse/JBIDE-19984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.Beta1
>
>
> JBDS 9.0.0.beta1 build contains alpha2 easymport plugins
> org.jboss.tools.playground.easymport.javascript_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.jee_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.Alpha2-v20150417-1604-B3.jar
> Also org.eclipse.e4.ui.importer.java_0.1.0.v20150414-1856.jar
> looks quite old but maybe nothing changed there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19984) Wrong version of playground components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19984?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19984:
-----------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-19984 (was: JBDS-3455)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Affects Version/s: (was: 9.0.0.Beta1)
Fix Version/s: 4.3.0.Beta1
(was: 9.0.0.Beta1)
Docs QE Status: (was: NEW)
> Wrong version of playground components
> --------------------------------------
>
> Key: JBIDE-19984
> URL: https://issues.jboss.org/browse/JBIDE-19984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.Beta1
>
>
> JBDS 9.0.0.beta1 build contains alpha2 easymport plugins
> org.jboss.tools.playground.easymport.javascript_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.jee_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.Alpha2-v20150417-1604-B3.jar
> Also org.eclipse.e4.ui.importer.java_0.1.0.v20150414-1856.jar
> looks quite old but maybe nothing changed there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months