[JBoss JIRA] (JBIDE-23054) Build for java-language-server
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-23054:
------------------------------------
Summary: Build for java-language-server
Key: JBIDE-23054
URL: https://issues.jboss.org/browse/JBIDE-23054
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Reporter: Gorkem Ercan
I need a build job that can build java-language server and publish it to download server for the use of VSCode extension.
Sources:_ https://github.com/gorkem/java-language-server_
Build command: _mvn -Pserver-distro clean verify_
Archive: server/org.jboss.tools.vscode.product/target/repository
Publish: file(s) under server/org.jboss.tools.vscode.product/distro/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[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:
-------------------------------------
Code for this test can be found here: https://github.com/robstryker/jbosstools-openshift/tree/JBIDE-23039
> 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, 10 months
[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:
--------------------------------
Attachment: vagranttty.png
attaching screenshot of my code attempt using the method [~rgrunber] suggested.
> 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, 10 months
[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:
-------------------------------------
[~rgrunber] Doesn't work. When I do it this way, I get the following errors:
{code}
==> default: Registering box with vagrant-registration...
Vagrant is attempting to interface with the UI in a way that requires
a TTY. Most actions in Vagrant that require a TTY have configuration
switches to disable this requirement. Please do that or run Vagrant
with TTY.
{code}
http://i.imgur.com/rMjt7s5.png
Using Runtime.getRuntime().exec(etc) does not behave like a TTY terminal, and so most vagrant plugins that require TTY fail in this fashion.
> 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
>
> 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, 10 months
[JBoss JIRA] (JBIDE-23053) Central news info does not seem uptodate
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-23053:
----------------------------------
Summary: Central news info does not seem uptodate
Key: JBIDE-23053
URL: https://issues.jboss.org/browse/JBIDE-23053
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.4.1.AM3
Reporter: Jeff MAURY
Fix For: 4.4.x
The RedHat Central view does not seem to display uptodate news: latest info is from June 2016 which is almost 3 months old
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23052) IllegalStateException in SProperties.get
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-23052:
-----------------------------------------------------
Summary: 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
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)
7 years, 10 months
[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 updated JBIDE-23052:
-----------------------------------
Fix Version/s: 4.4.x
> 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
> 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)
7 years, 10 months
