January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-590) Move aCute to latest OmniSharp-roslyn

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-590?page=com.atlassian.jira.plugin.sy... ] Mickael Istria updated ERT-590: ------------------------------- Sprint: devex #143 January 2018 > Move aCute to latest OmniSharp-roslyn > ------------------------------------- > > Key: ERT-590 > URL: https://issues.jboss.org/browse/ERT-590 > Project: Eclipse Release Train > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-590) Move aCute to latest OmniSharp-roslyn

by Mickael Istria (JIRA)

Mickael Istria created ERT-590: ---------------------------------- Summary: Move aCute to latest OmniSharp-roslyn Key: ERT-590 URL: https://issues.jboss.org/browse/ERT-590 Project: Eclipse Release Train Issue Type: Enhancement Reporter: Mickael Istria Assignee: Mickael Istria -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-542) Adoption of debug protocol

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-542?page=com.atlassian.jira.plugin.sy... ] Mickael Istria resolved ERT-542. -------------------------------- Resolution: Done Integration of exteranal patch was completed. Some examples are working. I initially had support for C# developer in the scope of a demo, but some legal issue make it impossible to have it working soon enough. So marking as resolved as the current state already delivers expected value. Some maintenance may be necessary in the future, when we start building upon the debug adapter protocol for aCute or RedOx, > Adoption of debug protocol > -------------------------- > > Key: ERT-542 > URL: https://issues.jboss.org/browse/ERT-542 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Platform > Reporter: Mickael Istria > Assignee: Mickael Istria > > Keep in touch with progress in LSP4J about Debug Protocol and start adoption as soon as possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-540) Parallel builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-540?page=com.atlassian.jira.plugin.sy... ] Mickael Istria updated ERT-540: ------------------------------- Sprint: devex #142 December 2017, devex #143 January 2018 (was: devex #142 December 2017) > Parallel builds > --------------- > > Key: ERT-540 > URL: https://issues.jboss.org/browse/ERT-540 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Platform > Reporter: Mickael Istria > Assignee: Mickael Istria > > Allow Eclipse Platform's Build Manager to build multiple projects in parallel, especially in case of auto-build -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-541) Enable CodeLens in Eclipse IDE

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-541?page=com.atlassian.jira.plugin.sy... ] Mickael Istria resolved ERT-541. -------------------------------- Resolution: Done I think this one can be marked as resolved as the value is shipped. There are still some ongoing maintenance effort going on but the would rather be tracked in dedicated tasks. > Enable CodeLens in Eclipse IDE > ------------------------------ > > Key: ERT-541 > URL: https://issues.jboss.org/browse/ERT-541 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Platform > Reporter: Mickael Istria > Assignee: Mickael Istria > > Be a facilitator in inclusion of Angelo's efforts regarding CodeLens in the various parts of Eclipse IDE. -- 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 3:59 AM: ----------------------------------------------------------------- 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 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] (JBDS-4642) JDK9 Certification

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Rastislav Wagner commented on JBDS-4642: ---------------------------------------- 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] (JBDS-4642) JDK9 Certification

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-4642: ----------------------------- Description: This is an epic for tracking JDK9 Devstudio Certification. All components need to be retested (run) with JDK9. Please link issues found here. was: This is an epic for tracking JDK9 Devstudio Certification. All components need to be retested with JDK9. Please link issues found here. > 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-25260) Console view is broken after entering subscription username

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25260?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25260: --------------------------------------- [~rob.stryker] Indeed. I believe that this was resolved in upstream with https://github.com/minishift/minishift/pull/1851. Just to have all together here. Should be in latest cdk, will verify. > Console view is broken after entering subscription username > ----------------------------------------------------------- > > Key: JBIDE-25260 > URL: https://issues.jboss.org/browse/JBIDE-25260 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.5.1.Final > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.5.2.AM3 > > Attachments: image-2017-10-17-10-38-53-270.png, with_devstudio_11.0.0.GA-0.PNG, with_devstudio_11.0.0.GA-1.PNG > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25349) Renaming of existing CDK server adapter is not applied everywhere

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25349?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25349: --------------------------------------- [~rob.stryker] great, thanks! > Renaming of existing CDK server adapter is not applied everywhere > ----------------------------------------------------------------- > > Key: JBIDE-25349 > URL: https://issues.jboss.org/browse/JBIDE-25349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.2.AM3 > > -- 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