That should as well be noted by the INFRA folks. That is files not getting pruned and thus wasting space over time because they sit in a dir structure that is too deep. I think at least "c:\\slave4\\tomee-trunk-win-sunsdk6\\" could be renamed to something like "C:\s4\tomee-trunk-ora6" or something like that. Thank heavens we don't build OSGi bundles, they usually create even more complex directory structures :)
Wondering why this issue still exists in 2014 :) Feel free to file a JIRA, I suppose this is an issue that applies to other projects too. Cheers Daniel On Thu, Aug 14, 2014 at 6:15 PM, Andy Gumbrecht <[email protected]> wrote: > What's really annoying is the Windows build, or lack of. > > I build locally on Windows, but the buildbot sits in a path that busts the > 255 char pathname limit - This prevents clean-up of files like: > > c:\\slave4\\tomee-trunk-win-sunsdk6\\build\\tck\\cdi- > embedded\\target\\surefire-reports\\junitreports\\TEST- > org.jboss.jsr299.tck.tests.context.passivating.broken. > enterpriseBeanWithNonPassivatingBeanConstructorParameterInInterceptor. > EnterpriseBeanWithNonPassivatingBeanConstructorParameterInIn > terceptorTest.xml > > I've tried all the property hacks for not creating these files, but every > build creates them. There is a Windows 'synchronise to an empty directory' > hack that can be used to clear the build directory, but no way of > automating that from the bot. > > Also... > > apache-ant-1.8.2 > jdk1.6.0_16 > apache-maven-3.0.4 > > ...are also really old. > > Time for an INFRA JIRA me thinks. > > Andy. > > -- > Andy Gumbrecht > > http://www.tomitribe.com > [email protected] > https://twitter.com/AndyGeeDe > > TomEE treibt Tomitribe! | http://tomee.apache.org > >
