Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gradle deletes all files and puts only changed files in build directory (only on exFAT fs) #15735

Closed
mihett05 opened this issue Jan 11, 2021 · 1 comment
Labels

Comments

@mihett05
Copy link

I've tried to build simple project with gradle on exFAT file system, after second build gradle deletes all compiled files from build/classes/java and puts only changed files. And it's impossible to run a project (referenced classes/packages not found). Gradle builds normally the same project on NTFS .

Expected Behavior

Gradle removes only files that have changed and puts changed files in build/classes directory.

Current Behavior

Gradle removes all and puts only changed files in build/classes directory.

Context

build.gradle file:

plugins {
    id 'application'
}

repositories {
    jcenter()
}

dependencies {
    testImplementation 'junit:junit:4.13'
    implementation 'com.google.guava:guava:29.0-jre'
}

application {
    mainClassName = 'org.app.App'
}

Steps to Reproduce

  1. Generate project by gradle init in directory on exFAT disk.
  2. Build it first time
  3. Build it again
  4. Look to build/classes/java directory or try to gradle run

Your Environment

File system: exFAT
OS: Windows 10 1909

Build scan URL for second gradle build: https://scans.gradle.com/s/cunw3wd2faz3e
Build scan URL for gradle run after second build: https://scans.gradle.com/s/t5tbhvxesquq6

@bmuskalla
Copy link
Contributor

Supporting exFAT is tracked on #4329. Thanks for the report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants