Jason van Zyl wrote on Thursday, July 15, 2004 8:16 PM: > On Thu, 2004-07-15 at 14:02, Jerome Lacoste wrote: >> Let's say I have a piece of the code that I want to compile only if a >> library is present. > > This is never a good idea. > > Why? From first hand experience it was found with code in > Turbine that optional packages often were left unloved, > unmaintained and generally left to rot. > > Projects should not have optional things to build: whatever > is believed to be optional should be moved out into another > build and referenced from the build in question. Optional > building based on the presence of resources is just nasty > business because then you need constructs to deal with > excludes for compilation, test compilation, test running and all the > way down the line.
This is not always possible. We have in a multiproject a subcomponent based on a piece of properietary software. We allow the customer to build anything from sources and the special subcopmponent is build, if the customer has that proprietary piece. Not even all of the project's developers have it. Therefore I search myself the best way to remove subprojects from the multiproject's reactor list. -- J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
