Ralph Goers schrieb: > On May 12, 2009, at 9:30 PM, Christian Schulte wrote: > >> Ralph Goers schrieb: >>> Imagine that you could get a pom.xml for all of Apache Commons that >>> contained the dependency management for it. Every time a commons >>> project released a new Commons "bill of materials" would go with it. >>> >>> a) You want all the projects to be part of the build to be sure that >>> they all work together. Even though some projects didn't change, >>> running the unit tests will help identify any compatibility problems. >> If an artifact did not change, those tests will always yield the same >> results as during the release of that artifact. By "did not change" I >> assume that not only the source code did not change, also the pom and >> everything else also did not change. Maven did not change, not a >> single >> Maven plugin changed, no dependency, etc. > > This assumption is incorrect. All the projects in the library use > other parts of the library, just as commons projects use other commons > projects. Because a project does not specify the version of the > project it depends on but obtains it from the bom pom the dependency > will change with the new release.
Ok. No code changes but the artifact and you don't want to release without actual code changes. -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
