Requirements for ClassToSource
In identifying a need for a custom task, we must identify the requirements that are the biases for our use cases or user stories. Three stories—one each for user activity (UA1), reporting (UR1), and configuration (UC1)—can be extracted from the previous description. These requirements are listed in Table 6.1.
| Use Case | Description |
|---|---|
| UA1: | For each class on the classpath, find the matching source file using the source path. |
| UA2: | Ignore inner classes. |
| UA3: | Ignore JAR files. |
| UR1: | Generate a report listing each class for which there is no corresponding source. |
| UC1: | Let the user decide whether to fail the build if no source files are found. |
In addition to these user stories, we need a few technical ...
Get Ant Developer’s Handbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
