August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23064) 0 Test Failure(s) in JBIDE 4.4.1.Final for hibernate component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23064?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23064: ------------------------------- Priority: Blocker (was: Critical) > 0 Test Failure(s) in JBIDE 4.4.1.Final for hibernate component > -------------------------------------------------------------- > > Key: JBIDE-23064 > URL: https://issues.jboss.org/browse/JBIDE-23064 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Priority: Blocker > Labels: testfailure > > *0 Test Failure(s) in JBIDE 4.4.1.Final for hibernate component:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate_... > [Search for Test Failure JIRAs in JBIDE 4.4.1.Final for hibernate component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23063) Github checks are not triggered for OpenShift PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23063?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23063: ---------------------------------------- I've tried a few changes to make the configuration for openshift look more like the one for target-platform: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... > Github checks are not triggered for OpenShift PRs > ------------------------------------------------- > > Key: JBIDE-23063 > URL: https://issues.jboss.org/browse/JBIDE-23063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.1.AM3 > Reporter: Alexey Kazakov > Assignee: Nick Boldt > > For example - https://github.com/jbosstools/jbosstools-openshift/pull/1301 > I have to manually trigger the check using "testPR". I do not see any PR in OS which will have these checks triggered automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4031) Installer refuses to install cygwin

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4031?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4031: ---------------------------------- 39Mb > Installer refuses to install cygwin > ----------------------------------- > > Key: JBDS-4031 > URL: https://issues.jboss.org/browse/JBDS-4031 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jeff MAURY > Attachments: install.log > > > I'm using devsuite-1.1.0-GA-20160831-126-installer.exe > The instaler refuses to install cygwin (for bad sha1 it seems) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4031) Installer refuses to install cygwin

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4031?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-4031: -------------------------------------- How big is the online installer? > Installer refuses to install cygwin > ----------------------------------- > > Key: JBDS-4031 > URL: https://issues.jboss.org/browse/JBDS-4031 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jeff MAURY > Attachments: install.log > > > I'm using devsuite-1.1.0-GA-20160831-126-installer.exe > The instaler refuses to install cygwin (for bad sha1 it seems) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23063) Github checks are not triggered for OpenShift PRs

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23063?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23063: -------------------------------------- Assignee: Nick Boldt cc: [~mickael_istria] > Github checks are not triggered for OpenShift PRs > ------------------------------------------------- > > Key: JBIDE-23063 > URL: https://issues.jboss.org/browse/JBIDE-23063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.1.AM3 > Reporter: Alexey Kazakov > Assignee: Nick Boldt > > For example - https://github.com/jbosstools/jbosstools-openshift/pull/1301 > I have to manually trigger the check using "testPR". I do not see any PR in OS which will have these checks triggered automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23063) Github checks are not triggered for OpenShift PRs

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-23063: -------------------------------------- Summary: Github checks are not triggered for OpenShift PRs Key: JBIDE-23063 URL: https://issues.jboss.org/browse/JBIDE-23063 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, openshift Affects Versions: 4.4.1.AM3 Reporter: Alexey Kazakov For example - https://github.com/jbosstools/jbosstools-openshift/pull/1301 I have to manually trigger the check using "testPR". I do not see any PR in OS which will have these checks triggered automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4031) Installer refuses to install cygwin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4031?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4031: ------------------------------------- Obviously, that is something what was supposed to happen at some point. In previous releases cygwin.exe installer was always included, because we were releasing only bundled installer. Now we have online one, which downloads bits from URL's that supposed to be sable and produce always the same bits. To deal with possible changes we have redirects configured on developers.redhat.com instead of dealing with direct links. So in case something is changed we can redirect installer to new location. That works for Vagrant and Virtualbox, because they keep previous releases available online. This though not the case for cygwin.exe installer. We have redirect for it, but now it is changed and there is no previous version available at official web site. Possible solutions: 1. Host it at RH (requires consultation with legal dep if we can host and redistribute it); 2. Always include sygwin.exe in offline and online installer, which increases installer +1M and already approved bby legal dep. I think option 2 is the way to go. > Installer refuses to install cygwin > ----------------------------------- > > Key: JBDS-4031 > URL: https://issues.jboss.org/browse/JBDS-4031 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jeff MAURY > Attachments: install.log > > > I'm using devsuite-1.1.0-GA-20160831-126-installer.exe > The instaler refuses to install cygwin (for bad sha1 it seems) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 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 commented on JBIDE-23039: ------------------------------------- Things to test with this patch: 1) Create a cdk server adapter 2) in server editor, disable the check box "pass credentials to environment". The goal here is to make it prompt us for credentials 3) Start the CDK 4) Verify that a terminal view pops up with the output 5) Verify that it prompts you for credentials 6) Verify that your input is accepted and is actually passed to the process as expected 7) Verify that (on linux at least) it prompts you for sudo rights to run landrush. 7a) If it does not prompt you, you may not be using a clean environment. Start over, and vagrant destroy the existing VM. Landrush only prompts on the first startup. 8) Verify your sudo password is properly accepted and output indicatse landrush did what it was supposed to do That's it as far as I can tell. > 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 > 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22889) Create and use Neon.0 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22889?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22889: ------------------------------- Attachment: docker-rc1-vs-rc2.p2diff.txt New PR to move to Docker Tooling from Neon.1.RC2: https://github.com/jbosstools/jbosstools-target-platforms/pull/233 p2diff between RC1 and RC2 site: [^docker-rc1-vs-rc2.p2diff.txt] > Create and use Neon.0 target platform > ------------------------------------- > > Key: JBIDE-22889 > URL: https://issues.jboss.org/browse/JBIDE-22889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.Final > > Attachments: AM3vsFinal.txt, AM3vsFinal_sorted.txt, docker-rc1-vs-rc2.p2diff.txt > > > Prepare TP to use Neon.0 bits, including possible updates to Red Hat Central. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 10 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22998) update 4.60.1.Final TPs to latest Docker/Vagrant tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22998?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22998: ------------------------------------ New mirror pulled from http://download.eclipse.org/linuxtools/update-neon-1-docker-rc2/ to http://download.jboss.org/jbosstools/updates/requirements/docker/2.1.0.20... > update 4.60.1.Final TPs to latest Docker/Vagrant tooling > -------------------------------------------------------- > > Key: JBIDE-22998 > URL: https://issues.jboss.org/browse/JBIDE-22998 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/updates-docker-nightly/ > We should include the latest docker tooling 2.1 once it's ready to be included in the TP. > cc: [~xcoulon] [~fbricon] [~akazakov] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016