February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16631) After stopping/restarting F2 the inputstream is closed

by Koen Aers (JIRA)

Koen Aers created JBIDE-16631: --------------------------------- Summary: After stopping/restarting F2 the inputstream is closed Key: JBIDE-16631 URL: https://issues.jboss.org/browse/JBIDE-16631 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.2.0.Beta1 This results in an IOException: java.io.IOException: Pipe closed at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:261) at java.io.PipedInputStream.receive(PipedInputStream.java:227) at java.io.PipedOutputStream.write(PipedOutputStream.java:149) at java.io.OutputStream.write(OutputStream.java:75) at org.jboss.tools.aesh.core.io.AeshInputStream.append(AeshInputStream.java:24) at org.jboss.tools.aesh.core.console.AeshConsole.sendInput(AeshConsole.java:132) at org.jboss.tools.aesh.ui.view.AeshTextViewer.handleVerifyEvent(AeshTextViewer.java:149) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15256) Include tycho-source-feature-plugin and tycho-p2-plugin into parent/pom.xml/build/pluginManagement

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15256?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15256: ------------------------------------ [~dgolovin] do you want to merge PR 170? https://github.com/jbosstools/jbosstools-base/pull/170 > Include tycho-source-feature-plugin and tycho-p2-plugin into parent/pom.xml/build/pluginManagement > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-15256 > URL: https://issues.jboss.org/browse/JBIDE-15256 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha1 > > > Currently every feature's pom.xml includes the same code, which is code-duplication issue. > {code} > <plugin> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-source-feature-plugin</artifactId> > <version>${tychoExtrasVersion}</version> > <executions> > <execution> > <id>source-feature</id> > <phase>package</phase> > <goals> > <goal>source-feature</goal> > </goals> > </execution> > </executions> > </plugin> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-p2-plugin</artifactId> > <version>${tychoVersion}</version> > <executions> > <execution> > <id>attached-p2-metadata</id> > <phase>package</phase> > <goals> > <goal>p2-metadata</goal> > </goals> > </execution> > </executions> > </plugin>{code} > It should be included into pluginManagement section of parent/pom.xml instead and that would reduce code duplication to > {code}<plugin> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-source-feature-plugin</artifactId> > </plugin> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-p2-plugin</artifactId> > </plugin>{code} > in every feture's pom.xml file. > More over code above could be moved to to features/pom.xml as > {code}<build> > <plugins> > <plugin> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-source-feature-plugin</artifactId> > </plugin> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-p2-plugin</artifactId> > </plugin> > </plugins> > </build>{code} > that would let keep pom.xml for every feature even cleaner. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16506) Tooling contains two Forge(1) consoles after installation from abridged tools

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16506?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-16506. ------------------------------- Resolution: Done > Tooling contains two Forge(1) consoles after installation from abridged tools > ----------------------------------------------------------------------------- > > Key: JBIDE-16506 > URL: https://issues.jboss.org/browse/JBIDE-16506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Alpha2 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Beta1 > > Attachments: forge-consoles-compare.png, forge-consoles.png > > > I installed JBT from the * Abridged JBoss Tools category and I see 2 Forge(1) consoles after the installation. > I suppose there should be just one. > Please see screenshot attached. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16514) Link and Goto F1 toolbar buttons are not working anymore

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16514?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-16514. ------------------------------- Resolution: Done > Link and Goto F1 toolbar buttons are not working anymore > -------------------------------------------------------- > > Key: JBIDE-16514 > URL: https://issues.jboss.org/browse/JBIDE-16514 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.0.Beta1 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16623) NPE when creating ConnectionProfile

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16623?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-16623. ------------------------------- Resolution: Done > NPE when creating ConnectionProfile > ----------------------------------- > > Key: JBIDE-16623 > URL: https://issues.jboss.org/browse/JBIDE-16623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.0.Beta1 > > > When creating a new connection profile, I get the following stack trace: > java.lang.NullPointerException > at org.jboss.tools.forge.ui.ext.database.ConnectionProfileManagerImpl.createProperties(ConnectionProfileManagerImpl.java:160) > at org.jboss.tools.forge.ui.ext.database.ConnectionProfileManagerImpl.saveExistingProfile(ConnectionProfileManagerImpl.java:73) > at org.jboss.tools.forge.ui.ext.database.ConnectionProfileManagerImpl.saveConnectionProfile(ConnectionProfileManagerImpl.java:65) > at org.jboss.tools.forge.ui.ext.database.ConnectionProfileManagerImpl.saveConnectionProfiles(ConnectionProfileManagerImpl.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:101) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:74) > at org.jboss.forge.addon.database.tools.connections.ConnectionProfileManager_$$_javassist_18b68e88-2ac3-4416-9bb7-d5f443805201.saveConnectionProfiles(ConnectionProfileManager_$$_javassist_18b68e88-2ac3-4416-9bb7-d5f443805201.java) > at org.jboss.forge.addon.database.tools.connections.CreateConnectionProfileCommand.execute(CreateConnectionProfileCommand.java:67) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75) > at org.jboss.forge.addon.database.tools.connections.CreateConnectionProfileCommand_$$_javassist_fe829c68-b03b-49e0-82ab-3702b548355c.execute(CreateConnectionProfileCommand_$$_javassist_fe829c68-b03b-49e0-82ab-3702b548355c.java) > at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:88) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:101) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:74) > at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_0a236872-8975-4b42-8b27-76e9882b76e5.execute(CommandController_$$_javassist_0a236872-8975-4b42-8b27-76e9882b76e5.java) > at org.jboss.tools.forge.ui.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:87) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2926) remove Google GPE + GWT + WB connector from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2926?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2926: ----------------------------- Attachment: 00000864.png > remove Google GPE + GWT + WB connector from Central > --------------------------------------------------- > > Key: JBDS-2926 > URL: https://issues.jboss.org/browse/JBDS-2926 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Attachments: 00000864.png > > > [~burrsutter] has requested that the Google Web Toolkit, Google Plugin for Eclipse, and WindowBuilder features within the GWT+GPE+WB connector in JBoss Central be removed for JBT 4.2 / JBDS 8.0. > Please discuss & ACK as needed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2926) remove Google GPE + GWT + WB connector from Central

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2926: -------------------------------- Summary: remove Google GPE + GWT + WB connector from Central Key: JBDS-2926 URL: https://issues.jboss.org/browse/JBDS-2926 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 8.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt [~burrsutter] has requested that the Google Web Toolkit, Google Plugin for Eclipse, and WindowBuilder features within the GWT+GPE+WB connector in JBoss Central be removed for JBT 4.2 / JBDS 8.0. Please discuss & ACK as needed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2926) remove Google GPE + GWT + WB connector from Central

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2926?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2926: ----------------------------- CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? CDW release: ? > remove Google GPE + GWT + WB connector from Central > --------------------------------------------------- > > Key: JBDS-2926 > URL: https://issues.jboss.org/browse/JBDS-2926 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > [~burrsutter] has requested that the Google Web Toolkit, Google Plugin for Eclipse, and WindowBuilder features within the GWT+GPE+WB connector in JBoss Central be removed for JBT 4.2 / JBDS 8.0. > Please discuss & ACK as needed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2869) 3rd party certification for JBDS 8.0.0.GA

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2869?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2869: ----------------------------------- [~nickboldt] Yes to the WindowBuilder, GWT, GPE pieces and possibly the Maven+GWT tool (awaiting Fred's thoughts) > 3rd party certification for JBDS 8.0.0.GA > ----------------------------------------- > > Key: JBDS-2869 > URL: https://issues.jboss.org/browse/JBDS-2869 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, requirements > Affects Versions: 8.0.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.GA > > > For JBDS 8.0.0.GA, we need to ensure this list is as current and up to date as possible. > Upstream question about JDK 7 support: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=423834 > Proposed *new* connectors for JBDS 8.0: > * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0* > Connectors we could update: > * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 > * m2e-wro4j 1.0.2 connector > * atlassian/3.2.2.v20130909 (affects JBT/JBDS/Central TP) > * pmd/4.0.1 > * testng/6.8.6.20130914_0724 (affects JBDS installer/Central TP) > * VJET/0.10.0.201309201624 > * eclipsecs/5.6.1.201306282206 > * springide/3.4.0.201310051539-RELEASE > * gwt/3.4.2.v201310081834-rel-*r43 ONLY* (affects JBT/JBDS/Central TP) > * subclipse/1.10_1.8 > * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15 > Additionally (Target Platform): > * swtbot 2.1.1.201305311053 (included in JBT TP; needed for running UI tests; move to 2.1.2?) > JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): > * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) > * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) > See comments below for latest site URLs. > [1] https://github.com/jbosstools/jbosstools-locus/ > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... > [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ > ¥ - These issues did not block the release of JBDS 7.1.0.GA, and therefore would not block 8.0.0 either -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2869) 3rd party certification for JBDS 8.0.0.GA

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2869?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2869: ----------------------------------- [~nickboldt] definitely NOT android :-) > 3rd party certification for JBDS 8.0.0.GA > ----------------------------------------- > > Key: JBDS-2869 > URL: https://issues.jboss.org/browse/JBDS-2869 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, requirements > Affects Versions: 8.0.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.GA > > > For JBDS 8.0.0.GA, we need to ensure this list is as current and up to date as possible. > Upstream question about JDK 7 support: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=423834 > Proposed *new* connectors for JBDS 8.0: > * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0* > Connectors we could update: > * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 > * m2e-wro4j 1.0.2 connector > * atlassian/3.2.2.v20130909 (affects JBT/JBDS/Central TP) > * pmd/4.0.1 > * testng/6.8.6.20130914_0724 (affects JBDS installer/Central TP) > * VJET/0.10.0.201309201624 > * eclipsecs/5.6.1.201306282206 > * springide/3.4.0.201310051539-RELEASE > * gwt/3.4.2.v201310081834-rel-*r43 ONLY* (affects JBT/JBDS/Central TP) > * subclipse/1.10_1.8 > * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15 > Additionally (Target Platform): > * swtbot 2.1.1.201305311053 (included in JBT TP; needed for running UI tests; move to 2.1.2?) > JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): > * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) > * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) > See comments below for latest site URLs. > [1] https://github.com/jbosstools/jbosstools-locus/ > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... > [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ > ¥ - These issues did not block the release of JBDS 7.1.0.GA, and therefore would not block 8.0.0 either -- 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, 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 February 2014