2012/2/21 Jochen Gazda <gazdahims...@gmail.com>: > Why should we always try to build with the latest available released > parent? And who is "we" here? Did you mean (a) "we" = developers > building James to test our own changes or is it (b) "we" = developers > building a release for the public? > At the moment I can identify myself with (a): I am trying to find a > way how to effectively test my own changes in a freshly built James > instance. I will consider what you recommend at the bottom:
(a) With time we should have less parent changes. We had a few of them lately, but I think things will settle. The "parent" is similar to other dependencies. You don't upgrade them whenever you can, but once in a while you make a "dependency update round" and you check that everything works fine with the updated environment. (b) Most time we change the parent is to inherit some website change declared in the parent, so we care about this mainly during the release cycle. >> mvn clean package && mvn install for each project (in the >> right order, so to not depend on only snapshot repositories) I saw a typo in my previous comment you quoted: s/only/online/ Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
