We traditionally distribute a pre-built ECJ jarfile in a jar/ directory. This got dropped from the development repo somehow. Since cloning the repo is the primary way many users will download ECJ, the jar needs to be in the repo (i.e. we can't rely on make dist to create a jar only at release time).
Maven, moreover, puts its jar in target/ instead of jar/. In this sense Maven is inconsistent with the Makefile.
We also need to write a section in ecj/README.md explaining how to get started with ECJ by just using the pre-built jar (right now the README only talks about how to compile a fresh build of ECJ, which will be irrelevant to many or most users).
We traditionally distribute a pre-built ECJ jarfile in a
jar/directory. This got dropped from the development repo somehow. Since cloning the repo is the primary way many users will download ECJ, the jar needs to be in the repo (i.e. we can't rely onmake distto create a jar only at release time).Maven, moreover, puts its jar in
target/instead ofjar/. In this sense Maven is inconsistent with the Makefile.We also need to write a section in
ecj/README.mdexplaining how to get started with ECJ by just using the pre-built jar (right now the README only talks about how to compile a fresh build of ECJ, which will be irrelevant to many or most users).