From: wisberg Date: Thu, 3 Aug 2006 16:03:35 +0000 (+0000) Subject: doc process for adding new modules (soon to be superceded) X-Git-Tag: pre_pr_153572~15 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=af722d0d6afc76147663ada3fe398a46e21fb90e;p=aspectj.git doc process for adding new modules (soon to be superceded) --- diff --git a/build/readme-build-and-test-aspectj.html b/build/readme-build-and-test-aspectj.html index 7292fc2ac..6ae35203f 100644 --- a/build/readme-build-and-test-aspectj.html +++ b/build/readme-build-and-test-aspectj.html @@ -448,6 +448,39 @@ the web with the release files and documentation, in Eclipse but fails in the Ant, it's your responsibility to fix it by following the build invariants below.

+

+

What to do when adding a new module (i.e., eclipse project): +

+
    +
  1. Setup like the other modules, following the invariants below, esp. +
      +
    1. same directory level
      2. +
    2. same naming conventions for source folders
      3. +
    3. same use of known classpath variables/entries
      4. +
    +
    2. +
  2. Add module to those checked for copyright/license in + + testsrc/org/aspectj/build/BuildModuleTests.java + +
    3. +
  3. Add module to module dependency tree as usual in Eclipse project properties
    4. +
  4. If the module is to produce a jar visible in {AspectJ}/lib, + then add a zero-length file of the correct name to + products/tools/dist/lib + and an alias to that file from the module name in + + Builder.properties +
    5. +
  5. To make the JUnit tests visible to the Ant builder, include a + top-level Ant suite titled {Module}ModuleTests.java +
    6. +
  6. Test the build in Eclipse/JUnit using + + testsrc/org/aspectj/internal/build/BuildModuleTest.java + +
    7. +

How the build system introspects, and the build invariants that are enforced by the Ant build: