August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23022) "Unable to initializa some runtime paths" error when detecting seam runtimes.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23022?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23022: ----------------------------------- Fix Version/s: LATER > "Unable to initializa some runtime paths" error when detecting seam runtimes. > ----------------------------------------------------------------------------- > > Key: JBIDE-23022 > URL: https://issues.jboss.org/browse/JBIDE-23022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.4.1.AM3 > Environment: Devstudio 10.1.0.AM3-v20160819-0530-B5800 > Reporter: Radim Hopp > Fix For: LATER > > > Detecting seam runtime causes "Unable to initializa some runtime paths" error. I have tried seam 2.1.2 and seam 2.3.1.Final. > The same is happening when downloading these runtimes via runtime detection. > There is "All runtime detectors failed to initialize jboss-seam-2.3.1.Final" message in error log. Nothing more. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22382: ----------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: James Cobb > Priority: Minor > Labels: respin-a > Fix For: 4.4.2.AM1 > > Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23016: ----------------------------------- Sprint: devex #119 August 2016 > When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23016 > URL: https://issues.jboss.org/browse/JBIDE-23016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already). > This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights. > When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23016: ----------------------------------- Priority: Blocker (was: Major) > When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23016 > URL: https://issues.jboss.org/browse/JBIDE-23016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.1.Final > > > The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already). > This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights. > When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23012) move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23012?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23012: ---------------------------------------- Let's move this script to jbosstools-build-ci. Let's also add a message to https://github.com/jbosstools/jbosstools-documentation/blob/master/README.md that this repo is deprecated and N&N stuff has moved to jbosstools-website and createnewandnoteworthy.py to jbosstools-build-ci. [~nickboldt] can you do it? > move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23012 > URL: https://issues.jboss.org/browse/JBIDE-23012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > Since July 2014, the only file that's been changed in the jbosstools-documentation repo is ... > https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn... > In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago. > So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project? > Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23012) move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23012?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23012: ----------------------------------- Labels: (was: new_and_noteworthy) > move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23012 > URL: https://issues.jboss.org/browse/JBIDE-23012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > Since July 2014, the only file that's been changed in the jbosstools-documentation repo is ... > https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn... > In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago. > So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project? > Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23012) move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23012?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23012: ----------------------------------- Fix Version/s: 4.4.x > move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23012 > URL: https://issues.jboss.org/browse/JBIDE-23012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > Since July 2014, the only file that's been changed in the jbosstools-documentation repo is ... > https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn... > In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago. > So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project? > Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23012) move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23012?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23012: -------------------------------------- Assignee: Nick Boldt (was: Alexey Kazakov) > move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23012 > URL: https://issues.jboss.org/browse/JBIDE-23012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > Since July 2014, the only file that's been changed in the jbosstools-documentation repo is ... > https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn... > In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago. > So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project? > Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22860: -------------------------------------- Assignee: Fred Bricon [~fbricon] originally moved this issue to the 119 sprint. So assigning it to Fred. Feel free to move it back to backlog if you do not plan to work on it. > Application Wizard: Improve layout for templates > ------------------------------------------------ > > Key: JBIDE-22860 > URL: https://issues.jboss.org/browse/JBIDE-22860 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.Final > > > In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23015: -------------------------------------- Assignee: Jeff MAURY > Creating a route should have a default port > ------------------------------------------- > > Key: JBIDE-23015 > URL: https://issues.jboss.org/browse/JBIDE-23015 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.1.Final > > > When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. > There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. > The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) > To reproduce: > - git clone https://github.com/redhat-helloworld-msa/aloha > - mvn package > - build docker image from Dockerfile, to CDK docker connection > - deploy docker image to openshift -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016