April 2018 - jbosstools-issues - Jboss List Archives

[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.6.x (was: 4.5.x) > 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.6.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.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12406) Provide a quickfix to create a JAX-RS Application (java or web.xml) if missing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12406?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-12406: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Provide a quickfix to create a JAX-RS Application (java or web.xml) if missing > ------------------------------------------------------------------------------ > > Key: JBIDE-12406 > URL: https://issues.jboss.org/browse/JBIDE-12406 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 3.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.6.x > > > If no Application class (or web.xml configuration) has been set, the JAX-RS resources won't be activated and the user will get 404 responses. > Provide quickfixes at the project level to create a java class or create/modify the web.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15488: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Web Service Tester doesn't work with https and self-signed certificate > ---------------------------------------------------------------------- > > Key: JBIDE-15488 > URL: https://issues.jboss.org/browse/JBIDE-15488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Juergen Zimmermann > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.6.x > > > If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests): > {code} > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22329) JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22329?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22329: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-22329 > URL: https://issues.jboss.org/browse/JBIDE-22329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Automated Error Reporting Bot > Assignee: Xavier Coulon > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Failed to build or refresh the JAX-RS metamodel > {noformat} > org.eclipse.jdt.core.JavaModelException: submt(HttpServletRequest, int) [in PublicWS [in [Working copy] PublicWS.java [in be.fromprison.ws.endpoints [in src/main/java [in from-prison]]]]] does not exist > at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.SourceRefElement.getSourceRange(SourceRefElement.java:218) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findDeclaringNode(JdtUtils.java:494) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveAllAnnotations(JdtUtils.java:373) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:153) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v_OTDT_r242_201601310642 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 | > | org.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > Operating Systems: > | Linux | 3.16.0 | 4.4.7.fc23 | > | MacOSX | 10.11.4 | 10.11.4 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571dd2b8e4b08bd809...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12161) Deploy application to JBoss AS 7 in domain mode

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12161?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-12161: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Deploy application to JBoss AS 7 in domain mode > ----------------------------------------------- > > Key: JBIDE-12161 > URL: https://issues.jboss.org/browse/JBIDE-12161 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.0.CR1 > Environment: Any. > Reporter: Humberto Ferreira da Luz Jr. > Assignee: Rob Stryker > Labels: f2f2012 > Fix For: 4.6.x > > > I think JBoss Tools should be able to deploy an application to JBoss AS 7 in domain mode. > We would choose an specific server group (or any) and the application would be automatically deployed (I guess JBoss AS CLI could be directly used by JBoss Tools instead of ftp, ssh...). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24305) Implement JSF faces-config.xml test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24305?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24305: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Implement JSF faces-config.xml test > ----------------------------------- > > Key: JBIDE-24305 > URL: https://issues.jboss.org/browse/JBIDE-24305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, jsf > Affects Versions: 4.4.4.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25698) Allow users to deploy a jar

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25698?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25698: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Allow users to deploy a jar > --------------------------- > > Key: JBIDE-25698 > URL: https://issues.jboss.org/browse/JBIDE-25698 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM1 > Reporter: Andre Dietisheim > Fix For: 4.6.x > > > Azure tooling blogged about how one would deploy a springboot application to their cloud: https://docs.microsoft.com/en-gb/java/azure/eclipse/azure-toolkit-for-ecl... > They're basically able to deploy a locally built jar as a docker container. > This is interesting in the sense that the hurdle for cloud-noobs is very low: The only thing they need to know is what Docker base image is required. The docker image is built and deployed by the cloud. They're not required to know about templates (new application wizard/template), have a remote git repo for the code (new application wizard/builder image), nor build a docker image locally (push docker image wizard) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20576) OpenShift Explorer: Add filter of resources by label

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20576?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20576: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > OpenShift Explorer: Add filter of resources by label > ---------------------------------------------------- > > Key: JBIDE-20576 > URL: https://issues.jboss.org/browse/JBIDE-20576 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.6.x > > > The upcoming version of the OpenShift Explorer (JBIDE-19178) should allow filtering of resources by label -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22378) Server editor: cannot edit the route

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22378?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22378: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Server editor: cannot edit the route > ------------------------------------ > > Key: JBIDE-22378 > URL: https://issues.jboss.org/browse/JBIDE-22378 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor > Fix For: 4.6.x > > Attachments: server-editor.png > > > The server editor wont allow the user to edit the route: > !server-editor.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23711: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.6.x > > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 2018