Rémy, count yourself lucky you don't have to use OC4J. :-) I really wasn't aware of Cargo. Me and my co-workers' search for a oc4j maven plugin never came up with Cargo.
I was able to briefly look at Cargo since Rémy pointed it out. The functionality provided by this plugin does not exist in Cargo since the the OC4J containers do not* *support a remote container. AFAIK, there's no reason it couldn't be done. The current Cargo OC4J containers do not support remote containers. Cargo certainly looks great if you need to embed a container or use it for functional testing. It does look a bit more complex if you're simply needing to deploying/undeploying local and remote containers. It took a little bit of digging before I could find the documentation on how to make this work. The application server maven plugins currently hosted by codehaus are easy to find and very easy to configure and get working. I saw a need for both my workplace as well as others looking for something like this. Since we couldn't find a suitable solution, I put this together outside of work and figured I'd be nice for others to get some use out of it. I am wondering why maven plugins for jboss, tomcat, and websphere exist here if they could just be implemented in Cargo? On Tue, Mar 31, 2009 at 10:56 AM, Markus Knittig <[email protected]> wrote: > On 03/31/2009 01:07 PM, Rémy Sanlaville wrote: > > > I'm not using OC4J, but why don't create a OC4J implementation for Cargo > > rather than create a specific plugin ? > > Maybe because Cargo already supports OC4J... > > Best regards, > Markus > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
