September 2016 - jbosstools-issues

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23016: -------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > 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.2.AM1 > > > 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23016: -------------------------------- Sprint: devex #120 September 2016 (was: 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 > Priority: Blocker > Fix For: 4.4.2.AM1 > > > 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-18912) Custom deploy dir with remote server using filesystem operations does not work

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18912: -------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Custom deploy dir with remote server using filesystem operations does not work > ------------------------------------------------------------------------------ > > Key: JBIDE-18912 > URL: https://issues.jboss.org/browse/JBIDE-18912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.4.2.AM1 > > > This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used). > Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles. > I tried this several times and still could not get it to work. > Perhaps it might be worth to try and get this in the final 4.2.1.Final build? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23039: -------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Need an interactive terminal that fits specific requirements > ------------------------------------------------------------ > > Key: JBIDE-23039 > URL: https://issues.jboss.org/browse/JBIDE-23039 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.2.AM1 > > Attachments: vagranttty.png > > > CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. > 1) I must be able to get a Process or IProcess object when a command is run > 2) I must be able to get an event or know when the process terminates > 3) The terminal or console must be interactive and allow user input when prompted. > 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. > These three requirements thus far seem impossible to solve. Solutions that have been attempted are: > 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. > 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed: > a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input > b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen > 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. > Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. > Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? > No other obvious solutions have presented themselves in the past year. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23039: -------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Need an interactive terminal that fits specific requirements > ------------------------------------------------------------ > > Key: JBIDE-23039 > URL: https://issues.jboss.org/browse/JBIDE-23039 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.2.AM1 > > Attachments: vagranttty.png > > > CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. > 1) I must be able to get a Process or IProcess object when a command is run > 2) I must be able to get an event or know when the process terminates > 3) The terminal or console must be interactive and allow user input when prompted. > 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. > These three requirements thus far seem impossible to solve. Solutions that have been attempted are: > 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. > 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed: > a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input > b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen > 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. > Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. > Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? > No other obvious solutions have presented themselves in the past year. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22869: -------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22869: -------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13661) Cannot create archive from archive in explorer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13661?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13661: -------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Cannot create archive from archive in explorer > ---------------------------------------------- > > Key: JBIDE-13661 > URL: https://issues.jboss.org/browse/JBIDE-13661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13661) Cannot create archive from archive in explorer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13661?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13661: -------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Cannot create archive from archive in explorer > ---------------------------------------------- > > Key: JBIDE-13661 > URL: https://issues.jboss.org/browse/JBIDE-13661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22578: -------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Publishing sometimes recursively deletes parent to deploy directory > ------------------------------------------------------------------- > > Key: JBIDE-22578 > URL: https://issues.jboss.org/browse/JBIDE-22578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Final > Environment: Eclipse Mars.2 Release (4.5.2) > Java 1.8.0_91 > Windows 7 64-bit > JBoss EAP 6.4.0 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml > > > For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it. > It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools. > We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx). > Our workspaces are structured as follows: > {noformat} > WORKSPACEROOT=$DEVROOT\workspacename > # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server > $WORKSPACEROOT\deploy > # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling > $WORKSPACEROOT\src > # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/data > # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/tmp > {noformat} > The Server is configured to "Automatically publish when resources change". > What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT. > The eclipse log includes the following: > {noformat} > !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problems occurred refreshing resources > !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problem finding next change, code: 5 > !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 > !MESSAGE Incremental publish failed for module $MODULENAME > !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 > !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process. > {noformat} > Any idea what might be happening? > Is there some debug logging we can enable to get better visibility to what's going on? -- 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 September 2016