July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-101) Eclipse Juno dir path length bug breaks ESB examples

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-101?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBTIS-101: -------------------------------- Assignee: Paul Leacu This might already be fixed but figured if it sat in JBDS as a Doug Palmer todo it would never been seen. > Eclipse Juno dir path length bug breaks ESB examples > ---------------------------------------------------- > > Key: JBTIS-101 > URL: https://issues.jboss.org/browse/JBTIS-101 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Environment: Eclipse Juno > JBosstools - from trunk - http://svn.jboss.org/repos/jbosstools > Reporter: Len DiMaggio > Assignee: Paul Leacu > Priority: Blocker > > This eclipse Juno bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193 > Which shows up as: > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(ProcessImpl.java:188) > at java.lang.ProcessImpl.start(ProcessImpl.java:132) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021) > ... 10 more > Note - The real issue is that the classpath is too long, not the dir path. > The problem is preventing the ESB examples from running. > To recreate the issue, open the eclipse/tools UI with a CLI command such as: > cmd.exe /X /C ""C:\Program Files\Java\jdk1.7.0\jre\bin\java.exe" -Dosgi.noShutdown=false -Dosgi.os=win32 -Dosgi.ws=win32 -Dosgi.arch=x86_64 -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -Djbosstools.test.jbossesb.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jbossesb-4.11 -Djbosstools.test.jbosssoa.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jboss-soa-p-5/jboss-as -Dswtbot.test.properties.file=./org.jboss.tools.esb.ui.bot.test.properties -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -jar C:\Users\jbossqa\.m2\repository\p2\osgi\bundle\org.eclipse.equinox.launcher\1.3.0.v20120522-1813\org.eclipse.equinox.launcher-1.3.0.v20120522-1813.jar -data C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\data -dev file:/C:/Users/jbossqa/jbosstools/trunk/esb/tests/org.jboss.tools.esb.ui.bot.test/target/dev.properties -install C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work -configuration C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\configuration -application org.eclipse.ui.ide.workbench " > Then import any of the ESB examples and attempt to run one of the clients (such as SendJMSMessage). > Automated tests for this are here: > Error #1 - http://machydra.brq.redhat.com:8080/job/esb.bot.tests.ldimaggi.matrixtest/ -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-101) Eclipse Juno dir path length bug breaks ESB examples

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-101?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-101 at 7/1/13 9:51 AM: ---------------------------------------------------------- This might already be fixed but figured if it sat in JBDS as a Doug Palmer todo it would never been seen. So, moved to JBTIS and assigned to [~pleacu]. was (Author: nickboldt): This might already be fixed but figured if it sat in JBDS as a Doug Palmer todo it would never been seen. > Eclipse Juno dir path length bug breaks ESB examples > ---------------------------------------------------- > > Key: JBTIS-101 > URL: https://issues.jboss.org/browse/JBTIS-101 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Environment: Eclipse Juno > JBosstools - from trunk - http://svn.jboss.org/repos/jbosstools > Reporter: Len DiMaggio > Assignee: Paul Leacu > Priority: Blocker > > This eclipse Juno bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193 > Which shows up as: > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(ProcessImpl.java:188) > at java.lang.ProcessImpl.start(ProcessImpl.java:132) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021) > ... 10 more > Note - The real issue is that the classpath is too long, not the dir path. > The problem is preventing the ESB examples from running. > To recreate the issue, open the eclipse/tools UI with a CLI command such as: > cmd.exe /X /C ""C:\Program Files\Java\jdk1.7.0\jre\bin\java.exe" -Dosgi.noShutdown=false -Dosgi.os=win32 -Dosgi.ws=win32 -Dosgi.arch=x86_64 -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -Djbosstools.test.jbossesb.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jbossesb-4.11 -Djbosstools.test.jbosssoa.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jboss-soa-p-5/jboss-as -Dswtbot.test.properties.file=./org.jboss.tools.esb.ui.bot.test.properties -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -jar C:\Users\jbossqa\.m2\repository\p2\osgi\bundle\org.eclipse.equinox.launcher\1.3.0.v20120522-1813\org.eclipse.equinox.launcher-1.3.0.v20120522-1813.jar -data C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\data -dev file:/C:/Users/jbossqa/jbosstools/trunk/esb/tests/org.jboss.tools.esb.ui.bot.test/target/dev.properties -install C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work -configuration C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\configuration -application org.eclipse.ui.ide.workbench " > Then import any of the ESB examples and attempt to run one of the clients (such as SendJMSMessage). > Automated tests for this are here: > Error #1 - http://machydra.brq.redhat.com:8080/job/esb.bot.tests.ldimaggi.matrixtest/ -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-101) Eclipse Juno dir path length bug breaks ESB examples

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-101?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-101 at 7/1/13 9:52 AM: ---------------------------------------------------------- This might already be fixed but figured if it sat in JBDS as a Doug Palmer todo it would never been seen. So, moved to JBTIS and assigned to [~pleacu]. Perhaps [~bfitzpat] can comment on whether it's still a problem? was (Author: nickboldt): This might already be fixed but figured if it sat in JBDS as a Doug Palmer todo it would never been seen. So, moved to JBTIS and assigned to [~pleacu]. > Eclipse Juno dir path length bug breaks ESB examples > ---------------------------------------------------- > > Key: JBTIS-101 > URL: https://issues.jboss.org/browse/JBTIS-101 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Environment: Eclipse Juno > JBosstools - from trunk - http://svn.jboss.org/repos/jbosstools > Reporter: Len DiMaggio > Assignee: Paul Leacu > Priority: Blocker > > This eclipse Juno bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193 > Which shows up as: > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(ProcessImpl.java:188) > at java.lang.ProcessImpl.start(ProcessImpl.java:132) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021) > ... 10 more > Note - The real issue is that the classpath is too long, not the dir path. > The problem is preventing the ESB examples from running. > To recreate the issue, open the eclipse/tools UI with a CLI command such as: > cmd.exe /X /C ""C:\Program Files\Java\jdk1.7.0\jre\bin\java.exe" -Dosgi.noShutdown=false -Dosgi.os=win32 -Dosgi.ws=win32 -Dosgi.arch=x86_64 -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -Djbosstools.test.jbossesb.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jbossesb-4.11 -Djbosstools.test.jbosssoa.home=C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target/requirements/jboss-soa-p-5/jboss-as -Dswtbot.test.properties.file=./org.jboss.tools.esb.ui.bot.test.properties -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -jar C:\Users\jbossqa\.m2\repository\p2\osgi\bundle\org.eclipse.equinox.launcher\1.3.0.v20120522-1813\org.eclipse.equinox.launcher-1.3.0.v20120522-1813.jar -data C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\data -dev file:/C:/Users/jbossqa/jbosstools/trunk/esb/tests/org.jboss.tools.esb.ui.bot.test/target/dev.properties -install C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work -configuration C:\Users\jbossqa\jbosstools\trunk\esb\tests\org.jboss.tools.esb.ui.bot.test\target\work\configuration -application org.eclipse.ui.ide.workbench " > Then import any of the ESB examples and attempt to run one of the clients (such as SendJMSMessage). > Automated tests for this are here: > Error #1 - http://machydra.brq.redhat.com:8080/job/esb.bot.tests.ldimaggi.matrixtest/ -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15035) Add tomcat runtime detection to JBT update site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15035?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15035: ---------------------------------------- > Why are we adding new features AFTER CR1 Feature Freeze? IIRC, Fred requested it on Thursday, just before CR1, and his request was not honoured promptly because the parent pom was not pointing to the right site for base. So it has been delayed to now. Seems like this feature contains some big value and is worth being added in CR1 (and also worth delaying delivery of CR1 to QA) ? [~maxandersen] Is it to be considered as a blocker for CR1? [~fbricon] [~maxandersen]: Is it ok to make this feature part of the Abridged category as well? If so, I'll update my PR immediately. > Add tomcat runtime detection to JBT update site > ----------------------------------------------- > > Key: JBIDE-15035 > URL: https://issues.jboss.org/browse/JBIDE-15035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Affects Versions: 4.1.0.Beta2 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.0.CR1 > > > Following JBIDE-14944, can we make sure the Tomcat Detection feature is added to the JBT update site? > See https://github.com/jbosstools/jbosstools-server/blob/master/site/category... for feature ids -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12492) release JBT SOA Tooling 3.3.0.Final to www.jboss.org/tools/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12492?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-12492. ------------------------------ Assignee: Nick Boldt (was: Douglas Palmer) Fix Version/s: 3.3.3.Final-SOA (was: 4.0.0.Alpha1-SOA) Resolution: Out of Date 3.3.3 is released; closing Out Of Date. > release JBT SOA Tooling 3.3.0.Final to www.jboss.org/tools/ > ----------------------------------------------------------- > > Key: JBIDE-12492 > URL: https://issues.jboss.org/browse/JBIDE-12492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Integration Platform, website > Affects Versions: 3.3.0.Final-SOA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 3.3.3.Final-SOA > > > JBT SOA 3.3.0.GA is not yet linked from www.jboss.org/tools. > Affected pages: > http://www.jboss.org/tools/download/ > http://www.jboss.org/tools/download/stable > http://www.jboss.org/tools/download/dev/3_3_SOA (page should be copied into /stable/, then edited) > http://www.jboss.org/tools/download/stable/3_3_SOA (new page) > Also, for future releases, please use .Final instead of .GA as per the jboss.org guidelines [1] for project releases. > [1] https://community.jboss.org/wiki/JBossProjectVersioning > Details on how to publish the bits and update via Magnolia are here: > https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/2... (needs updating) > https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/2... (last updated for 3.3.1.Final release) > If you need assistance, please don't hesitate to ask. > If you need access to the sourceforge repo, please ping one of the project owners listed here: http://sourceforge.net/projects/jboss/ eg., Mark Newton. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15035) Add tomcat runtime detection to JBT update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15035?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15035: ------------------------------------ [~fbricon] [~maxandersen] Why are we adding new features AFTER CR1 Feature Freeze? Surely this is *too late* to be included? Would this new feature need to be on the webtools [0] site too, so it's available when o.j.i.e.as.feature is being installed? [0] http://download.jboss.org/jbosstools/updates/nightly/webtools/trunk/ ----- [~mickael_istria] To add new features to Marketplace: a) add to CoreTools ("Abridged") category b) build & publish new release to the dev milestone site [1] c) copy new IU(s) from CoreTools.category.features list [2] into list of IUs included in the connector description [3] [1] http://download.jboss.org/jbosstools/updates/development/kepler/ [2] http://download.jboss.org/jbosstools/updates/development/kepler/site.prop... [3] https://marketplace.eclipse.org/content/jboss-tools-kepler/edit > Add tomcat runtime detection to JBT update site > ----------------------------------------------- > > Key: JBIDE-15035 > URL: https://issues.jboss.org/browse/JBIDE-15035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Affects Versions: 4.1.0.Beta2 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.0.CR1 > > > Following JBIDE-14944, can we make sure the Tomcat Detection feature is added to the JBT update site? > See https://github.com/jbosstools/jbosstools-server/blob/master/site/category... for feature ids -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2673) Can't build JBDS because of p2.mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2673?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2673: ---------------------------------- Can't use unified as default for JBDS because then anyone NOT on VPN can't build. Point was to make it possible to build JBDS from source zip from anywhere by anyone. Therefore must set multiple as default, or publish JBDS TP to a public location instead of www.qa server, or strip p2.mirrors from our mirrors. > Can't build JBDS because of p2.mirrors > -------------------------------------- > > Key: JBDS-2673 > URL: https://issues.jboss.org/browse/JBDS-2673 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 7.0.0.CR1 > > > Tried to build JBDS 7.0.0.CR1 tonight in Jenkins, but got this instead: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_70/347/console} > [ERROR] Internal error: java.lang.RuntimeException: "Messages while reading artifacts from child repositories": ["Problems while reading artifacts from http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626...": ["Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."], "Retry another mirror": ["HTTP Server 'Service Unavailable': http://ftp.ussg.iu.edu/eclipse/releases/kepler/201306260900/plugins/org.e..."]]] -> [Help 1] > {code} > I thought we were filtering out all the external references from the metadata after we mirrored? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13301) Need a new core test - ESB runtime detection - to successfully test for ESB version 4.11

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13301?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick resolved JBIDE-13301. --------------------------------------- Resolution: Done merged and assumed resolved > Need a new core test - ESB runtime detection - to successfully test for ESB version 4.11 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-13301 > URL: https://issues.jboss.org/browse/JBIDE-13301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.0.0.Final > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.CR1 > > > Related to: > https://issues.jboss.org/browse/JBDS-2394#comment-12741206 > <nboldt> ldimaggi: do any of the as.core tests involve esb 4.11? > <nboldt> ldimaggi: open a jira for rawblem to add a test for JBT 4.1 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15068) Please wait while Hibernate Tools is being installed

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15068?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-15068: -------------------------------- Attachment: 2013-07-01_0837.png 2013-07-01_0838.png 2013-07-01_0838_001.png > Please wait while Hibernate Tools is being installed > ---------------------------------------------------- > > Key: JBIDE-15068 > URL: https://issues.jboss.org/browse/JBIDE-15068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Environment: Windows 64-bit, 32-bit 1.6 JVM > Reporter: Burr Sutter > Attachments: 10244.txt, 2013-07-01_0837.png, 2013-07-01_0838.png, 2013-07-01_0838_001.png > > > While attempting to use Forge Wizard Generate Entities, you first receive a Forge Starting message, then a Hibernate Tools message which hangs/locks up. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15068) Please wait while Hibernate Tools is being installed

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15068?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-15068: -------------------------------- Attachment: 10244.txt > Please wait while Hibernate Tools is being installed > ---------------------------------------------------- > > Key: JBIDE-15068 > URL: https://issues.jboss.org/browse/JBIDE-15068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Environment: Windows 64-bit, 32-bit 1.6 JVM > Reporter: Burr Sutter > Attachments: 10244.txt, 2013-07-01_0837.png, 2013-07-01_0838.png, 2013-07-01_0838_001.png > > > While attempting to use Forge Wizard Generate Entities, you first receive a Forge Starting message, then a Hibernate Tools message which hangs/locks up. -- 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, 9 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 July 2013