[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Mat Booth (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Mat Booth commented on JBDS-3981:
---------------------------------
Hey, do you know why does org.eclipse.linuxtools.docker.feature still appear in this RPM? This feature is supplied by a separate RPM.
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM1
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23143 at 9/14/16 12:39 PM:
--------------------------------------------------------------
Tried to reproduce your issue...
1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
2. Window > Preferences > Install/Update > Available Software Sites > disable the Luna sites, as they're hella slow.
[^jbt4.4.1_on_neon.1.RC3_disabled_sites.png]
3. Help > Eclipse Marketplace... > Search for "jboss" and install JBoss Tools 4.4.1.Final
4. Remediation needed: [^jbt4.4.1_on_neon.1.RC3_remediation_needed.png]
5. I got a different conflict:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
Only one of the following can be installed at once:
Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
Code Recommenders Dependency Identification UI 2.4.3.v20160708-1339 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160708-1339)
Cannot satisfy dependency:
From: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160708-1339]
Cannot satisfy dependency:
From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
Cannot satisfy dependency:
From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code} -- [^jbt4.4.1_on_neon.1.RC3.png]
6. Remediation alternate: [^jbt4.4.1_on_neon.1.RC3_remediation_opt2.png]
was (Author: nickboldt):
Tried to reproduce your issue...
1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
2. Window > Preferences > Install/Update > Available Software Sites > disable the Luna sites, as they're hella slow.
[^jbt4.4.1_on_neon.1.RC3_disabled_sites.png]
3. Help > Eclipse Marketplace... > Search for "jboss" and install JBoss Tools 4.4.1.Final
4. Remediation needed: [^jbt4.4.1_on_neon.1.RC3_remediation_needed.png]
5. I got a different conflict:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
Only one of the following can be installed at once:
Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
Code Recommenders Dependency Identification UI 2.4.3.v20160708-1339 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160708-1339)
Cannot satisfy dependency:
From: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160708-1339]
Cannot satisfy dependency:
From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
Cannot satisfy dependency:
From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code} --[^jbt4.4.1_on_neon.1.RC3.png]
6. Remediation alternate: [^jbt4.4.1_on_neon.1.RC3_remediation_opt2.png]
> Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
> --------------------------------------------------------------
>
> Key: JBIDE-23143
> URL: https://issues.jboss.org/browse/JBIDE-23143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, updatesite, upstream, webservices
> Affects Versions: 4.4.1.Final
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png
>
>
> When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen.
> !neon-1-remediation.png!
> If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools.
> This is the original error message (third option):
> {code}
> Your original request has been modified.
> "Code Recommenders Snipmatch" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> Only one of the following can be installed at once:
> Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
> Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824)
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
> To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824]
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23143:
-------------------------------
Attachment: jbt4.4.1_on_neon.1.RC3.png
jbt4.4.1_on_neon.1.RC3_remediation_needed.png
jbt4.4.1_on_neon.1.RC3_remediation_opt2.png
jbt4.4.1_on_neon.1.RC3_disabled_sites.png
Tried to reproduce your issue...
1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
2. Window > Preferences > Install/Update > Available Software Sites > disable the Luna sites, as they're hella slow.
[^jbt4.4.1_on_neon.1.RC3_disabled_sites.png|thumbnail]
3. Help > Eclipse Marketplace... > Search for "jboss" and install JBoss Tools 4.4.1.Final
4. Remediation needed: [^jbt4.4.1_on_neon.1.RC3_remediation_needed.png|thumbnail]
5. I got a different conflict:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
Only one of the following can be installed at once:
Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
Code Recommenders Dependency Identification UI 2.4.3.v20160708-1339 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160708-1339)
Cannot satisfy dependency:
From: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160708-1339]
Cannot satisfy dependency:
From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
Cannot satisfy dependency:
From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code}
[^jbt4.4.1_on_neon.1.RC3.png|thumbnail]
6. Remediation alternate: [^jbt4.4.1_on_neon.1.RC3_remediation_opt2.png|thumbnail]
> Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
> --------------------------------------------------------------
>
> Key: JBIDE-23143
> URL: https://issues.jboss.org/browse/JBIDE-23143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, updatesite, upstream, webservices
> Affects Versions: 4.4.1.Final
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png
>
>
> When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen.
> !neon-1-remediation.png!
> If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools.
> This is the original error message (third option):
> {code}
> Your original request has been modified.
> "Code Recommenders Snipmatch" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> Only one of the following can be installed at once:
> Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
> Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824)
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
> To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824]
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23143 at 9/14/16 12:38 PM:
--------------------------------------------------------------
Tried to reproduce your issue...
1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
2. Window > Preferences > Install/Update > Available Software Sites > disable the Luna sites, as they're hella slow.
[^jbt4.4.1_on_neon.1.RC3_disabled_sites.png]
3. Help > Eclipse Marketplace... > Search for "jboss" and install JBoss Tools 4.4.1.Final
4. Remediation needed: [^jbt4.4.1_on_neon.1.RC3_remediation_needed.png]
5. I got a different conflict:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
Only one of the following can be installed at once:
Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
Code Recommenders Dependency Identification UI 2.4.3.v20160708-1339 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160708-1339)
Cannot satisfy dependency:
From: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160708-1339]
Cannot satisfy dependency:
From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
Cannot satisfy dependency:
From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code} --[^jbt4.4.1_on_neon.1.RC3.png]
6. Remediation alternate: [^jbt4.4.1_on_neon.1.RC3_remediation_opt2.png]
was (Author: nickboldt):
Tried to reproduce your issue...
1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
2. Window > Preferences > Install/Update > Available Software Sites > disable the Luna sites, as they're hella slow.
[^jbt4.4.1_on_neon.1.RC3_disabled_sites.png|thumbnail]
3. Help > Eclipse Marketplace... > Search for "jboss" and install JBoss Tools 4.4.1.Final
4. Remediation needed: [^jbt4.4.1_on_neon.1.RC3_remediation_needed.png|thumbnail]
5. I got a different conflict:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
Only one of the following can be installed at once:
Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
Code Recommenders Dependency Identification UI 2.4.3.v20160708-1339 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160708-1339)
Cannot satisfy dependency:
From: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609)
To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160708-1339]
Cannot satisfy dependency:
From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
Cannot satisfy dependency:
From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code}
[^jbt4.4.1_on_neon.1.RC3.png|thumbnail]
6. Remediation alternate: [^jbt4.4.1_on_neon.1.RC3_remediation_opt2.png|thumbnail]
> Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
> --------------------------------------------------------------
>
> Key: JBIDE-23143
> URL: https://issues.jboss.org/browse/JBIDE-23143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, updatesite, upstream, webservices
> Affects Versions: 4.4.1.Final
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png
>
>
> When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen.
> !neon-1-remediation.png!
> If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools.
> This is the original error message (third option):
> {code}
> Your original request has been modified.
> "Code Recommenders Snipmatch" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> Only one of the following can be installed at once:
> Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
> Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824)
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
> To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824]
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3627:
--------------------------------
Fix Version/s: 10.2.0.GA
(was: 10.2.0.AM1)
Epic Name: DevSuite Installer T&C's Support
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.GA
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3627:
--------------------------------
Affects Version/s: 10.0.0.GA
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM1
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23134) Improve UI of Deployment tab of Runtime Editor
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-23134 at 9/14/16 12:28 PM:
------------------------------------------------------------------
{quote}Actions where users won’t affect the website are where you use a link. These are actions that take users from one page to another without changing anything on the website’s back or front-end. The user is basically a spectator browsing through content.{quote}
In that case, the action is clearly changing the [application] front-end, user is not browsing through content, he's intereacting with the front-end.
I invoke [~crobson]! Catherine, can you or someone else from UX please have a look at the screenshot and tell us whether the "Refresh" link is okay here or whether a button would be better?
was (Author: mickael_istria):
{quote}Actions where users won’t affect the website are where you use a link. These are actions that take users from one page to another without changing anything on the website’s back or front-end. The user is basically a spectator browsing through content.{quote}
In that case, the action is clearly changing the [application] front-end, user is not browsing through content, he's intereacting with the front-end.
I invoke [~crobson]! Catherine, can you -or someone else from UX- please have a look at the screenshot and tell us whether the "Refresh" link is okay here or whether a button would be better?
> Improve UI of Deployment tab of Runtime Editor
> ----------------------------------------------
>
> Key: JBIDE-23134
> URL: https://issues.jboss.org/browse/JBIDE-23134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
> Attachments: screenshot-1.png
>
>
> - Refresh table button is really strange
> - there are some grey background around the sections
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23134) Improve UI of Deployment tab of Runtime Editor
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-23134:
----------------------------------------
{quote}Actions where users won’t affect the website are where you use a link. These are actions that take users from one page to another without changing anything on the website’s back or front-end. The user is basically a spectator browsing through content.{quote}
In that case, the action is clearly changing the [application] front-end, user is not browsing through content, he's intereacting with the front-end.
I invoke [~crobson]! Catherine, can you -or someone else from UX- please have a look at the screenshot and tell us whether the "Refresh" link is okay here or whether a button would be better?
> Improve UI of Deployment tab of Runtime Editor
> ----------------------------------------------
>
> Key: JBIDE-23134
> URL: https://issues.jboss.org/browse/JBIDE-23134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
> Attachments: screenshot-1.png
>
>
> - Refresh table button is really strange
> - there are some grey background around the sections
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-885) The condition 'TableHasRow' sometimes fails due to a disposed widget
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-885?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-885.
-----------------------------------
pushed to master
> The condition 'TableHasRow' sometimes fails due to a disposed widget
> --------------------------------------------------------------------
>
> Key: JBTIS-885
> URL: https://issues.jboss.org/browse/JBTIS-885
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE
> Affects Versions: 4.3.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.3.2.CR1
>
>
> {code}
> org.jboss.reddeer.core.exception.CoreLayerException: Exception during sync execution in UI thread
> at org.jboss.reddeer.core.util.Display.syncExec(Display.java:87)
> at org.jboss.reddeer.core.util.ObjectUtil.invokeMethodUI(ObjectUtil.java:60)
> at org.jboss.reddeer.core.util.ObjectUtil.invokeMethod(ObjectUtil.java:41)
> at org.jboss.reddeer.core.util.ObjectUtil.invokeMethod(ObjectUtil.java:23)
> at org.jboss.reddeer.core.handler.WidgetHandler.getText(WidgetHandler.java:167)
> at org.jboss.reddeer.swt.impl.table.AbstractTableItem.getText(AbstractTableItem.java:53)
> at org.jboss.tools.switchyard.reddeer.condition.TableHasRow.test(TableHasRow.java:27)
> at org.jboss.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:80)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:122)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:34)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:25)
> at org.jboss.tools.switchyard.reddeer.wizard.ServiceWizard.selectJavaInterface(ServiceWizard.java:70)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorTransformersTest.existingDozerJava2JavaFirstTest(SwitchYardEditorTransformersTest.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.reddeer.junit.internal.runner.statement.RunTestMethod.evaluate(RunTestMethod.java:36)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeTestExtensions.evaluate(RunIBeforeTestExtensions.java:63)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:51)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:58)
> at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:115)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.reddeer.core.exception.CoreLayerException: Exception when invoking method public java.lang.String org.eclipse.swt.widgets.TableItem.getText() by reflection
> at org.jboss.reddeer.core.util.ObjectUtil.invokeMethod(ObjectUtil.java:72)
> at org.jboss.reddeer.core.util.ObjectUtil.access$0(ObjectUtil.java:68)
> at org.jboss.reddeer.core.util.ObjectUtil$1.run(ObjectUtil.java:63)
> at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:160)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.jdt.internal.ui.dialogs.FilteredTypesSelectionDialog.open(FilteredTypesSelectionDialog.java:512)
> at org.switchyard.tools.ui.common.impl.JavaInterfaceControlAdapter.browse(JavaInterfaceControlAdapter.java:95)
> at org.switchyard.tools.ui.common.InterfaceControl.handleBrowse(InterfaceControl.java:488)
> at org.switchyard.tools.ui.common.InterfaceControl.access$4(InterfaceControl.java:487)
> at org.switchyard.tools.ui.common.InterfaceControl$6.widgetSelected(InterfaceControl.java:313)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1119)
> at org.jboss.reddeer.core.handler.WidgetHandler$5.run(WidgetHandler.java:382)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:194)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1)
> at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:160)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.switchyard.tools.ui.editor.diagram.shared.BaseTypeFactory.createType(BaseTypeFactory.java:37)
> at org.switchyard.tools.ui.editor.diagram.component.BaseComponentFactory.createType(BaseComponentFactory.java:37)
> at org.switchyard.tools.ui.editor.diagram.component.BaseComponentFactory.createType(BaseComponentFactory.java:1)
> at org.switchyard.tools.ui.editor.diagram.shared.CreateTypeFeature.create(CreateTypeFeature.java:94)
> at org.switchyard.tools.ui.editor.diagram.shared.CompositeCreateFeature.create(CompositeCreateFeature.java:67)
> at org.eclipse.graphiti.features.impl.AbstractCreateFeature.execute(AbstractCreateFeature.java:100)
> at org.eclipse.graphiti.internal.command.GenericFeatureCommandWithContext.execute(GenericFeatureCommandWithContext.java:64)
> at org.eclipse.graphiti.internal.command.GFPreparableCommand.doExecute(GFPreparableCommand.java:37)
> at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
> at org.eclipse.graphiti.ui.internal.editor.GFWorkspaceCommandStackImpl.execute(GFWorkspaceCommandStackImpl.java:128)
> at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
> at org.eclipse.graphiti.internal.command.CommandExec.executeCommand(CommandExec.java:85)
> at org.eclipse.graphiti.ui.internal.command.CreateModelObjectCommand.execute(CreateModelObjectCommand.java:49)
> at org.eclipse.graphiti.ui.internal.editor.EmfOnGefCommand.execute(EmfOnGefCommand.java:54)
> at org.eclipse.graphiti.internal.command.GFPreparableCommand2.doExecute(GFPreparableCommand2.java:43)
> at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
> at org.eclipse.emf.workspace.EMFCommandOperation.doExecute(EMFCommandOperation.java:119)
> at org.eclipse.emf.workspace.AbstractEMFOperation.execute(AbstractEMFOperation.java:150)
> at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:516)
> at org.eclipse.emf.workspace.impl.WorkspaceCommandStackImpl.doExecute(WorkspaceCommandStackImpl.java:208)
> at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
> at org.eclipse.graphiti.ui.internal.editor.GFWorkspaceCommandStackImpl.execute(GFWorkspaceCommandStackImpl.java:97)
> at org.eclipse.graphiti.ui.internal.editor.GFCommandStack.execute(GFCommandStack.java:138)
> at org.eclipse.gef.tools.AbstractTool.executeCommand(AbstractTool.java:425)
> at org.eclipse.gef.tools.AbstractTool.executeCurrentCommand(AbstractTool.java:438)
> at org.eclipse.gef.tools.CreationTool.performCreation(CreationTool.java:269)
> at org.eclipse.gef.tools.CreationTool.handleButtonUp(CreationTool.java:189)
> at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200)
> at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301)
> at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380)
> at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1119)
> at org.jboss.reddeer.core.handler.WidgetHandler$5.run(WidgetHandler.java:382)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:194)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1)
> at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:160)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.reddeer.core.util.ObjectUtil.invokeMethod(ObjectUtil.java:70)
> ... 100 more
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.SWT.error(SWT.java:4377)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:482)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:419)
> at org.eclipse.swt.widgets.TableItem.getText(TableItem.java:607)
> ... 104 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months