September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2733: ----------------------------- CDW pm_ack: ? (was: +) > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, Requirements > Reporter: Burr Sutter > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2733: -------------------------------------- Component/s: Requirements > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, Requirements > Reporter: Burr Sutter > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15436) Bump Webservices to version 1.5.1

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15436: ------------------------------------- Summary: Bump Webservices to version 1.5.1 Key: JBIDE-15436 URL: https://issues.jboss.org/browse/JBIDE-15436 Project: Tools (JBoss Tools) Issue Type: Task Components: webservices Affects Versions: 4.1.1.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.1.1.Alpha1 Bump WebServices component version from 1.5.0 to 1.5.1 on jbosstools-4.1.x branch only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-15435: ----------------------------------- Assignee: Fred Bricon > "installed plugins" detection seems fishy in project examples / central > ----------------------------------------------------------------------- > > Key: JBIDE-15435 > URL: https://issues.jboss.org/browse/JBIDE-15435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha2 > > > Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins. > Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2753) Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2753: ----------------------------------- I concur, all "GWT+Window Designer" IUs should be added to the com.google.gpe.gwt connector. I opened JBIDE-15435 since [~maxandersen] sees inconsistent behaviour in the way installed plugins are detected. > Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer" > ------------------------------------------------------------------- > > Key: JBDS-2753 > URL: https://issues.jboss.org/browse/JBDS-2753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build > Reporter: Burr Sutter > Attachments: 2013-09-04_1215.png > > > See screenshot. > Do we need to keep the two Google Web Toolkit options separate? They were separated because they came in at different intervals, now it is unclear to me if they need to remain separate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-15435: ----------------------------------- Summary: "installed plugins" detection seems fishy in project examples / central Key: JBIDE-15435 URL: https://issues.jboss.org/browse/JBIDE-15435 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, project-examples Affects Versions: 4.1.0.Final Reporter: Fred Bricon Fix For: 4.1.1.Alpha2 Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins. Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2261) Flat File Importer unable to import files with no extensions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/JBDS-2261?page=com.atlassian.jira.plugin.... ] Barry LaFond resolved JBDS-2261. -------------------------------- Resolution: Done TEIIDDES-1483 was fixed and included in 8.x Designer builds. > Flat File Importer unable to import files with no extensions > ------------------------------------------------------------ > > Key: JBDS-2261 > URL: https://issues.jboss.org/browse/JBDS-2261 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: teiid > Affects Versions: 5.0.0.GA > Environment: JBDS 5.0.0 > Teiid Designer 7.7.x > Reporter: Hisanobu Okuda > Fix For: 6.0.0.Alpha1-SOA > > > Assuming a data directory with two files, "mydata1" and "mydata2.csv", when attempting to import files with the flat file importer of Teiid Designer, only "mydata2.csv" will be discovered and selectable in the import process. It is not possible to discover/select files without extensions in the flat file importer, since available file name filters are only "*.csv", "*.psv", "*.ssv", "*.tsv", "*.txt", and "*.*". "*" (no extension) is necessary. It is found in Teiid Designer, however, it is not an issue only concerning Teiid Designer, but a general issue, because a general file selection UI can not show files without extensions. There is no reason to consider a file without extensions as a non-text file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15334) Use Java5 method to check if String is empty

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15334?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15334: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version > Use Java5 method to check if String is empty > -------------------------------------------- > > Key: JBIDE-15334 > URL: https://issues.jboss.org/browse/JBIDE-15334 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > When importing some Archive projects in a workspace where a Java5 JRE exists, there is a compilation error because of the use of String#isEmpty() which is defined in Java6+ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14728) Distinguish between started and not started servers in MBean Explorer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14728?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14728: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version > Distinguish between started and not started servers in MBean Explorer > --------------------------------------------------------------------- > > Key: JBIDE-14728 > URL: https://issues.jboss.org/browse/JBIDE-14728 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Lets imagine these steps: > STEP: define a lot of servers in servers view > STEP: run one of them > STEP: open MBean Explorer view > STEP: in opened view (MBean) try to connect to started server > last step is very difficult for user if there are many similar server names or he doesn't remember exactly which server he started before. > It would be useful if user has possibility to somehow recognize started and not started servers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15321) ConcurrentModificationException in KbBuilder

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15321?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15321: ---------------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) set proper fix version > ConcurrentModificationException in KbBuilder > -------------------------------------------- > > Key: JBIDE-15321 > URL: https://issues.jboss.org/browse/JBIDE-15321 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Final > Environment: eclipse.buildId=4.3.0.I20130605-2000 > java.version=1.7.0_21 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > Reporter: George Gastaldi > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > The following exception happens sporadically when Eclipse is building projects in background (each panel is a log entry in the Error log panel): > {code} > Errors running builder 'JBoss Knowledge Base Builder' on project 'ui-tests'. > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) > at java.util.HashMap$KeyIterator.next(HashMap.java:928) > at java.util.AbstractCollection.addAll(AbstractCollection.java:333) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.hasToUpdateProjectDependencies(ClassPathMonitor.java:173) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.build(ClassPathMonitor.java:214) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:102) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} > and: > {code} > Errors running builder 'JBoss Knowledge Base Builder' on project 'maven'. > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) > at java.util.HashMap$KeyIterator.next(HashMap.java:928) > at java.util.AbstractCollection.addAll(AbstractCollection.java:333) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.hasToUpdateProjectDependencies(ClassPathMonitor.java:173) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.build(ClassPathMonitor.java:214) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:102) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) > at java.util.HashMap$KeyIterator.next(HashMap.java:928) > at java.util.AbstractCollection.addAll(AbstractCollection.java:333) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.hasToUpdateProjectDependencies(ClassPathMonitor.java:173) > at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.build(ClassPathMonitor.java:214) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:102) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 September 2013