June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18871) Promote JBoss Tools CAT in JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18871?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18871: ---------------------------------------- [~fbricon] It seems to me that this can be marked as resolved in Beta1. If you agree, can you please update the bug details accordingly and mark it as resolved? > Promote JBoss Tools CAT in JBoss Central > ---------------------------------------- > > Key: JBIDE-18871 > URL: https://issues.jboss.org/browse/JBIDE-18871 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.2.0.Final > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Fix For: 4.3.x > > > It would be nice to put basic information about JBT CAT to JBoss Central to attract users to join JBT CAT. > Should be applied to JBT and JBDS -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3453) Launch after installation results in 'not responding' when running the installer on Java 7

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3453?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3453: ------------------------------ Attachment: .log I attached the log file, but there seems to be not much in it. > Launch after installation results in 'not responding' when running the installer on Java 7 > ------------------------------------------------------------------------------------------ > > Key: JBDS-3453 > URL: https://issues.jboss.org/browse/JBDS-3453 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Environment: Fedora 20, 64-bit > installer run with OpenJDK 1.7.0_79 > devstudio run with OpenJDK 1.8.0_45 > Reporter: Jan Richter > Attachments: .log > > > When I try to launch JBDS from the installer, which I run with Java 7, after choosing a workspace (using a clean workspace btw.) the 'loading' splash disappears shortly after it shows up (and the progress bar is still somewhere around the beginning). > Then a blank JBDS window appears and about 10 - 20 seconds later a 'Not Responding' dialog appears followed by the rest of JBDS right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Ma Deshuai edited comment on JBIDE-19947 at 6/8/15 10:06 PM: ------------------------------------------------------------- When I change to a new env with jdk1.8 it works.It's just an issue about update when user use jdk1.7. was (Author: deshuai): When I change to a new env with jdk1.8 it works. > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Attachments: error1.jpg, error2.jpg, error3.jpg, JDK7-warning.png > > > Description of problem: > After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/mars/. Can't open openshift v3 plug in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > Jdk: 1.7 > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/mars/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Ma Deshuai commented on JBIDE-19947: ------------------------------------ When I change to a new env with jdk1.8 it works. > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Attachments: error1.jpg, error2.jpg, error3.jpg, JDK7-warning.png > > > Description of problem: > After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/mars/. Can't open openshift v3 plug in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > Jdk: 1.7 > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/mars/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19983) Fix ContentScanner.nextToken() logic to avoid use exception for flow control

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-19983: ------------------------------------- Summary: Fix ContentScanner.nextToken() logic to avoid use exception for flow control Key: JBIDE-19983 URL: https://issues.jboss.org/browse/JBIDE-19983 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: freemarker Affects Versions: 4.3.0.Beta1 Reporter: Denis Golovin Priority: Minor Currently ContentScanner.nextToken() tests chars without detecting EOF first. It tiggers BadLocationException and catch block then decide what to do next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19983) Fix ContentScanner.nextToken() logic to avoid use exception for flow control

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19983?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19983: ---------------------------------- Fix Version/s: 4.3.0.Beta2 > Fix ContentScanner.nextToken() logic to avoid use exception for flow control > ---------------------------------------------------------------------------- > > Key: JBIDE-19983 > URL: https://issues.jboss.org/browse/JBIDE-19983 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.3.0.Beta1 > Reporter: Denis Golovin > Priority: Minor > Fix For: 4.3.0.Beta2 > > > Currently ContentScanner.nextToken() tests chars without detecting EOF first. It tiggers BadLocationException and catch block then decide what to do next. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19982) Wildfly doesn't pick up batchlet classes in debug mode

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19982?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-19982. ------------------------------------ Assignee: Alexey Kazakov Fix Version/s: 4.3.0.Beta1 Resolution: Rejected I'm rejecting the issue then. > Wildfly doesn't pick up batchlet classes in debug mode > ------------------------------------------------------ > > Key: JBIDE-19982 > URL: https://issues.jboss.org/browse/JBIDE-19982 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, server > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > It seems that wildfly 8.2. (or JBT server adapter?) doesn't support hot deployment for batch application. > See steps to reproduce. > If I change job.xml then it works fine. But if I add some new classes which are referenced from the job xml file then it doesn't it. > I see both the modified jbo xml files and new class file in wildfly-8.2.0.Final/standalone/deployments/jboss-batch-processing.war folder but server restarting is still required. > This is probably an upstream issue but we need to investigate this case and maybe document it somehow if this is an expecting behavior. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19982) Wildfly doesn't pick up batchlet classes in debug mode

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19982?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19982: ---------------------------------------- Yes, restrating the module works too. Didn't try it before ;( > Wildfly doesn't pick up batchlet classes in debug mode > ------------------------------------------------------ > > Key: JBIDE-19982 > URL: https://issues.jboss.org/browse/JBIDE-19982 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, server > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > > It seems that wildfly 8.2. (or JBT server adapter?) doesn't support hot deployment for batch application. > See steps to reproduce. > If I change job.xml then it works fine. But if I add some new classes which are referenced from the job xml file then it doesn't it. > I see both the modified jbo xml files and new class file in wildfly-8.2.0.Final/standalone/deployments/jboss-batch-processing.war folder but server restarting is still required. > This is probably an upstream issue but we need to investigate this case and maybe document it somehow if this is an expecting behavior. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3427) Filter installed graphical files per OS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3427?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3427: -------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015 (was: Sprint #3 May 2015) > Filter installed graphical files per OS > --------------------------------------- > > Key: JBDS-3427 > URL: https://issues.jboss.org/browse/JBDS-3427 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: respin-a > Fix For: 9.0.0.Beta1 > > > Installer should not copy .ico files on Mac and Linux, also some .png files installed on every supported OS are never used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3427) Filter installed graphical files per OS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3427?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3427: -------------------------------- Labels: respin-a (was: ) > Filter installed graphical files per OS > --------------------------------------- > > Key: JBDS-3427 > URL: https://issues.jboss.org/browse/JBDS-3427 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: respin-a > Fix For: 9.0.0.Beta1 > > > Installer should not copy .ico files on Mac and Linux, also some .png files installed on every supported OS are never used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015