[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 reassigned JBIDE-20092:
----------------------------------------
Assignee: Andre Dietisheim (was: Max Rydahl Andersen)
> 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-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 edited comment on JBIDE-20092 at 6/30/15 10:37 AM:
--------------------------------------------------------------------
I worked around this issue using a styled text, which works fine for me: it reacts to clicking and there's no visual difference I could spot.
!styled-text-link.png!
was (Author: adietish):
I worked around this issue using a styled text, which works fine for me: it reacts to clicking and there's no visual difference I could spot.
!macos-styled-text-link.png!
> 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: Max Rydahl Andersen
> 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-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:
-------------------------------------
Attachment: styled-text-link.png
> 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: Max Rydahl Andersen
> 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-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 commented on JBIDE-20092:
------------------------------------------
I worked around this issue using a styled text, which works fine for me: it reacts to clicking and there's no visual difference I could spot.
!macos-styled-text-link.png!
> 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: Max Rydahl Andersen
> 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
>
>
> 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] (JBDS-3462) remove /development/ and /staging/ URLs from JBDS artifacts
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3462?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3462.
----------------------------
Page removed from generation in jbdevstudio-product/results/build.xml via this PR:
https://github.com/jbdevstudio/jbdevstudio-product/pull/318
Pushed to master.
Building:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=3451
> remove /development/ and /staging/ URLs from JBDS artifacts
> -----------------------------------------------------------
>
> Key: JBDS-3462
> URL: https://issues.jboss.org/browse/JBDS-3462
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Beta2
>
>
> There's a TODO in the JBDS 9 release guide which says:
> {quote}
> when releasing GA make sure to :%s/development/stable/g and :%s/9.0-staging/9.0/g{quote}
> Here are a couple files which still need to be tweaked so they don't have to change between milestone releases and GA:
> {code}
> ./results/build.xml **
> 224- <!-- <antcall target="create.results.html">
> 225- <param name="update.site.qualifier" value="${update.site.qualifier}"/>
> 226: <param name="PREFIX" value="/earlyaccess/builds/development/${update.site.version}.${BUILD_ALIAS}"/>
> {code}
> {code}
> ./results/index-internal-template.html **
> 102- </div>
> 103- <div align="right">
> 104: <a class="blue" style="align: right;" href="http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site...">JBT Git Revisions</a>
> 105- </div>
> {code}
> {code}
> ./sources/build.xml **
> 176- </target>
> 177-
> 178: <!-- NOTE: after staging a build, latest/all/ folder no longer exists so need to override to find upstream or build fails.
> 179: mvn install -Djbosstools-site=http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Final-build-core/2015-03-01_13-40-40-B357/all/
> 180- -->
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20141:
------------------------------------
{quote}A) you asked for having ability to browse directory content. I agreed that would be nice, but having a place with nice html page without internal details exposed is nice too. Hence why a composite at /updates/*/mars would be useful. {quote}
Are you suggesting that we should have symlinks from:
* /updates/snapshots/mars -> http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ [pretty HTML page]
* /updates/staging/mars -> http://download.jboss.org/jbosstools/mars/staging/updates/core/{some version}/ [pretty HTML page]
* /updates/development/mars -> http://download.jboss.org/jbosstools/mars/development/updates/core/ [pretty HTML page]
> Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20141
> URL: https://issues.jboss.org/browse/JBIDE-20141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, & stable build.
> But sometimes, finding these artifacts can be a daunting task.
> Below are some URLs where things can be found.
> *CI builds / SNAPSHOTS / nightlies*
> * http://download.jboss.org/jbosstools/updates/nightly/master/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/updates/nightly/mars -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/nightly/updates/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central)
> * http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects' update sites)
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3....
> ** ..
> * http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI builds)
> *Staging Sites*
> * http://download.jboss.org/jbosstools/mars/staging/builds/
> * http://download.jboss.org/jbosstools/mars/staging/updates/
> *Development Milestones*
> * http://download.jboss.org/jbosstools/updates/development/mars/ -> ../../mars/development/updates/ (*OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/development/updates/ (composites & content that isn't *static*)
> * http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update sites, moved here for Akamai performance)
> ----
> For JBDS, we follow the same pattern as above but use https://devstudio.redhat.com/9.0/ instead of http://download.jboss.org/jbosstools/mars/ ... but we also have a /builds/installer/ folder because the public JBDS site now includes the standalone installer:
> * https://devstudio.redhat.com/9.0/development/builds/installer/
> Also, for JBDS we don't have to differentiate between /static/ and non-static content, since Akamai set up the entire server to be mirrored to their servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20141 at 6/30/15 10:24 AM:
--------------------------------------------------------------
{quote}A) you asked for having ability to browse directory content. I agreed that would be nice, but having a place with nice html page without internal details exposed is nice too. Hence why a composite at /updates/*/mars would be useful. {quote}
Are you suggesting that we should have symlinks from:
* /updates/snapshots/mars -> http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ [pretty HTML page]
* /updates/staging/mars -> http://download.jboss.org/jbosstools/mars/staging/updates/core/\{some version}/ [pretty HTML page]
* /updates/development/mars -> http://download.jboss.org/jbosstools/mars/development/updates/core/ [pretty HTML page]
was (Author: nickboldt):
{quote}A) you asked for having ability to browse directory content. I agreed that would be nice, but having a place with nice html page without internal details exposed is nice too. Hence why a composite at /updates/*/mars would be useful. {quote}
Are you suggesting that we should have symlinks from:
* /updates/snapshots/mars -> http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ [pretty HTML page]
* /updates/staging/mars -> http://download.jboss.org/jbosstools/mars/staging/updates/core/{some version}/ [pretty HTML page]
* /updates/development/mars -> http://download.jboss.org/jbosstools/mars/development/updates/core/ [pretty HTML page]
> Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20141
> URL: https://issues.jboss.org/browse/JBIDE-20141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, & stable build.
> But sometimes, finding these artifacts can be a daunting task.
> Below are some URLs where things can be found.
> *CI builds / SNAPSHOTS / nightlies*
> * http://download.jboss.org/jbosstools/updates/nightly/master/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/updates/nightly/mars -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/nightly/updates/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central)
> * http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects' update sites)
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3....
> ** ..
> * http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI builds)
> *Staging Sites*
> * http://download.jboss.org/jbosstools/mars/staging/builds/
> * http://download.jboss.org/jbosstools/mars/staging/updates/
> *Development Milestones*
> * http://download.jboss.org/jbosstools/updates/development/mars/ -> ../../mars/development/updates/ (*OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/development/updates/ (composites & content that isn't *static*)
> * http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update sites, moved here for Akamai performance)
> ----
> For JBDS, we follow the same pattern as above but use https://devstudio.redhat.com/9.0/ instead of http://download.jboss.org/jbosstools/mars/ ... but we also have a /builds/installer/ folder because the public JBDS site now includes the standalone installer:
> * https://devstudio.redhat.com/9.0/development/builds/installer/
> Also, for JBDS we don't have to differentiate between /static/ and non-static content, since Akamai set up the entire server to be mirrored to their servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20141:
------------------------------------
Max, "provide examples backing your thesis rather than just stating it" does not mean "vaguely reference some conversation". I was looking for specific examples. :(
---
Instead of telling me what you don't want, please tell me what you DO want. I've suggested this:
* http://download.jboss.org/jbosstools/mars/snapshots/updates/
* http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ (contains pretty html page from master branch; same URL for the entire 4.3.x cycle)
* http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ (contains pretty html page from stable branch; only used by QE)
* http://download.jboss.org/jbosstools/mars/development/updates/ (browseable directory w/ composite*.xml)
* http://download.jboss.org/jbosstools/mars/development/updates/core/ (pretty html page)
How would you change that? Where would you put the HTML pages, if not where I've set them above?
{quote}I don't really know how to make it more clear{quote}
Give examples, not descriptions. "Show me, don't tell me", as my grade 11 English teacher used to say. :D
> Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20141
> URL: https://issues.jboss.org/browse/JBIDE-20141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, & stable build.
> But sometimes, finding these artifacts can be a daunting task.
> Below are some URLs where things can be found.
> *CI builds / SNAPSHOTS / nightlies*
> * http://download.jboss.org/jbosstools/updates/nightly/master/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/updates/nightly/mars -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/nightly/updates/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central)
> * http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects' update sites)
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3....
> ** ..
> * http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI builds)
> *Staging Sites*
> * http://download.jboss.org/jbosstools/mars/staging/builds/
> * http://download.jboss.org/jbosstools/mars/staging/updates/
> *Development Milestones*
> * http://download.jboss.org/jbosstools/updates/development/mars/ -> ../../mars/development/updates/ (*OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/development/updates/ (composites & content that isn't *static*)
> * http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update sites, moved here for Akamai performance)
> ----
> For JBDS, we follow the same pattern as above but use https://devstudio.redhat.com/9.0/ instead of http://download.jboss.org/jbosstools/mars/ ... but we also have a /builds/installer/ folder because the public JBDS site now includes the standalone installer:
> * https://devstudio.redhat.com/9.0/development/builds/installer/
> Also, for JBDS we don't have to differentiate between /static/ and non-static content, since Akamai set up the entire server to be mirrored to their servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months