I thnk it's not a problem that container is not stateless. No matter how we should have CI jobs that builds all the artifacts and store them as official repos. You point out an important thing that is the mvn install is the key feature to propergate self patched components around. If we disable this than there's no reason to build jars by ourselves. I'm +1 to option 2. 2015年6月19日 上午5:59於 "Olaf Flebbe" <o...@oflebbe.de>寫道：
> > > Am 18.06.2015 um 23:57 schrieb jay vyas <jayunit100.apa...@gmail.com>: > > > > You can easily share the artifacts with a docker shared volume > > > > in the container "EXPORT M2_HOME=/container/m2/" > > > > follwed by > > > > "docker build -v ~/.m2/ /container/m2/ ........ " > > > > This will put the mvn jars into the host rather than the guest > conatainer, so that they persist. > > > > > > Thats not the point. Containers are not stateless any more. > > Olaf >
