On Sun, 27 Oct 2019 at 01:41, Vladimir Sitnikov <[email protected]> wrote: > > >And why does assemble run javadocAggregate? > > The aggregate javadoc is included into the binary distribution, so > assembling binary distribution requires the javadoc.
OK. I misunderstood the purpose of the assemble task, assuming it to be more like Maven assemble. > Do you think we can drop javadoc from the binary distribution? That is a separate issue. > >Whilst gradlew tasks lists all tasks, there are so many that finding > >the correct one is hard work > > sebb, I see how you might have troubles with shifting the build system, > however, I'm inclined that use cases of "how to build jars" and "how to > populate lib/" are properly accessible from "./gradlew tasks" output. > > ant -p produced 101 lines Of which half are description and introduction. There are only 52 actual tasks listed, and a lot of them are similar (e.g. the compile-xxx tasks) This leaves about 33 distinct tasks. Furthermore, the introduction has examples of how to use the build file. > ./gradlew tasks produces 136 lines. It produces 182 lines for me, and includes quite a lot of irrelevant output at the start. AFAICT there are 74 actual tasks, plus 3 pattern rules i.e. about twice as many actual tasks, and no helpful description. > > I don't think it is fair to say that it is "gradlew tasks produces way too > many tasks" or "it is worse than it was before" It is worse. ant -p is quite usable when displayed on the console. gw tasks is not really usable without further effort for the reasons listed above. > On the contrary, the tasks are grouped now, so you can skip sections. That was not really necessary before, as the list was relatively short. > If you search for "lib", then you find the task you need: > > $ ./gradlew tasks | grep lib > createDist - Copies JMeter jars and dependencies to projectRoot/lib/ folder > > Of course, there's a room for improvement (e.g. Gradle does not allow to > specify the order of groups in the `tasks` output yet), > however, "Build tasks" group is sorted the first, so "createDist" should be > discoverable fast. There is a lot of irrelevant output that appears first. > The task can be found by both "jar" and "lib" searches, so it does not look > like adding links to "gradle.md" would help in this case. No idea where you are proposing to add links. > Have you tried gradlew tasks? Yes, see above. > Do you have suggestions on improving the description? No idea what description you mean. > Vladimir
