Skip to content
prod/lib (core jars)prod/comp (component jars)
Workflow
TOP LEVEL build.xml
↓
Delegates everything to: common/Agent/build.xml
↓
This file builds ~30 components Each component has its own build.xml
↓
Each component compiles Java → .class Creates a JAR for that component
↓
All JARs copied into: common/Agent/prod/lib, or common/Agent/prod/comp. All resources copied into: common/Agent/prod/Resources
↓
Installer pipeline picks up prod/ directory
↓
NSIS builds final MyProductInstaller.exe
⭐ Final Summary — The EXACT Truth
Let me combine it cleanly:
✔ 1. prod/lib contains dependency JARs
Correct.
✔ 2. build.xml creates only:
bin/
prod/Resources/
Nothing else.
✔ 3. Each component does create its own JAR
Correct — one per component.
✔ 4. JAR outputs are placed in two places:
✔ 5. Locale/language files go into
prod/Resources/
✔ 6. .class files are NOT all placed in the top-level bin
Some components compile into:
common/Agent/bin/
Others compile into:
com/apcc/m11/components/EventLogger/bin/
etc.
It depends on each component's build.xml.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.