Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

These are just Ant scripts, and I already have tasks for javadoc and PMD. Whats the point of using Glean?

0
Posted

These are just Ant scripts, and I already have tasks for javadoc and PMD. Whats the point of using Glean?

0

The goal of Glean is to make code feedback easy in a couple of different ways: • to let you add or remove feedback tools easily for a given project • to let you run these tools against any project you have The first point means that you can easily try out different tools, change your mind, and experiment with what particular feedback is most valuable for your project. For many of the tools, it’s as simple as adding the tool’s name to the tool.pattern property. The Glean tool scripts are boilerplate Ant script for each tool, often just the one that most anyone would need to write if they were going to use that tool. For most people, this is a good starting point, and with Glean the time needed to try out a tool is minimal. And if the standard boilerplate values aren’t just what you want, there are property values that you can override with standard Ant property overrides. The second point means that you can have a consistent feedback process across any number of projects. You define you

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123