> But then, this seems like a Maven bug. Why go through the install process > for a project if its source code hasn't changed?
As soon as you can figure out how Maven can consistently, reliably, and definitively tell that an artifact has not changed before building it, we can talk about how it might be implemented in Maven. Bear in mind that it is not sufficient to look at the file timestamps in target vs source and say "target files are all newer than source, therefore no changes" due to the possibilities of changes coming in via dependencies (including transitive ones), changes in plugins (if they aren't locked down, or if they are snapshots), etc. Part of your build may be to grab another jar (versioned as snapshot), unpack it, and use it during this project's build -- without doing that, how do you know what the results will be in advance? As such, the only way to know if the output of a given project is different from the last build is to do the build itself, right? If you are really unhappy about this situation, you can use profiles or simply multiple parent poms that specify collections of modules rather than invoking all of them. But I think you will run into troubles with versions before too long. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
