[ https://issues.apache.org/jira/browse/TINKERPOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667122#comment-15667122 ]
ASF GitHub Bot commented on TINKERPOP-1493: ------------------------------------------- Github user pauljackson commented on the issue: https://github.com/apache/tinkerpop/pull/457 Is there a stacktrace or other output that might help us figure this out? Specific test that fails? Thanks, -Paul From: stephen mallette [mailto:notificati...@github.com] Sent: Saturday, November 12, 2016 6:22 AM To: apache/tinkerpop Cc: Paul A. Jackson; Author Subject: Re: [apache/tinkerpop] TINKERPOP-1493 Groovy project doesn't build on Windows (#457) I'm still in a position where tp31 is fine on docker but this PR is not. I rely on docker pretty heavily, so until I figure out what's wrong with my environment, I'm hesitant to +1 this though I admit that this change really shouldn't affect spark at all (yet somehow it does). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/apache/tinkerpop/pull/457#issuecomment-260116393>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAUcSN3Z2a6jxIhpM6WzjYTYgSCYCkKcks5q9aFugaJpZM4KVbcO>. ________________________________ > Groovy project doesn't build on Windows > --------------------------------------- > > Key: TINKERPOP-1493 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1493 > Project: TinkerPop > Issue Type: Bug > Components: groovy > Affects Versions: 3.2.2 > Reporter: Paul Jackson > Assignee: Jason Plurad > Priority: Minor > > Builds on Windows fail for two reasons. First the line to create extTestDir > is creating a path consisting of two full paths concatenated together. The > second drive letter is seen as an illegal character: > {code}private static final File extTestDir = new > File(System.getProperty("user.dir"), > TestHelper.makeTestDataDirectory(DependencyGrabberTest.class));{code} > Second, when it comes time to delete the directory it is locked. This is > because some instances of JarFile are created on it but not closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)