August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22802) Change test project from eclipse plugin to maven projec

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22802?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22802. --------------------------------- > Change test project from eclipse plugin to maven projec > ------------------------------------------------------- > > Key: JBIDE-22802 > URL: https://issues.jboss.org/browse/JBIDE-22802 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.4.1.Final > > > Former test project was an eclipse plugin and with changes made in this sprint it had became faulty. Convert project into maven project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22979) Freemarker New and Noteworthy for 4.4.1.AM3

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22979?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22979. --------------------------------- Jira in query is documented on http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.1.AM3.html, closing. > Freemarker New and Noteworthy for 4.4.1.AM3 > ------------------------------------------- > > Key: JBIDE-22979 > URL: https://issues.jboss.org/browse/JBIDE-22979 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22765) In FTL file in editor are missing directives in code assistant

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22765?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-22765: ------------------------------------- Assignee: Alexey Kazakov > In FTL file in editor are missing directives in code assistant > -------------------------------------------------------------- > > Key: JBIDE-22765 > URL: https://issues.jboss.org/browse/JBIDE-22765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160715-2233-B5663 > Build date: 20160715-2233 > Reporter: Ondrej Dockal > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.Final > > > In .ftl file when using <# and opening code assistant, there are missing directives: compress, nt and setting. I checked http://freemarker.org/docs/ref_directive_alphaidx.html for supported directives but did not find any reason we are missing those mentioned above. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-843) SwitchYard Tests sometimes fail due to unability to find CTab

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-843?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-843: ------------------------------------ Description: Sometimes the CTab cannot be activated due to SWITCHYARD-2907 {code} org.jboss.reddeer.swt.exception.SWTLayerException: No matching widget found at org.jboss.reddeer.swt.wait.AbstractWait.timeoutExceeded(AbstractWait.java:157) at org.jboss.reddeer.swt.wait.AbstractWait.wait(AbstractWait.java:110) at org.jboss.reddeer.swt.wait.AbstractWait.(AbstractWait.java:75) at org.jboss.reddeer.swt.wait.AbstractWait.(AbstractWait.java:51) at org.jboss.reddeer.swt.wait.AbstractWait.(AbstractWait.java:39) at org.jboss.reddeer.swt.wait.WaitUntil.(WaitUntil.java:23) at org.jboss.reddeer.swt.lookup.WidgetLookup.activeWidget(WidgetLookup.java:71) at org.jboss.reddeer.swt.widgets.AbstractWidget.(AbstractWidget.java:30) at org.jboss.reddeer.swt.impl.ctab.AbstractCTabItem.(AbstractCTabItem.java:28) at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.(DefaultCTabItem.java:79) at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.(DefaultCTabItem.java:44) at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.(DefaultCTabItem.java:35) at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.activateDesignTab(SwitchYardEditor.java:79) at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.(SwitchYardEditor.java:73) at org.jboss.tools.switchyard.reddeer.project.SwitchYardProject.openSwitchYardFile(SwitchYardProject.java:46) at org.jboss.tools.switchyard.ui.bot.test.ValidatorsTest.openSwitchYardFile(ValidatorsTest.java:63) {code} or {code} org.jboss.reddeer.core.exception.CoreLayerException: No matching widget found with Matcher matching when all matchers match: [Matcher matching widgets with text that without mnenomic matches: is "Domain", Matcher matching widget with the same type as or type extending class org.eclipse.swt.custom.CTabItem] class org.eclipse.swt.widgets.Shell at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173) at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126) 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.WaitUntil.<init>(WaitUntil.java:37) at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:77) at org.jboss.reddeer.swt.widgets.AbstractWidget.<init>(AbstractWidget.java:31) at org.jboss.reddeer.swt.impl.ctab.AbstractCTabItem.<init>(AbstractCTabItem.java:28) at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.<init>(DefaultCTabItem.java:87) at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.<init>(DefaultCTabItem.java:47) at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.<init>(DefaultCTabItem.java:37) at org.jboss.tools.switchyard.reddeer.editor.DomainEditor.activateDomainTab(DomainEditor.java:45) at org.jboss.tools.switchyard.reddeer.editor.DomainEditor.<init>(DomainEditor.java:40) at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorDomainSettingsTest.securityConfigurationTest(SwitchYardEditorDomainSettingsTest.java:145) {code} was:Sometimes the CTab cannot be activated due to SWITCHYARD-2907 > SwitchYard Tests sometimes fail due to unability to find CTab > ------------------------------------------------------------- > > Key: JBTIS-843 > URL: https://issues.jboss.org/browse/JBTIS-843 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, switchyard > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > Sometimes the CTab cannot be activated due to SWITCHYARD-2907 > {code} > org.jboss.reddeer.swt.exception.SWTLayerException: No matching widget found > at org.jboss.reddeer.swt.wait.AbstractWait.timeoutExceeded(AbstractWait.java:157) > at org.jboss.reddeer.swt.wait.AbstractWait.wait(AbstractWait.java:110) > at org.jboss.reddeer.swt.wait.AbstractWait.(AbstractWait.java:75) > at org.jboss.reddeer.swt.wait.AbstractWait.(AbstractWait.java:51) > at org.jboss.reddeer.swt.wait.AbstractWait.(AbstractWait.java:39) > at org.jboss.reddeer.swt.wait.WaitUntil.(WaitUntil.java:23) > at org.jboss.reddeer.swt.lookup.WidgetLookup.activeWidget(WidgetLookup.java:71) > at org.jboss.reddeer.swt.widgets.AbstractWidget.(AbstractWidget.java:30) > at org.jboss.reddeer.swt.impl.ctab.AbstractCTabItem.(AbstractCTabItem.java:28) > at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.(DefaultCTabItem.java:79) > at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.(DefaultCTabItem.java:44) > at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.(DefaultCTabItem.java:35) > at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.activateDesignTab(SwitchYardEditor.java:79) > at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.(SwitchYardEditor.java:73) > at org.jboss.tools.switchyard.reddeer.project.SwitchYardProject.openSwitchYardFile(SwitchYardProject.java:46) > at org.jboss.tools.switchyard.ui.bot.test.ValidatorsTest.openSwitchYardFile(ValidatorsTest.java:63) > {code} > or > {code} > org.jboss.reddeer.core.exception.CoreLayerException: No matching widget found with Matcher matching when all matchers match: [Matcher matching widgets with text that without mnenomic matches: is "Domain", Matcher matching widget with the same type as or type extending class org.eclipse.swt.custom.CTabItem] > class org.eclipse.swt.widgets.Shell > at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173) > at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126) > 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.WaitUntil.<init>(WaitUntil.java:37) > at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:77) > at org.jboss.reddeer.swt.widgets.AbstractWidget.<init>(AbstractWidget.java:31) > at org.jboss.reddeer.swt.impl.ctab.AbstractCTabItem.<init>(AbstractCTabItem.java:28) > at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.<init>(DefaultCTabItem.java:87) > at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.<init>(DefaultCTabItem.java:47) > at org.jboss.reddeer.swt.impl.ctab.DefaultCTabItem.<init>(DefaultCTabItem.java:37) > at org.jboss.tools.switchyard.reddeer.editor.DomainEditor.activateDomainTab(DomainEditor.java:45) > at org.jboss.tools.switchyard.reddeer.editor.DomainEditor.<init>(DomainEditor.java:40) > at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorDomainSettingsTest.securityConfigurationTest(SwitchYardEditorDomainSettingsTest.java:145) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-843) SwitchYard Tests sometimes fail due to unability to find CTab

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-843: --------------------------------------- Summary: SwitchYard Tests sometimes fail due to unability to find CTab Key: JBTIS-843 URL: https://issues.jboss.org/browse/JBTIS-843 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, switchyard Affects Versions: 4.3.1.Final Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Sometimes the CTab cannot be activated due to SWITCHYARD-2907 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3959) DevSuite Uninstaller for Windows (powershell script)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3959?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3959: -------------------------------- Summary: DevSuite Uninstaller for Windows (powershell script) (was: DevSuite Uninstaller for Windows) > DevSuite Uninstaller for Windows (powershell script) > ---------------------------------------------------- > > Key: JBDS-3959 > URL: https://issues.jboss.org/browse/JBDS-3959 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > DevSuite should provide uninstaller that would remove what was installed by installer and skip what was detected during installation. > Uninstaller script is located uninstaller/uninstall.ps1 after installation. > Before running the script make sure vagrant vm is destroyed with > {code}vagrant destroy{code} > To run uninstaller start windows command processor or powershell and issue > {code}powershell -ExecutionPolicy bypass -File c:\${targetInstallFolder}\unistaller\uninstall.ps1 -Verb runas{code} > Uninstaller script output would look like example below: > {code}C:\Users\eskimo>powershell -ExecutionPolicy bypass -File c:\${targetInstallFolder}\unistaller\uninstall.ps1 > Uninstalling Development Suite > Removing VirtualBox > DONE > Removing Vagrant > DONE > Removing VirtualBox > DONE > Removing installation folder > DONE > Removing path entries > DONE > Press any key to exit: > C:\Users\eskimo>{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19911: ---------------------------------------- I'd split C into multiple steps: C1. Update TP C1a. Sed to change repository urls C1b. Use the fix-version mojo to fix version C2. Prepare commit locally C3. Push commit C4. Create PR C5. Validate PR Step C5 (verification of TP) automatically happens whenever a TP is published ( JBIDE-22312 ). I don't have credentials for rhdevelopers-ci profile and I'm not aware of an existing OAuth token we can reuse, but we can ask [~ppitonak] who IIRC manages this account: Is it possible to get a clone of jbosstools/jbosstools-target-platform repository and some tokens to push content/create PRs with it? > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Fix For: 4.4.x > > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage

by Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ] Alexander Kurtakov commented on JBDS-4014: ------------------------------------------ Can someone point me to the usage plugin sources location so I can get details of what we speak about? > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBDS-4014 > URL: https://issues.jboss.org/browse/JBDS-4014 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 10.2.0.AM1 > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4015) Only one MSI installer can be running at the same time

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4015?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4015: -------------------------------- Fix Version/s: 10.1.0.GA Steps to Reproduce: # Install cygwin only # restart installer # install Vagrant and Virtual box only # See one of them failed to install > Only one MSI installer can be running at the same time > ------------------------------------------------------ > > Key: JBDS-4015 > URL: https://issues.jboss.org/browse/JBDS-4015 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 64-bit > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.1.0.GA > > > Currently with cygwin detection and OpenJDK component uses MSI installer there is running two msi installers at the same time. If that happens only one that starts first succeed all other fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4015) Only one MSI installer can be running at the same time

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4015?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4015: ----------------------------- > Only one MSI installer can be running at the same time > ------------------------------------------------------ > > Key: JBDS-4015 > URL: https://issues.jboss.org/browse/JBDS-4015 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 64-bit > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.1.0.GA > > > Currently with cygwin detection and OpenJDK component uses MSI installer there is running two msi installers at the same time. If that happens only one that starts first succeed all other fails. -- 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