February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-67) Bump JSDT feature/plugin versions to 2.0 [EBZ#485699]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-67?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny resolved ERT-67. -------------------------------- Resolution: Done > Bump JSDT feature/plugin versions to 2.0 [EBZ#485699] > ----------------------------------------------------- > > Key: ERT-67 > URL: https://issues.jboss.org/browse/ERT-67 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > We have several new features and breaking changes coming to JSDT that affects UI, core and debugger. The plugin and feature versions should be updated to 2.0 to accommodate the adoption of these changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21768) NPE in Job when calling a RefreshAction

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21768?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-21768: ----------------------------------------- thanks for having integrated my PR quickly :-) > NPE in Job when calling a RefreshAction > --------------------------------------- > > Key: JBIDE-21768 > URL: https://issues.jboss.org/browse/JBIDE-21768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Final > Reporter: Aurélien Pupier > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2016-02-25 14:14:55.363 > !MESSAGE An internal error occurred during: "Refreshing JMX Connection". > !STACK 0 > java.lang.NullPointerException > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:71) > {noformat} > based on Job.run javadoc: "Returns:resulting status of the run. The result must not be null" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21768) NPE in Job when calling a RefreshAction

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21768?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21768: ----------------------------------- Assignee: Fred Bricon (was: Rob Stryker) Resolution: Done PR applied in master and 4.3.x branch. Thanks for the patch [~aurelien.pupier]! > NPE in Job when calling a RefreshAction > --------------------------------------- > > Key: JBIDE-21768 > URL: https://issues.jboss.org/browse/JBIDE-21768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Final > Reporter: Aurélien Pupier > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2016-02-25 14:14:55.363 > !MESSAGE An internal error occurred during: "Refreshing JMX Connection". > !STACK 0 > java.lang.NullPointerException > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:71) > {noformat} > based on Job.run javadoc: "Returns:resulting status of the run. The result must not be null" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21770) OpenShift 2 connection loading message is archaic

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21770?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21770: ----------------------------------- Fix Version/s: 4.3.1.CR1 Assignee: Marián Labuda Resolution: Done PR applied in 4.3.x and master. Thanks for your contribution [~mlabuda]! > OpenShift 2 connection loading message is archaic > ------------------------------------------------- > > Key: JBIDE-21770 > URL: https://issues.jboss.org/browse/JBIDE-21770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Minor > Labels: openshift_v2 > Fix For: 4.3.1.CR1 > > Attachments: progress_dialog.png > > > When loading OS2 connection there is sometimes progress dialog informing about loading of connection details. It has deprecated "ExpressConnection" message, probably it remained from times when there was OpenShift Express. > !progress_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21771) Simplest java project is imported sometimes as JDT, sometimes not.

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21771?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21771: ---------------------------------------- Just to sort out the priority, is the project usable in workspace in any case or does the difference of behavior have an impact on usabillity? > Simplest java project is imported sometimes as JDT, sometimes not. > ------------------------------------------------------------------ > > Key: JBIDE-21771 > URL: https://issues.jboss.org/browse/JBIDE-21771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Attachments: PlainJavaProject > > > Importing simplest java project (in attachment) gets sometimes imported as "Java, JDT" and sometimes only as "Java". I am not able to provide exact steps to reproduce, as it seems to do that randomly. > Looking at http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles/org.eclips..., project should be detected as JDT, in case ".classpath" is found in the project. Couldn't be the issue the order of executing configurators? Like when Java configurator is called first, it creates .classpath and then JDT configurator is called and it sees the .classpath file. When the order is opposite, JDT is not configured, because .classpath is not there yet? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21771) Simplest java project is imported sometimes as JDT, sometimes not.

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-21771: ---------------------------------- Summary: Simplest java project is imported sometimes as JDT, sometimes not. Key: JBIDE-21771 URL: https://issues.jboss.org/browse/JBIDE-21771 Project: Tools (JBoss Tools) Issue Type: Bug Components: easymport Affects Versions: 4.3.1.CR1 Reporter: Radim Hopp Attachments: PlainJavaProject Importing simplest java project (in attachment) gets sometimes imported as "Java, JDT" and sometimes only as "Java". I am not able to provide exact steps to reproduce, as it seems to do that randomly. Looking at http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles/org.eclips..., project should be detected as JDT, in case ".classpath" is found in the project. Couldn't be the issue the order of executing configurators? Like when Java configurator is called first, it creates .classpath and then JDT configurator is called and it sees the .classpath file. When the order is opposite, JDT is not configured, because .classpath is not there yet? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-563) Update BPMN2 Modeler to 1.2.3.Final

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-563: -------------------------------- Summary: Update BPMN2 Modeler to 1.2.3.Final Key: JBTIS-563 URL: https://issues.jboss.org/browse/JBTIS-563 Project: JBoss Tools Integration Stack Issue Type: Task Reporter: Paul Leacu Assignee: Paul Leacu -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-19910. ------------------------------- Verified, closing. > Add w3 schemes to XML catalog > ----------------------------- > > Key: JBIDE-19910 > URL: https://issues.jboss.org/browse/JBIDE-19910 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > We should add w3 schemes which are used in our quickstarts/examples to XML catalog because: > 1) w3 servers are intentionally slow > 2) it seems that wsdl validator does no caching of previously downloaded schemes > I will take a look at examples and list schemes here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3615) virtual box cannot be installed reliably on windows

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-3615: ----------------------------------------- Summary: virtual box cannot be installed reliably on windows Key: JBDS-3615 URL: https://issues.jboss.org/browse/JBDS-3615 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Reporter: Max Rydahl Andersen Priority: Blocker look at docker-toolbox what they do that is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3614) Developer Suite installer

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-3614: ----------------------------------------- Summary: Developer Suite installer Key: JBDS-3614 URL: https://issues.jboss.org/browse/JBDS-3614 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Components: installer Reporter: Max Rydahl Andersen Priority: Blocker Make installer that has: VirtualBox Vagrant Cygwin CDK (custom VagrantFile?) (docker client?) OpenJDK Red Hat Developer Studio 9.1 (with or without JBoss EAP ? - EAP 7 not available) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016