well, depends a lot on the enterprise and its workflow. About tests arquillian can already do a lot (multiple containers, multiple archives...)
About deployment, deploying from jenkins through mvn seems quite common today but using just a jenkins hook to do so is maybe easier and more "portable" (accross servers). *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/4/2 James Green <james.mk.gr...@gmail.com> > This leads nicely into something I'm about to approach. We have a few maven > based projects. I'd like to avoid having to manually deploy the build > artifacts onto the respective QA VMs and perform the QA'ing of the > components together. > > Sounds nicer to build a maven project that depends on each artifact and has > tests that run across the deployed instances. proj-1.qa.mydomain and > proj-2.qa.mydomain for instance. > > So I was considering building just such a project but using maven to > remotely deploy each artifact into each TomEE instance then run the tests. > Before I try, is this considered "normal" practice or there are better > ways? > > By moving in this direction I'm rather hoping to automate with Jenkins! > > > > On 2 April 2013 10:24, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > > > FYI https://issues.apache.org/jira/browse/TOMEE-880 > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > *Github: https://github.com/rmannibucau* > > > > > > > > 2013/4/2 Romain Manni-Bucau <rmannibu...@gmail.com> > > > > > i was looking to it since i already have the code > > > > > > about aether that's the lib we use to get mvn dependencies. > > > > > > Here is the pattern used: > > > > > > > > > mvn:[repository_url!]groupId/artifactId[/[version]/[type]] > > > > > > > > > *Romain Manni-Bucau* > > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > > > *Blog: **http://rmannibucau.wordpress.com/*< > > http://rmannibucau.wordpress.com/> > > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > > > *Github: https://github.com/rmannibucau* > > > > > > > > > > > > 2013/4/2 og0815 <oliver.guent...@gg-net.de> > > > > > >> Hi, > > >> > > >> > Mvn works with remote repo too and custom repo can be in the url > (see > > >> > aether). > > >> > > >> What's aether ? > > >> > > >> > DeployerEjb doesnt handle remote deployment passing url (remote > > >> deployment > > >> > is used in tomee for cluster deployment). > > >> > > >> > Could be done but not the original goal of deploy goal. > > >> Ok, i might look into this and supply a patch. > > >> > > >> > > >> > > >> > > >> -- > > >> View this message in context: > > >> > > > http://openejb.979440.n4.nabble.com/maven-tomee-plugin-and-remote-deploy-tp4661806p4661886.html > > >> Sent from the OpenEJB User mailing list archive at Nabble.com. > > >> > > > > > > > > >
