hmm, you find eclipse easier but tomee mvn plugin is far better to work in a team because you share in your project your tomee.xml in a standard place and calling mvn tomee:run it is automatically used where in eclipse you need to put it manually in the right server project. Then that's just habits i think.
*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/6/3 pierrepinon <ppi...@smaeur.eu> > Hi, > > Thank you for your message, > > But it's annoying to not have integrated solution (Eclipse Server Adapter) > to deploy on TomEE like we have with Tomcat, Glassfish, ... > > Because I have TomEE server with a custom ActiveMQ Broker (activemq.xml), > queues, connection pool, SSL connector, custom JVM options and it's easier > to work with adapter linked to a local TomEE server. > > But it is not clear to work with several people with this solution. > > Maybe in the future... > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Tomee-Plus-and-EAR-debugging-in-Eclipse-tp4663415p4663429.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
