Move plugin build content under buildDir/j2objc

j2objc-contrib / j2objc-gradle

This plugin is no longer actively maintained. J2ObjC Gradle Plugin: enables Java source to be part of an iOS application's build so you can write an app's non-UI code (such as application logic and data models) in Java, which is then shared by Android apps (natively Java) and iOS apps (using J2ObjC), all as part of your usual Android Gradle build.

https://github.com/j2objc-contrib/j2objc-gradle

Apache License 2.0

139 stars 43 forks source link

Move plugin build content under buildDir/j2objc #317

Open brunobowden opened 9 years ago

brunobowden commented 9 years ago

The plugin produces 10+ files and directories under buildDir. They should all be moved under a common buildDir/j2obj/... structure to make it tidier.

advayDev1 commented 9 years ago

Actually, we should use the standard directories. Namely:

Every non-assemble task should have its output files in build/tmp/Something. (there is a variable on every Task for its temp output files that will generate that directory by the name of the task).
The assemble tasks should stay in build/j2objcOutputs/

brunobowden commented 9 years ago

@advayDev1 - are you speaking of Task.html#getTemporaryDir()? In that case, there's no guarantee that the contents last beyond the task... and we have a number of cases where they're passing content between tasks.

https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#getTemporaryDir()

advayDev1 commented 9 years ago

The key bug here is #549 re podspecs in the root of build/ directory. build/j2objcOutputs should indeed be separated from all other implementation detail build/ directories.

Here's a specific proposal: build/j2objcInternalGen - move everything that isn't intended for client consumption into here build/j2objcOutputs - everything that someone outside gradle needs to consume.