January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25549) Cannot create OpenShift connection with OC binary on path

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25549?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25549: ---------------------------------------- Assignee: Rob Stryker > Cannot create OpenShift connection with OC binary on path > --------------------------------------------------------- > > Key: JBIDE-25549 > URL: https://issues.jboss.org/browse/JBIDE-25549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Environment: FC27 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Attachments: image-2018-01-09-08-50-39-566.png, image-2018-01-09-08-53-21-234.png > > > I have OC Binary on path: > !image-2018-01-09-08-50-39-566.png|thumbnail! > But when I try to create OpenShift connection, wizard is showing an error message, that OC binary is not set: > !image-2018-01-09-08-53-21-234.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25550) Add progress bar for "Delete resource" wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25550?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25550: ------------------------------- Sprint: devex #143 January 2018 > Add progress bar for "Delete resource" wizard > --------------------------------------------- > > Key: JBIDE-25550 > URL: https://issues.jboss.org/browse/JBIDE-25550 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > > When you are using slower OpenShift instance (e.g. https://console.starter-us-east-2.openshift.com) it takes a few seconds (1-2) until the list is loaded, but you do not see if something is happening or not. Progress bar is needed to show info to user. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4637) Failing quickstart WildFly-11 [template]

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4637?page=com.atlassian.jira.plugin.... ] Josef Kopriva commented on JBDS-4637: ------------------------------------- I think this can be closed, as PR is closed, WDYT [~vprusa]? > Failing quickstart WildFly-11 [template] > ---------------------------------------- > > Key: JBDS-4637 > URL: https://issues.jboss.org/browse/JBDS-4637 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > WF11 > quickstartes 11.0.0.Final > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: pom.xml > > > Automation fails because of error after template project is imported. > Test report: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Solutions: > https://stackoverflow.com/questions/31835033/web-xml-is-missing-and-failo... > Updated pom.xml as attachment does no show errors after Project Maven -> Update project .. > Idk if right solution is to change pom or generate web.xml with "Java EE Tools -> Generate Deployment Descriptor Stub" in test. > Please comment recommendations [~n1hility] [~ctomc] [~trepel] [~sgilda] [~jkopriva] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-25553: ---------------------------------------- Summary: Cannot create Hibernate Console Configuration for projects with java 9 Key: JBIDE-25553 URL: https://issues.jboss.org/browse/JBIDE-25553 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.5.2.AM2 Reporter: Rastislav Wagner Priority: Critical -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4636) Failing tests for quickstart [spring-petclinic] on WildFly-11

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on JBDS-4636: ----------------------------------- Btw, for using releases of quickstarts, better zip to download is https://github.com/wildfly/quickstart/releases/download/11.0.0.Final/wild... this one is proper release, with all docs, bells and whistles. > Failing tests for quickstart [spring-petclinic] on WildFly-11 > ------------------------------------------------------------- > > Key: JBDS-4636 > URL: https://issues.jboss.org/browse/JBDS-4636 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: jdk=jdk1.8,label=fedora26 > jdk=jdk1.8,label=ubuntu1704 > jdk=openjdk-1.8,label=fedora26 > jdk=openjdk-1.8,label=win10 > Server: WF11 > Quickstarts: 11.x > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: spring-petclinic.errors.txt > > > There are JavaScript related errors in JBDS for which automation fails. > Related test reports: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Test results: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I think there may be some other configuration for JavaScript support necessary. > I was successful at deploying this quickstart. > Errors bothering me most are: > ')' expected intro.js /spring-petclinic/src/main/webapp/vendors/jquery/src line 20 > and > The element type "meta" must be terminated by the matching end-tag "</meta>". > I have added Spring IDE plugin to JBDS but I still get same errors. > Please comment [~n1hility] [~ctomc] [~trepel] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4642) JDK9 Certification

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Rastislav Wagner edited comment on JBDS-4642 at 1/10/18 7:14 AM: ----------------------------------------------------------------- To run your tests via maven you have to: 1. add maven-toolchain-plugin with following configuration {code} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-toolchains-plugin</artifactId> <version>1.0</version> <executions> <execution> <phase>validate</phase> <goals> <goal>toolchain</goal> </goals> </execution> </executions> <configuration> <toolchains> <jdk> <version>1.9</version> <vendor>oracle</vendor> </jdk> </toolchains> </configuration> </plugin> {code} 2. create toolchains.xml file inside .m2 folder {code} <?xml version="1.0" encoding="UTF8"?> <toolchains> <toolchain> <type>jdk</type> <provides> <version>1.9</version> <vendor>oracle</vendor> <id>CustomJRE</id> </provides> <configuration> <jdkHome>/usr/java/jdk-9.0.1/</jdkHome> </configuration> </toolchain> </toolchains> {code} 3.run tests with mvn clean verify -PITests,download-devstudio,jdk9 Your default java has to be java8 (will be used for building the plugins/tests) and java 9 will be used to run the tests was (Author: rawagner): To run you tests via maven you have to: 1. add maven-toolchain-plugin with following configuration {code} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-toolchains-plugin</artifactId> <version>1.0</version> <executions> <execution> <phase>validate</phase> <goals> <goal>toolchain</goal> </goals> </execution> </executions> <configuration> <toolchains> <jdk> <version>1.9</version> <vendor>oracle</vendor> </jdk> </toolchains> </configuration> </plugin> {code} 2. create toolchains.xml file inside .m2 folder {code} <?xml version="1.0" encoding="UTF8"?> <toolchains> <toolchain> <type>jdk</type> <provides> <version>1.9</version> <vendor>oracle</vendor> <id>CustomJRE</id> </provides> <configuration> <jdkHome>/usr/java/jdk-9.0.1/</jdkHome> </configuration> </toolchain> </toolchains> {code} 3.run tests with mvn clean verify -PITests,download-devstudio,jdk9 Your default java has to be java8 (will be used for building the plugins/tests) and java 9 will be used to run the tests > JDK9 Certification > ------------------ > > Key: JBDS-4642 > URL: https://issues.jboss.org/browse/JBDS-4642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Reporter: Pavol Srna > > This is an epic for tracking JDK9 Devstudio Certification. > All components need to be retested (run) with JDK9. Please link issues found here. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25066) cdi itests job is failing

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25066?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25066. -------------------------------- > cdi itests job is failing > ------------------------- > > Key: JBIDE-25066 > URL: https://issues.jboss.org/browse/JBIDE-25066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, integration-tests > Reporter: Pavol Srna > Assignee: Lukáš Valach > Fix For: 4.5.2.AM3 > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25514) Build to not allow goal dependency:tree

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25514?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25514. -------------------------------- All PRs have been merged and "mvn dependency:tree" works fine. I think we can close this jira. > Build to not allow goal dependency:tree > --------------------------------------- > > Key: JBIDE-25514 > URL: https://issues.jboss.org/browse/JBIDE-25514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: build, maven, tycho > Fix For: 4.5.2.AM3 > > Attachments: tree.log > > > When we run dependency:tree error is reported probably due to incompatibility between the Maven Dependency plugin and Tycho. Upgrading to Maven Dependency plugin 3.0.2 fixed the issue -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25507) Move RHAMT tooling out of early access

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25507?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25507. -------------------------------- Verified in both JBT and DevStudio, RHAMT 4.0.0.Final is out of early access. Closing. > Move RHAMT tooling out of early access > -------------------------------------- > > Key: JBIDE-25507 > URL: https://issues.jboss.org/browse/JBIDE-25507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: John Steele > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > Attachments: install-devstudio-central.png, install-jbt-central.png, rhamt-no-ea.png > > > RHAMT 4.0.0.Final will be released December 15th, and now that it's GA, we'd like it be out of early access. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25551) Format Checker: dont enforce line feed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25551?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25551: ------------------------------------------ [~dbocharov] I would have thought that telling the formatter *NOT* to join wrapped lines, which makes eclipse respect manual line wrapping, would help: {code:title=eclipse-formatter.xml} -<setting id="org.eclipse.jdt.core.formatter.join_wrapped_lines" value="true"/> +<setting id="org.eclipse.jdt.core.formatter.join_wrapped_lines" value="false"/> {code} But it doesn't. Any idea? > Format Checker: dont enforce line feed > --------------------------------------- > > Key: JBIDE-25551 > URL: https://issues.jboss.org/browse/JBIDE-25551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > > Current format checks enforce line feeds which leads to badly readable code when you're using fluent builders like in the following case (see here: https://github.com/jbosstools/jbosstools-openshift/pull/1645/files?diff=u...): > {code:title=enforced line feeds} > TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer) > .column(resource -> ((IResource) resource).getName()).name("Name").align(SWT.LEFT).weight(1) > .minWidth(100).buildColumn().column(resource -> ((IResource) resource).getKind()).name("Type") > .align(SWT.LEFT).weight(1).minWidth(100).buildColumn() > .column(new LabelsCellLabelProvider(labelFilter)).name("Labels").align(SWT.LEFT).weight(2) > .minWidth(200).buildColumn().buildViewer(); > {code} > {code:title=manual line feeds with superior readability} > TableViewer resourcesViewer = new TableViewerBuilder(table, tableContainer) > .column(resource -> ((IResource) resource).getName()) > .name("Name").align(SWT.LEFT).weight(1).minWidth(100).buildColumn() > .column(resource -> ((IResource) resource).getKind()) > .name("Type").align(SWT.LEFT).weight(1).minWidth(100).buildColumn() > .column(new LabelsCellLabelProvider(labelFilter)) > .name("Labels").align(SWT.LEFT).weight(2).minWidth(200).buildColumn() > .buildViewer(); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 January 2018