It is actually explained there http://tomee.apache.org/tomee-maven-plugin.html
path is the archive path to deploy and the server application path to undeploy (logged when deployed). This complexity comes from the remote support. Locally I think everybody uses run/debug and it makes things easier from experience than trying to match old EE server development lifecycle (start the server on the morning and deploy/redeploy the whole day). Also avoids surprises when you restart the next day ;). Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-12-04 12:37 GMT+01:00 MarkD <[email protected]>: > I shall take your advice and use run/debug. If you are able to quickly > detail > the deploy/undeploy process, that may be useful, but don't worry if you are > busy. > > Thank-you for helping. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/maven-plugin-error-tp4677110p4677136.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
