Disable maven release plugin defined in parent pom?

I think you're taking the wrong approach here. Let me explain.

I think you're taking the wrong approach here. Let me explain. The deploy phase of maven is not meant to mean deploy to a remote server or anything like this.

This is meant to be deploy to a remote repository. Hence I believe you shouldn't try to skip the deploy phase in your module, but un-tie the deployment to a remote Tomcat server from the deploy phase, by making it a specific goal for example.

Thanks for you reply. I had tied my deploy war file to remort tomcat server at prepare-package-phase since my test goal depends on that. What is your suggestion for this kind testing package?

– user639812 Apr 7 at 16:23 Well it all depends but my general rule is that my build should be self contained, including (integration) testing. So I'd look in deploying in a local (to the build) Tomcat instance (using the Cargo or Tomcat plugin for example) and test there. This way your build doesn't depend on any external resource that needs a specific configuration.

If that takes too much time to run for releases, then I suggest you find a way to just skip the testing on the tomcat instance, but not the full deploy phase. Also the best phase for this testing is probably the integration-test phase. HTH.

– SaM Apr 9 at 7:25.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.