Good day, That or simply removing the test projects from your parent's list of modules. Removing your test projects from the parent's module list will prevent mvn deploy from acting on your test projects. But of course, the drawback would be that any other maven command done on your parent project will no longer reach thoes test projects as well.
Cheers, Franz Arnaud Bailly-3 wrote: > > "Jochen Wiedmann" <[EMAIL PROTECTED]> writes: > >> Hi, >> >> I have a parent project (Apache XML-RPC) with several childs: common, >> client, server, and tests. >> >> When deploying, they are all transmitted to the server. For obvious >> reasons, I do not want the tests to be published, so I remove the >> tests folder from the repository later on. However, the best solution >> would be, if I could tell the maven-deploy-plugin not to deploy the >> tests project at all. >> >> Is that possible? Another thrick to achieve the same goal? >> > > Hi, > You could use profiles: they allow you to control modules. Something > like this: > > (profiles > (profile > (id 'testing') > (modules (module 'my-module') > )))) > > Then you can > mvn -P testing test > > or > mvn deploy > > HTH > -- > OQube < software engineering \ génie logiciel > > Arnaud Bailly, Dr. > \web> http://www.oqube.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/How-not-to-deploy-a-project--tf2691005s177.html#a7555819 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
