> we face the same issue in mevenide (say one wants to build against a particular > ide). altho i dont know if this the best way to achieve this, what we do to > solve this is to declare a specific goal for each part we may want to build, > those goals only override maven.multiproject.includes and attain > multiproject:goal. this has worked nice so far.
That means you have all the info in several files? I pretty like the idea of using the sourceModifications excludes / includes. It can be useful in some cases. It makes have the info all in one place. Of course that's the anti multiproject paradigm. But I don't see that as being against maven way of working. It's still declarative programming, and if it works, why not? If each module has several classes then I don't mind going the multiproject way. But if I have a tool that just integrates with many other tools and I have 20 classes each of them depending on one particular external (potentially non accessible library), should I use multiproject or the sourceModifications exclude mechanism? Not sure. It seems it would be faster with sourceModifications. I talk but I have used maven on a handful of small projects. Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
