Hi,
Extensions can be used to achieve some modularization of the
OpenOffice.org code base and should be used to reduce the build time and
dependencies of the core OpenOffice.org builds.
For that reason we introduced different aliases to support the
differentiation of the core and extensions.
To my knowleadge there are at least three open issues:
1. move the pdf import extension into an extension only module (90061)
2. move the report designer extension into an extension only module (90062)
3. do we need the extensions make a prerequisite of the postprocess module ?
Once these issue are solved, we going to switch from OpenOffice2 to
OpenOffice3 alias plus an additional alias for the extensions (Extensions3)
Martin
c) Checking out OpenOffice.org
What is now the canonical way to check out OpenOffice.org ? is it meant
to be with alias OpenOffice3 ?
i.e.
we have the alias Extensions3 for
"scext sdext swext tomcat apache-commons reportdesign jfreereport"
we have the alias OpenOffice3 which has ...
"sccomp, sdext, reportdesign, reportdesign" in it
So swext and friends do not appear in the OpenOffice3 (or OpenOffice2)
alias, so they don't get checked out, but they are referenced in the
build.lsts. So in practice is seems to be to check out *both*
OpenOffice3 and Extensions3 to get the full tree required to build
C.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
