add process-mangement design spec
Add some details about recent efforts in Play to support a Gradle plugin and how an incoming Play request triggers a Gradle build. Split Milestone 1 into two milestones - the first being the minimum required to get folks with basic project setups using and testing gradle's play support and the second being what should be worked on right after that
Removed a TODO that didn't actually show big improvement.
Documented an idea for avoiding too much hashing.
Profiled the incremental java compilation and tackled the first bottleneck: the detection of duplicate classes in the classpath was way too slow.
Documented one more thing TODO.
Documented incremental java compilation in the DSL for JavaCompile task.
Documented incremental java compilation in the user guide.
Added release note for incremental java compilation.
Better output path for generated jvm library jars
Removed unused field
Renamed global container of project components: ‘softwareComponents’ -> ‘projectComponents’
Fleshed out the potential DSL for the implementing a custom library type
- This is a bit of a straw-man to provide context for discussion
Added a few open issues to the spec
Instead of moving and aliasing the Jar task, just keep it in the original package
Removed unused plugin id
Test fix
Another test fix
Suggestion from GRADLE-2967 that exceptions during hashing should print the file path for troubleshooting purposes.
Adding docs, samples and release notes for the java-gradle-plugin development plugin story.