April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 GA: Update support page with fedora and os x versions

by Deepak Bhole (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Deepak Bhole edited comment on TOOLSDOC-708 at 4/19/16 4:07 PM: ---------------------------------------------------------------- [~mmalina]], ah, sorry, I misunderstood. We have never branded our version as Red Hat OpenJDK. It has always been OpenJDK and I think we should continue to say OpenJDK 1.8 (and implicitly assume that it refers to our distributed version). With Linux we never had a need for branding but Windows potentially opens the door for that now. Our Java PM is on PTO right now, but I will speak to him when he is back. In the mean time, OpenJDK 1.8 is appropriate IMO. was (Author: dbhole): [~mhusnain], ah, sorry, I misunderstood. We have never branded our version as Red Hat OpenJDK. It has always been OpenJDK and I think we should continue to say OpenJDK 1.8 (and implicitly assume that it refers to our distributed version). With Linux we never had a need for branding but Windows potentially opens the door for that now. Our Java PM is on PTO right now, but I will speak to him when he is back. In the mean time, OpenJDK 1.8 is appropriate IMO. > JBDS 9.1 GA: Update support page with fedora and os x versions > -------------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Fix For: 9.1 GA > > Attachments: screenshot_support.png, Screenshot_support_update.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 GA: Update support page with fedora and os x versions

by Deepak Bhole (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Deepak Bhole edited comment on TOOLSDOC-708 at 4/19/16 4:07 PM: ---------------------------------------------------------------- [~mmalina], ah, sorry, I misunderstood. We have never branded our version as Red Hat OpenJDK. It has always been OpenJDK and I think we should continue to say OpenJDK 1.8 (and implicitly assume that it refers to our distributed version). With Linux we never had a need for branding but Windows potentially opens the door for that now. Our Java PM is on PTO right now, but I will speak to him when he is back. In the mean time, OpenJDK 1.8 is appropriate IMO. was (Author: dbhole): [~mmalina]], ah, sorry, I misunderstood. We have never branded our version as Red Hat OpenJDK. It has always been OpenJDK and I think we should continue to say OpenJDK 1.8 (and implicitly assume that it refers to our distributed version). With Linux we never had a need for branding but Windows potentially opens the door for that now. Our Java PM is on PTO right now, but I will speak to him when he is back. In the mean time, OpenJDK 1.8 is appropriate IMO. > JBDS 9.1 GA: Update support page with fedora and os x versions > -------------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Fix For: 9.1 GA > > Attachments: screenshot_support.png, Screenshot_support_update.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 GA: Update support page with fedora and os x versions

by Deepak Bhole (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Deepak Bhole commented on TOOLSDOC-708: --------------------------------------- [~mhusnain], ah, sorry, I misunderstood. We have never branded our version as Red Hat OpenJDK. It has always been OpenJDK and I think we should continue to say OpenJDK 1.8 (and implicitly assume that it refers to our distributed version). With Linux we never had a need for branding but Windows potentially opens the door for that now. Our Java PM is on PTO right now, but I will speak to him when he is back. In the mean time, OpenJDK 1.8 is appropriate IMO. > JBDS 9.1 GA: Update support page with fedora and os x versions > -------------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Fix For: 9.1 GA > > Attachments: screenshot_support.png, Screenshot_support_update.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Thomas Mäder commented on JBDS-3841: ------------------------------------ I'm sure we could come up with a way to pass the original user to the post-UAC part. However, if we require admin privileges, why do we install for a single user? Normally, when you install a program, you either put it in the users home directory (no admin required) or you install it for everybody. Why do we even need admin priviliges if we only try to update the user's environment? That should be possible without admin access. If we need an admin account to run the installer, we should not use UAC, but simply refuse to start from a non-admin account. > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.x > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 GA: Update support page with fedora and os x versions

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-708: ---------------------------------------- [~dbhole], yes, that is correct. But the main question was: What do we want to call this in the document? OpenJDK or Red Hat OpenJDK? Maybe it's not so important. > JBDS 9.1 GA: Update support page with fedora and os x versions > -------------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Fix For: 9.1 GA > > Attachments: screenshot_support.png, Screenshot_support_update.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 GA: Update support page with fedora and os x versions

by Deepak Bhole (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Deepak Bhole edited comment on TOOLSDOC-708 at 4/19/16 3:59 PM: ---------------------------------------------------------------- [~akazakov], [~mhusnain], We will only be supplying and supporting OpenJDK 1.8, so that is the only OpenJDK that should appear on the list for Windows as we do not build 1.6 or 1.7. was (Author: dbhole): alkazako, mhusnain, We will only be supplying and supporting OpenJDK 1.8, so that is the only OpenJDK that should appear on the list for Windows as we do not build 1.6 or 1.7. > JBDS 9.1 GA: Update support page with fedora and os x versions > -------------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Fix For: 9.1 GA > > Attachments: screenshot_support.png, Screenshot_support_update.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 GA: Update support page with fedora and os x versions

by Deepak Bhole (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Deepak Bhole commented on TOOLSDOC-708: --------------------------------------- alkazako, mhusnain, We will only be supplying and supporting OpenJDK 1.8, so that is the only OpenJDK that should appear on the list for Windows as we do not build 1.6 or 1.7. > JBDS 9.1 GA: Update support page with fedora and os x versions > -------------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Fix For: 9.1 GA > > Attachments: screenshot_support.png, Screenshot_support_update.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3841: ------------------------------------- In windows environment when running with Standard user account it is not possible to determine original user account after UAC prompt for administrator login. Current installer obviously works only when current session is create by user with administrator account. > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.x > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-22201: ------------------------------------------- {quote} And no, I did not remove it while CDK was running. I stopped CDK first. {quote} Interesting. Wonder whether this really is a reproducable workaround. > Error contacting OpenShift after CDK is started > ----------------------------------------------- > > Key: JBIDE-22201 > URL: https://issues.jboss.org/browse/JBIDE-22201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.3.1.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > > Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up: > {code} > Error contacting OpenShift > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233) > {code} > When you actually copy&paste that url into a browser, you will get "ok". > This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Thomas Mäder commented on JBDS-3841: ------------------------------------ Pro. > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.x > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016