Hi Adam, Sorry I missed your reply, only saw it now.
Basically my requirements is that I'm am developing APIs that will be shared across different WARs, along with an integration with Pluto & J2 that needs it's JARs deployed to the shared classloader. I want to avoid manual copy as I want to automate this for building fully functional deployments for QA and distribution. We have this process running fine in Maven 1, but I must admit it is a hard transition for me to Maven 2. In Maven 1 I simply used dependency properties to mark the libraries as "shared", and had to be careful to maintain version consistency. In Maven 2 I am cleaning this process by using a top project for these dependencies, but I'm still running into the problem of packaging these dependencies properly, and only these. Ideally I would like to have something like this : appserver:deploy-shared-libs And this would automatically deploy shared libraries into Tomcat 5.5, Tomcat 6, Websphere and Weblogic. Any assistance on this topic would be really welcome. I hope it is clearer. Regards, Serge Huber. On Dec 22, 2007 8:53 PM, Adam Hardy <[EMAIL PROTECTED]> wrote: > Hi Serge, > > it's a bit unclear what your aim is here, or rather your requirements. > > You have one project or more? When running a deploy to the server, m2 > would > generally speaking just deploy a WAR file to the server's deploy > directory, e.g. > webapps in tomcat 5 & 6. > > If you are building several projects which would need to share jars that > you > want to put in a webserver's common directory, then do it manually. What > reason > do you have to redeploy such common jars? If they are dependencies of > several > projects, then it seems you require maven to maintain version consistency > across > several projects and to determine what versions of projects were already > deployed, which seems unreasonably complicated. I doubt there is a plugin > which > does such a thing. > > Regards > Adam > > Serge Huber on 20/12/07 14:54, wrote: > > Hi all, > > > > I am in the process of converting a rather complex project from Maven 1 > to > > Maven 2, and despite my best attempts at googling for these answers, I > have > > only been able to go so far. I've also been looking at some projects, > like > > Jetspeed 2, that seems to be doing some rather advanced stuff with Maven > 2. > > > > Anyway, in our existing Maven 1 project, we use Jelly scripts to perform > > deployment of "common" resources to our Tomcat server. The problem is > that > > Tomcat has been moving around things in the latest versions, and > deployment > > of common resources is different between Tomcat 5.5 and 6. In Tomcat 5.5we > > would copy the required dependencies manually to tomcat/shared/lib, but > I > > didn't really think this was the cleanest way of doing this. > > > > As I am re-organizing our project structure for Maven 2, I was building > a > > "common" sub-project with all the dependencies, which is cleaner than > what > > we use to do, but I know have no idea how best to deploy these, > especially > > based on the different locations for different Tomcat versions. Should I > use > > the tomcat-maven-plugin ? Should I use Cargo ? Which one of the two has > the > > biggest community ? If I should build my own Mojo, is there a > recommended > > way to build deployment plugins, using maybe profiles to make it as > server > > independent as possible ? Lots of questions as you can see :) > > > > I really hope someone out there can help, because I can't believe I'm > the > > only one having this issue :) > > > > cheers, > > Serge... > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
