Hi everyone, Thanks to Sachin Patel I've had a look today at the WST/JST API for wrapping servers and I've noticed that there's a clear overlap with Cargo (http://cargo.codehaus.org). Actually I've known about WTP for some time (I even sent an email in may 2005 to propose some collaboration but unfortunately I never got an answer) but it's only this morning that I started looking into it in more details.
Cargo is a framework I've started about a year and half ago with the goal of offering a Java API for manipulating servers (we call them containers). Cargo offers a API for starting, stopping, configuring containers and deploying modules to them. It has a core API and quite a lot of container implementations. Cargo's main goal is to make it easy for anyone who needs to manipulate containers, like IDEs, automated builds, etc. Cargo is meant to be agnostic to its execution environment so that users can use it all different kinds of situations. However we've implemented some extensions that use the Cargo Java API. For example we have Ant tasks, maven1 plugin, maven2 plugin, netbeans and intellij IDEA plugins, etc. All those extensions are generic and using the core Cargo Java API. While reading http://www.eclipse.org/webtools/wst/components/server/api_concepts.html this morning I realized how similar the Cargo and the WST API are. I thought I should discuss this with you and see what are the options and how we could possibly collaborate instead of redoing the same things... WDYT? Do you think there's some possibility of collaboration? I'm very open to any idea. Thanks a lot -Vincent _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
