[JBoss JIRA] (JBIDE-20092) Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20092?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20092:
-------------------------------------
Sprint: (was: 22-Jun >> 05-Jul 2015-JBDS/JBT)
> Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20092
> URL: https://issues.jboss.org/browse/JBIDE-20092
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: new-connection-link.png, retrieve-token-link.png, singnup-link.png, styled-text-link.png
>
>
> using https://console.stg.openshift.com as server
> the retrieve link does nothing if clicked.
> Only if I use "enter" on the keyboard does it actually show a browser.
> Steps:
> # ASSERT: make sure that you're using MacOS
> # EXEC: launch new connection wizard,
> # EXEC: provide host, pick "OpenShift v3" and make sure you have "Oauth" authentication chosen
> # EXEC: hit "retrieve" link
> !retrieve-token-link.png!
> Result:
> Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-20168:
----------------------------------
Assignee: Nick Boldt
> create buildinfo.json files for old project builds which predate buildinfo.json generator
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20168
> URL: https://issues.jboss.org/browse/JBIDE-20168
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Max asked:
> {quote}
> i'm asking what shah's was used in the build for these components.
> No sure if you are trolling me by us keeping having these conversations everytime we need to tag :)
> Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right.
> and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20168:
-------------------------------
Fix Version/s: 4.3.0.Beta2
> create buildinfo.json files for old project builds which predate buildinfo.json generator
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20168
> URL: https://issues.jboss.org/browse/JBIDE-20168
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Max asked:
> {quote}
> i'm asking what shah's was used in the build for these components.
> No sure if you are trolling me by us keeping having these conversations everytime we need to tag :)
> Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right.
> and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-20168:
----------------------------------
Summary: create buildinfo.json files for old project builds which predate buildinfo.json generator
Key: JBIDE-20168
URL: https://issues.jboss.org/browse/JBIDE-20168
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.0.Beta1
Reporter: Nick Boldt
Max asked:
{quote}
i'm asking what shah's was used in the build for these components.
No sure if you are trolling me by us keeping having these conversations everytime we need to tag :)
Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right.
and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ?
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-17643) Archive jar is not deleted along with project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17643?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17643.
---------------------------------
Fix Version/s: (was: 4.2.x)
Resolution: Rejected
User should just refresh project before deleting it. This is a normal bug in Eclipse, and will function the same if you go to cmd line nad add a text file in the project but never refresh workspace.
Also, auto-refresh is improving in eclipse, which minimizes this bug.
> Archive jar is not deleted along with project
> ---------------------------------------------
>
> Key: JBIDE-17643
> URL: https://issues.jboss.org/browse/JBIDE-17643
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives
> Affects Versions: 4.2.0.Beta2
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
>
> This bug is easier to reproduce on windows than linux
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-15313) Investigate how to handle Wildfly port multiplexing
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15313?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-15313.
---------------------------------
Fix Version/s: 4.2.0.Final
(was: 4.2.x)
Resolution: Out of Date
JIRA is out of date. Ports are properly discovered via xpaths as always.
> Investigate how to handle Wildfly port multiplexing
> ----------------------------------------------------
>
> Key: JBIDE-15313
> URL: https://issues.jboss.org/browse/JBIDE-15313
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.1.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Final
>
>
> While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen.
> This jira will investigate what's necessary and what may need to change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months