August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4024) Installation for selected components called twice sometimes

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4024?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4024: -------------------------------- Fix Version/s: 10.1.0.GA > Installation for selected components called twice sometimes > ----------------------------------------------------------- > > Key: JBDS-4024 > URL: https://issues.jboss.org/browse/JBDS-4024 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Fix For: 10.1.0.GA > > > Regression after fixing JBDS-4015 due to wron processing of installComplete events. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4024) Installation for selected components called twice sometimes

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4024?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4024: ----------------------------- > Installation for selected components called twice sometimes > ----------------------------------------------------------- > > Key: JBDS-4024 > URL: https://issues.jboss.org/browse/JBDS-4024 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Fix For: 10.1.0.GA > > > Regression after fixing JBDS-4015 due to wron processing of installComplete events. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4024) Installation for selected components called twice sometimes

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4024: ----------------------------------- Summary: Installation for selected components called twice sometimes Key: JBDS-4024 URL: https://issues.jboss.org/browse/JBDS-4024 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.GA Reporter: Denis Golovin Regression after fixing JBDS-4015 due to wron processing of installComplete events. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23060) Upgrade Forge Runtime to 3.3.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23060?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-23060: ------------------------------------ Labels: new_and_noteworthy (was: ) > Upgrade Forge Runtime to 3.3.1.Final > ------------------------------------ > > Key: JBIDE-23060 > URL: https://issues.jboss.org/browse/JBIDE-23060 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.1.AM3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23060) Upgrade Forge Runtime to 3.3.1.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-23060: --------------------------------------- Summary: Upgrade Forge Runtime to 3.3.1.Final Key: JBIDE-23060 URL: https://issues.jboss.org/browse/JBIDE-23060 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.4.1.AM3 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.4.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22225: ------------------------------------- [~akazakov], I have tested it and record a demo - https://youtu.be/1cKPPQrlC4k Latest Openshift / Latest JSDT > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22225: ---------------------------------------- [~ibuziuk] by any chance can you test OpenShift with the latest JSDT to make sure it works as expected? > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23052) IllegalStateException in SProperties.get

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23052?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23052: ---------------------------------------- We have 74 reports of this problem from 18 reporters. I added a note to the report asking for steps to reproduce. > IllegalStateException in SProperties.get > ---------------------------------------- > > Key: JBIDE-23052 > URL: https://issues.jboss.org/browse/JBIDE-23052 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > The following problem was reported via the automated error reporting: > Message: Cannot read C:\Desarrollo\workspaceSTS\.metadata\.plugins\org.jboss.tools.common.model\tmp\efs_8421649034830489156.sp.txt for object > entity:FacesConfig12 > id= > xmlns=http://java.sun.com/xml/ns/javaee > xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance > xmlns:xi=http://www.w3.org/2001/XInclude > xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd > version=1.2 > isIncorrect=no > incorrectBody= > encoding=UTF-8 > {noformat} > java.lang.IllegalStateException: Cannot read C:\Desarrollo\workspaceSTS\.metadata\.plugins\org.jboss.tools.common.model\tmp\efs_8421649034830489156.sp.txt for object > entity:FacesConfig12 > id= > xmlns=http://java.sun.com/xml/ns/javaee > xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance > xmlns:xi=http://www.w3.org/2001/XInclude > xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd > version=1.2 > isIncorrect=no > incorrectBody= > encoding=UTF-8 > at org.jboss.tools.common.model.impl.SProperties.get(XModelObjectImpl.java:692) > at org.jboss.tools.common.model.impl.XModelObjectImpl.get(XModelObjectImpl.java:145) > at org.jboss.tools.common.model.filesystems.impl.FileAnyImpl.get(FileAnyImpl.java:176) > at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.get(AbstractExtendedXMLFileImpl.java:71) > at org.jboss.tools.jst.web.model.AbstractWebFileImpl.getAsText(AbstractWebFileImpl.java:54) > at org.jboss.tools.common.model.util.PositionHolder.update(PositionHolder.java:60) > at org.jboss.tools.jst.web.model.project.ext.store.XMLValueInfo.getPositionHolder(XMLValueInfo.java:59) > at org.jboss.tools.jst.web.model.project.ext.store.XMLValueInfo.getLength(XMLValueInfo.java:41) > at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:174) > at org.jboss.tools.jst.web.validation.Check.fireMessage(Check.java:49) > at org.jboss.tools.jst.web.validation.CheckClass.fireNotExist(CheckClass.java:192) > at org.jboss.tools.jst.web.validation.CheckClass.check(CheckClass.java:96) > at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateObject(FacesConfigValidator.java:284) > at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateObject(FacesConfigValidator.java:289) > at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateObject(FacesConfigValidator.java:289) > at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateFile(FacesConfigValidator.java:276) > at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validate(FacesConfigValidator.java:265) > at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:140) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.10.0.v20150423-0755 | 3.11.0.v20160503-1608 | > | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 | > | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 | > | org.eclipse.ltk.core.refactoring | 3.6.200.v20140826-0859 | 3.7.0.v20160419-0705 | > | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20160518-1817 | > | org.eclipse.search | 3.10.0.v20150318-0856 | 3.10.0.v20150318-0856 | > | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 | > | org.eclipse.team.svn.core | 3.0.4.I20160131-1700 | 3.0.4.I20160131-1700 | > | org.eclipse.team.svn.ui | 3.0.4.I20160131-1700 | 3.0.4.I20160131-1700 | > | org.eclipse.team.ui | 3.7.200.v20150203-1452 | 3.7.200.v20150203-1452 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 | > | org.eclipse.ui.editors | 3.9.0.v20150213-1939 | 3.9.0.v20150213-1939 | > | org.eclipse.ui.ide | 3.11.0.v20150825-2158 | 3.11.0.v20150825-2158 | > | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 | > | org.eclipse.ui.navigator.resources | 3.5.1.v20160128-1644 | 3.5.100.v20160518-1929 | > | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 | > | org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.202.v201602111638 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 | > | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | > | org.jboss.tools.batch.core | 1.8.0.Final-v20160610-0126-B1 | 1.8.0.Final-v20160610-0126-B1 | > | org.jboss.tools.common | 3.7.0.Final-v20150924-2213-B38 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.common.model | 3.7.0.Final-v20150924-2213-B38 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.common.model.ui | 3.7.0.Final-v20150924-2213-B38 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.hibernate.ui | 5.0.1.Final-v20160331-1852-B88 | 5.1.0.Final-v20160609-2146-B2 | > | org.jboss.tools.hibernate.xml | 5.0.1.Final-v20160331-1852-B88 | 5.0.1.Final-v20160331-1852-B88 | > | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.0.Final-v20160610-0126-B1 | > | org.jboss.tools.jsf.ui | 3.7.1.Final-v20160330-2256-B84 | 3.7.1.Final-v20160330-2256-B84 | > | org.jboss.tools.jst.web | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 | > | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 | > | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 | > | org.jboss.tools.seam.core | 3.8.0.Final-v20160610-0126-B1 | 3.8.0.Final-v20160610-0126-B1 | > Operating Systems: > | Linux | 3.2.0 | 4.6.3.fc24 | > | MacOSX | 10.11.4 | 10.11.6 | > | 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/57193d5de4b0cd449c...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-846) Productise the Devstudio IS stand-alone installer

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-846: -------------------------------- Summary: Productise the Devstudio IS stand-alone installer Key: JBTIS-846 URL: https://issues.jboss.org/browse/JBTIS-846 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 9.0.2.GA Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 9.0.2.GA The IS devstudio pom can now build a stand-alone installer. Modify any/all Jenkins jobs, product.yml, etc to handle productizing the installer. -- 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 Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Roland Grunberg edited comment on JBIDE-23039 at 8/30/16 1:02 PM: ------------------------------------------------------------------ I haven't had time to test this out, but here are a few suggestions : - Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag. - Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash', or 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"} UPDATE : After some more tinkering, I set up an example of calling 'vagrant up fedora/23-cloud-base', which causes a prompt because mutliple providers exist for that image. If one just calls that with Runtime.getRuntime().exec(..) that error message you describe above comes up. If we then wrap that script around 'script -qfc "vagrant up fedora/23-cloud-base" /dev/null', then vagrant responds with the expected output indicating one must select a provider, and even the terminal codes are intact within the message. Given that these will be taken care of by Terminal.TM I think this should solve your needs. Also don't forget that you probably only need that for "Linux" and things should work using just the standard 'vagrant up' on Windows according to the vagrant sources. was (Author: rgrunber): I haven't had time to test this out, but here are a few suggestions : - Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag. - Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash', or 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"} UPDATE : After some more tinkering, I set up an example of calling 'vagrant up fedora/23-cloud-base', which causes a prompt because mutliple providers exist for that image. If one just calls that with Runtime.getRuntime().exec(..) that error message you describe above comes up. If we then wrap that script around 'script -qfc "vagrant up fedora/23-cloud-base" /dev/null', then vagrant responds with the expected output indicating one must select a provider, and even the terminal codes are intact within the message. Given that these will be taken care of by Terminal.TM I think this should solve your needs. Also don't forget that you probably only need that for "Linux" because according to vagrant sources, stdin.tty is never checked unless not on Windows. > 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)

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 August 2016