Community
Participate
Working Groups
It would be great to have pluggable ant targets that would fire at different points in the build process. I'm thinking of something similar to the targets supported by PDE Build. preProcess/postProcess - Used to run operations before and after compiling the source preAssemble/postAssemble - Used to run operations before and after assembling the binary distributables postBuild - Used to run operations at the end of the build My use case is that I need to modify the source code (replace tokens) during a product export. Another use case (mentioned in bug 85443) would be to package the product with an installer.
I don't think that this should be in the domain of PDE UI. As you already mentioned, this is already available in PDE Build. Wouldn't it be better if PDE UI would create some tools for creating the Ant scripts necessary for an automated build using PDE build? I tried to replicate the product export feature using PDE Build but this is not possible because of the hidden magic in ProductExportJob.
I see where you're going with that. If there was some way to get the product export functionality (launchers, icons, ini file, vm args, etc) into the PDE Build process, that would be great. The bottom line is that there really needs to be a way to build an RCP application in an automated way, and in a way which allows the actual RCP product export to be integrated into a larger build process. It looks like there's already a general discussion of this in bug 84065. We could call this a dup, if you like.
*** This bug has been marked as a duplicate of 84065 ***
