June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22370) Intermittent warning when importing quickstarts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22370?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22370: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Intermittent warning when importing quickstarts > ----------------------------------------------- > > Key: JBIDE-22370 > URL: https://issues.jboss.org/browse/JBIDE-22370 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.0.Alpha1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.x > > > The issue is described in JBEAP-4286. The patch that was created for that one does not really solve the issue at it's core. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24498: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Deploy Docker Image wizard: results dialog is not very informative > ------------------------------------------------------------------ > > Key: JBIDE-24498 > URL: https://issues.jboss.org/browse/JBIDE-24498 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: image-2017-05-23-11-07-21-461.png > > > steps to reproduce: > # ASSERT: have a docker connection > # ASSERT: have an OpenShift connection > # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..." > # ASSERT: deploy docker image wizard pops up > # EXEC: provide settings and finish the wizard > Result: > A dialog pops up informing you about the result of your deployment. > !image-2017-05-23-11-07-21-461.png! > But the dialog is not very informative, it's far from obvious what the different informations are all about: > * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator) > * There's a list of items. Nothing in the dialog tells the user what these items are. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18902) Add Ceylon IDE to JBoss Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18902?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18902: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Add Ceylon IDE to JBoss Central > ------------------------------- > > Key: JBIDE-18902 > URL: https://issues.jboss.org/browse/JBIDE-18902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.5.x > > > It's probably time to consider adding Ceylon IDE to JBoss Central, provided it doesn't break anything. > Questions are : > - Early Access or not? > - should JBDS get it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23431) Remote server over ssh does not work with cygwin

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23431?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23431: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Remote server over ssh does not work with cygwin > ------------------------------------------------ > > Key: JBIDE-23431 > URL: https://issues.jboss.org/browse/JBIDE-23431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > Today [~rawagner] reported to me that he cannot run a remote server over ssh on Windows. > So I tried it and I get the same error as him: > {code} > cd / > cd / > echo $PWD'>' > echo $PWD'>' > java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone& > echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$! > Last login: Thu Nov 3 10:47:34 2016 from 10.40.4.40 > 0;~ > jbossqa@DESKTOP-QOUU1SV ~ > $ cd / > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ cd / > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ echo $PWD'>' > /> > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ echo $PWD'>' > /> > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.re solver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInter val=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs= org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/ c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration =file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging. properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jb oss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss -modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as .standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/c ygdrive/c/mmalina/wildfly-10.0.0.Final/standalone& > [1] 7888 > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$! > JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:7888 > 0;/ > jbossqa@DESKTOP-QOUU1SV / > $ Error: Unable to access jarfile /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar > wait 7888; echo "JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x147816649407 6:" $? > [1]+ Exit 1 java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone > JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x1478166494076: 1 > {code} > I'm not sure what's going on, /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar is accessible for me just fine over ssh. One may think that perhaps the java process has to use windows paths. But when I try to run ./standalone.sh in cygwin there, it works just fine. So I guess there is no reason why it shouldn't work over ssh then. We just need to figure out what's wrong. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23658) Hibernate console configuration wizard problems - and no way to get specifics

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23658?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23658: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Hibernate console configuration wizard problems - and no way to get specifics > ----------------------------------------------------------------------------- > > Key: JBIDE-23658 > URL: https://issues.jboss.org/browse/JBIDE-23658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.2.Final > Environment: Neon.1 and Neon.2, Windows 7, targeting Oracle > Reporter: Jesper Skov > Assignee: Koen Aers > Fix For: 4.5.x > > Attachments: empty-clean.zip > > > Creating a Hibernate Console Configuration using the wizard fails for most of our projects. > All the feedback we have is the text in red: "Could not create JPA based Configuration" > I would have liked to qualify this problem report with some more information. But there is no problems reported in the eclipse log. > I have tried enabling debugging, as per http://docs.jboss.org/tools/latest/en/hibernatetools/html/plugins.html#de..., without getting any output to the Eclipse Error console, or to the hibernate log file. > We wonder if maybe the plugin/perspective is just dead (or dying). > The plugin documentation has snapshots from 2010/2011, and the JBossTools documentation itself (http://docs.jboss.org/tools/latest/) was not updated since 4.1.0/2013. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15464) Create Datasource Dialog/Wizard should let preview changes in affected resources

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15464?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15464: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Create Datasource Dialog/Wizard should let preview changes in affected resources > -------------------------------------------------------------------------------- > > Key: JBIDE-15464 > URL: https://issues.jboss.org/browse/JBIDE-15464 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common > Affects Versions: 4.1.1.Alpha2 > Reporter: Denis Golovin > Assignee: Jeff MAURY > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24495) Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24495?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24495: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose" > --------------------------------------------------------------------------- > > Key: JBIDE-24495 > URL: https://issues.jboss.org/browse/JBIDE-24495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Fix For: 4.5.x > > > [Helloworld MSA|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-msa/master/re...] - the reference examples for openshift - is using the command line client "oc" to create the applications in OpenShift. > A typical approach is doing the following: > {code} > $ oc new-build --binary --name=hola -l app=hola > $ mvn package; oc start-build hola --from-dir=. --follow > $ oc new-app hola -l app=hola,hystrix.enabled=true > $ oc expose service hola > {code} > For people to be able to run those with Eclipse tooling people should be able to run the equivalent in Eclipse. > The alternative approach, that's currently available in Eclipse is imbo less evident: Users can currently build docker images locally and deploy them to OpenShift. > The tricky part though - for now - is that the CDK is not providing access to the docker registry from the outside: the docker registry address is a private IP that's only reachable within OpenShift. Users can get around this limitation by building docker images using the docker daemon in OpenShift, which is publicly reachable. Once available in the OpenShift docker daemon it can be pushed to the OpenShift docker registry. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21652?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21652: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > We should make OS 3 application status more visible for users > ------------------------------------------------------------- > > Key: JBIDE-21652 > URL: https://issues.jboss.org/browse/JBIDE-21652 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Fix For: 4.5.x > > > Currently it can be confusing for users when an application is not available because it's building. > We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters). > For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible. > OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24179) Command to tune autoscaling

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24179?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24179: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Command to tune autoscaling > --------------------------- > > Key: JBIDE-24179 > URL: https://issues.jboss.org/browse/JBIDE-24179 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23924: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.x > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017