Now my confusion over my own understanding and assumption is:
1) During the development process within an iteration, how to make
sure that all the module owners dependent on "a.jar" keeps up to date
with the changing versions of a.jar as the development goes on until
Integration Testing.
In my opinion there is also some bit of discipline involved here. Your
CI server does scheduled builds for all project modules. Developers
should ensure they update their projects regularly. For me the first
thing in the morning when I get to work are:
> svn up
> mvn clean eclipse:clean eclipse:eclipse -DdownloadSources=true
(assuming there were not build failure notifications from CI server ;-)
). Also keep in the mind to use SNAPSHOTS (as suggested in the other
email).
2) If a module owner dependent on a.jar fails to update the version of
the a.jar in the pom.xml and/or miss to commit the updated pom.xml
with a contemporary version of a.jar. Continuous Integration at
Continuum would suffer( assuming that even with not up to date version
of a.jar the module still gets through build),
Continuous integration would show red flags if there were incompatible
changes checked in. To a good extent this also depends on the tests that
the developers have in place for each module.
Pardon me for any wrong assumptions, I do not have much exposure to the process.
Regards,
Amit
HTH,
Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
