On 10/15/2015 04:18 PM, Eric Ludlam wrote:
Any particular project type may or may not care about the build system.
Some do because they are the build system. Some do because they look in
the config files to try to extract some handy nuggets of information.
Some do because the build system leaves a file behind that can be
detected as the root of the project.
Then we might as well treat the build-file-as-project-root-marker and
build-file-as-source-of-build-tasks as two unrelated things, in the API. And in
certain cases both implementations can delegate to the same code.
For your example above someone who is familiar with those tools would
pick the best way to detect a project (maybe by build system like ant,
or by some other means) and also pick the best way to extract whatever
data is needed, such as a command to pass to 'compile', and hopefully a
classpath. It might be 6 independent types that share a lot of code or
baseclasses, or maybe one hybrid. I don't think it really matters.
It matters if to *really* add support for a new build tool, the author has to
add X new project definitions.