> Want to raise a JIRA (task?) and put it in the umbrella task? (SOLR-13914)? > I’m trying to keep all these kinds of TODO’s in a place we won’t forget them.
I won't forget this -- it's too annoying. ;) We can't change the folder structure now because merges would be too painful (and if we want to keep parallel build systems in place we can't do it anyway). This really is of low priority. What we should have in place is a list of common ant tasks that people use and a corresponding list of gradle commands -- this would ease the transition and encourage people to try the gradle build. I'd create an in-your-face top-level file "help.txt" and have a concise list of these. It can also be prioritized so that we know what needs to be ported asap? I can think of: ant compile => gradlew compileJava ant jar => gradlew package ant clean => gradlew clean ant clean-jars => [no replacement - JARs sourced directly from gradle caches] ant jar-checksums => gradlew jarChecksums ant test => gradlew test [or better (includes any other verification tasks): gradlew check] ant validate => gradlew check ant precommit => TODO If there's anything people regularly use, I'd add it to the list above. Most tasks that are rarely (or never) used I would *not* port from ant. Things like "jar-src" or "jacoco"... They should be components of other higher-level tasks or even subprojects on their own (jacoco could be a "check" task on a submodule called "tests:coverage" for example). A prioritized list of common workflow is really necessary to know which things are needed first so that people can start to use it for work. Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
