We're updating the issue view to help you get more done. 

Only check / offset port numbers for configuration properties prefixed with "cargo."


See: https://groups.google.com/d/msgid/codehaus-cargo/CAKumxByRiQhKv8219N%2BwJEgDYqdNOWGMAHzNODqNQ0MtKCfKmA%40mail.gmail.com?utm_medium=email&utm_source=footer

The Cargo port checker is useful as it checks whether ports are in use before starting a container - Which avoids dark issues later on. Unfortunately, in case a properties file is used for Cargo and for external services, Cargo can check port numbers outside its scope. For example, one could be defining one file with all port numbers:

1 2 3 4 5 6 7 cargo.servlet.port=9888 cargo.tomcat.ajp.port=9889 cargo.rmi.port=9890 spring.mail.host=localhost #comment out the port and the problem does not occur spring.mail.port=15025

... and Cargo will check the servlet, AJP and RMI ports (which is good), and the SMTP port (which doesn't name sense).

Only check port numbers for configuration properties prefixed with cargo. to avoid this issue.



S. Ali Tokmen


S. Ali Tokmen


Fix versions