November 2016 - jbosstools-issues

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23431?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23431: ------------------------------------- Running a windows server isn't our primary usecase, but I'll look into it. > 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.0.AM1 > > > 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)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23430) Run as -> Run on server -> browser might open too early causing http 404

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23430?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23430. --------------------------------- Resolution: Rejected We wait a set amount of time of 20 seconds. We don't want to wait forever, and the user can simply refresh if the browser opens too early and the console indicates the deployment is still being deployed. This is better behavior than doing nothing for an extended period while a user sits confused. Sorry :( > Run as -> Run on server -> browser might open too early causing http 404 > ------------------------------------------------------------------------ > > Key: JBIDE-23430 > URL: https://issues.jboss.org/browse/JBIDE-23430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Josef Ludvicek > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: runas.png > > > There should be some mechanism to detect when application is succesfully deployed. > It is possible that on slow machine it starts to deploy and open internal web browser too early - before app is fully deployed. > Stepps: > * start eap server > * right click on app -> Run as -> run on server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23430) Run as -> Run on server -> browser might open too early causing http 404

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23430?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23430: -------------------------------- Fix Version/s: 4.5.0.AM1 > Run as -> Run on server -> browser might open too early causing http 404 > ------------------------------------------------------------------------ > > Key: JBIDE-23430 > URL: https://issues.jboss.org/browse/JBIDE-23430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Josef Ludvicek > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: runas.png > > > There should be some mechanism to detect when application is succesfully deployed. > It is possible that on slow machine it starts to deploy and open internal web browser too early - before app is fully deployed. > Stepps: > * start eap server > * right click on app -> Run as -> run on server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22819) wrap staging build process with a series of jenkins jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22819: ------------------------------- Summary: wrap staging build process with a series of jenkins jobs (was: wrap staging build process with a jenkins job) > wrap staging build process with a series of jenkins jobs > -------------------------------------------------------- > > Key: JBIDE-22819 > URL: https://issues.jboss.org/browse/JBIDE-22819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > Job requires about 13 params: > {code} > version (JBT and JBDS) > versionWithRespin (JBT and JBDS) > versionWithRespin_PREV (JBT and JBDS) > target platforms (min, max, central) > respin # (- or a, b, c) > devsuite installerExe url > stream_JBT=master # or 4.4.neon > stream_DS=master # or 10.0.neon > {code} > See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19933: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19933: ------------------------------------ Slip again - missed this last week. > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23387) enable jiralint nagging for CDK project JIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23387?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23387: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > enable jiralint nagging for CDK project JIRAs > --------------------------------------------- > > Key: JBIDE-23387 > URL: https://issues.jboss.org/browse/JBIDE-23387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > As discussed on the sprint retrospective, CDK devs are not properly cleaning up their JIRAs (eg., completed issues not marked resolved/closed). > So, we should enable jiralint [1] to also nag those devs about their jiras. > [1] https://github.com/jbosstools/jiralint -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20683) Remove unnecessary lines in ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20683?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-20683. -------------------------------- Fix Version/s: 4.4.2.Final (was: LATER) Resolution: Done Fixed as part of JBIDE-23475. > Remove unnecessary lines in ide-config.properties > ------------------------------------------------- > > Key: JBIDE-20683 > URL: https://issues.jboss.org/browse/JBIDE-20683 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, website > Affects Versions: 4.3.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Trivial > Fix For: 4.4.2.Final > > > Currently, the properties file at > http://download.jboss.org/jbosstools/configuration/ide-config.properties > contains lots of lines which are commented out. I suggest to remove all unnecessary lines to improve the readability. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20683) Remove unnecessary lines in ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20683?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20683: ------------------------------- Sprint: devex #123 November 2016 > Remove unnecessary lines in ide-config.properties > ------------------------------------------------- > > Key: JBIDE-20683 > URL: https://issues.jboss.org/browse/JBIDE-20683 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, website > Affects Versions: 4.3.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Trivial > Fix For: LATER > > > Currently, the properties file at > http://download.jboss.org/jbosstools/configuration/ide-config.properties > contains lots of lines which are commented out. I suggest to remove all unnecessary lines to improve the readability. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23387) enable jiralint nagging for CDK project JIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23387?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23387: ------------------------------- Sprint: (was: devex #123 November 2016) > enable jiralint nagging for CDK project JIRAs > --------------------------------------------- > > Key: JBIDE-23387 > URL: https://issues.jboss.org/browse/JBIDE-23387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > As discussed on the sprint retrospective, CDK devs are not properly cleaning up their JIRAs (eg., completed issues not marked resolved/closed). > So, we should enable jiralint [1] to also nag those devs about their jiras. > [1] https://github.com/jbosstools/jiralint -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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