Hi KP I have not been able to understand why the lwp generation is so different in every aspect from the generation of 'normal' packages. Where is the logic for the lwp generation hidden, it definitely does not have a buildtool.cfg which takes care of the package generation.
As there is no compilation involved would it not make most sense to just put this logic into the buildtool.mk for lwp? I am asking, because I have a number of new and changed files for webconf and I am just uncertain where to put them . My original idea to just bundle them with the files for the corresponding leaf package was that harshly rejected that I gave up. Right now we have two distinct places where we build webconf stuff and that makes be quite uneasy, as the dependency will certainly grow. cheers Erich
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
