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

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786495#comment-12786495 ] 

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