June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24543) Get rid of AbstractCreateApplicationTest

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-24543: ---------------------------------- Summary: Get rid of AbstractCreateApplicationTest Key: JBIDE-24543 URL: https://issues.jboss.org/browse/JBIDE-24543 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, openshift Affects Versions: 4.5.0.AM1 Reporter: Radim Hopp Assignee: Radim Hopp Functionality of AbstractCreateApplicationTest should be implemented by requirements using openshift API isntead of UI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24222: ------------------------------- Sprint: devex #130 April 2017, devex #133 Jun 2017 (was: devex #130 April 2017, devex #132 May 2017) > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-836) Update the logic for adding a new component according to FUSETOOLS-1976

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-836?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík resolved JBTIS-836. -------------------------------- Resolution: Out of Date the logic has been updated > Update the logic for adding a new component according to FUSETOOLS-1976 > ----------------------------------------------------------------------- > > Key: JBTIS-836 > URL: https://issues.jboss.org/browse/JBTIS-836 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > > Update the logic for adding a new component according to FUSETOOLS-1976. Now, we can just click on the component we want connect to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-836) Update the logic for adding a new component according to FUSETOOLS-1976

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-836?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-836. ------------------------------ > Update the logic for adding a new component according to FUSETOOLS-1976 > ----------------------------------------------------------------------- > > Key: JBTIS-836 > URL: https://issues.jboss.org/browse/JBTIS-836 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > > Update the logic for adding a new component according to FUSETOOLS-1976. Now, we can just click on the component we want connect to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4417) Bundle org.eclipse.wst.jsdt.nashorn.extension not found

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBDS-4417?page=com.atlassian.jira.plugin.... ] Victor Rubezhny commented on JBDS-4417: --------------------------------------- [~ibuziuk] Absolutely. We don't need to have the following option in devstudio.ini anymore: {code} -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension {code} This was only the requirement for Neon.x stream, starting from Oxygen (WTP 3.9.x) we've switched to use Closure Compiler bundled in Orbit (for WTP 3.9.0 RC1-RC3 we use orbit-buildrepo-S20170516192513 as the prerequisite). > Bundle org.eclipse.wst.jsdt.nashorn.extension not found > ------------------------------------------------------- > > Key: JBDS-4417 > URL: https://issues.jboss.org/browse/JBDS-4417 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM1 > Environment: Devstudio installed form devstudio-11.0.0.AM1-v20170531-1042-B189-installer-standalone.jar > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Fix For: 11.0.0.AM1 > > > I have this error message in eclipse log: > {code} > !SESSION Wed May 31 14:13:11 CEST 2017 ----------------------------------------- > !ENTRY org.eclipse.equinox.launcher 4 0 2017-05-31 14:13:11.062 > !MESSAGE Could not find extension: org.eclipse.wst.jsdt.nashorn.extension > !SESSION 2017-05-31 14:13:11.038 ----------------------------------------------- > eclipse.buildId=11.0.0.AM1-v20170531-1042-B189 > java.version=1.8.0_131 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > !ENTRY org.eclipse.osgi 4 0 2017-05-31 14:13:11.805 > !MESSAGE Bundle org.eclipse.wst.jsdt.nashorn.extension not found. > {code} > I see that plugin org.eclipse.wst.jsdt.nashorn.extension isn't installed in .../Devstudio/studio/plugins/ folder. > Possibly we have to remove this line from devstudio.ini? > {code} > -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23489: --------------------------------- Story Points: 15 > Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm > ------------------------------------------------------------------------------ > > Key: JBIDE-23489 > URL: https://issues.jboss.org/browse/JBIDE-23489 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests, qa > Affects Versions: 4.4.2.AM3 > Reporter: Pavol Srna > Assignee: Lukáš Valach > Fix For: 4.5.0.AM1 > > Attachments: FreeMarket_rhscl_enabled.log, Freemarker_testRuntime_p2Installed.log > > > We need to find a way how to run automated tests agains devstudio rpm. > I've tried the following paths: > 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/ > 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 > But none of the above works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM (headless)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23882: --------------------------------- Summary: Automate test of installation of software from Red Hat Central into devstudio RPM (headless) (was: Automate test of installation of software from Red Hat Central into devstudio RPM) > Automate test of installation of software from Red Hat Central into devstudio RPM (headless) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.0.AM2 > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24542) All installer/Central test should be started weekly

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24542: ------------------------------------ Summary: All installer/Central test should be started weekly Key: JBIDE-24542 URL: https://issues.jboss.org/browse/JBIDE-24542 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, qa Affects Versions: 4.5.0.AM1 Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.5.0.AM1 There are some tests which have to be started manually because they require path to installer package which varies for each build. We should find the way how to start these tests automatically. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24539: ------------------------------------- Sprint: (was: RHDEVDOCS Sprint 133, > Jun 28) > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM1 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24539: ------------------------------------- Sprint: RHDEVDOCS Sprint 133, > Jun 28 > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM1 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017