I've found that the eclipse:eclipse task works very nicely at setting up your workspace as WSAD is built upon Eclipse. I would imagine RAD is no different but I have no exposure to RAD.
The only other things you'll need to do are: Add a Java -> classpath variable in your settings to "M2_REPO" pointing to your local repository Change the settings in Java -> Compiler to "allow using multiple output locations for source folders" HTH... also Mike, in all fairness, the nabble archives and whatnot are not all that easy to find or use (and not spidered all that well in google). If you have nothing good to say, don't say anything at all. -j --------------------------------------------------- Justin Fung [EMAIL PROTECTED] Sr. Analyst, Business Systems IT Banking Systems, e-Business HSBC Bank Canada http://www.hsbc.ca p: (604) 643-6605 f: (604) 643-6727 "Serge Emmanuel Pagop" <[EMAIL PROTECTED]> 04/18/2006 06:53 AM Please respond to "Maven Users List" To: "Maven Users List" <[email protected]> cc: Subject: Re: Maven and WSAD or RAD Our Ref: Your Ref: Which local env. do u like to get at (runtime, compile, ...) ? On 4/18/06, Mike Perham <[EMAIL PROTECTED]> wrote: > > Please check the archives. This has been discussed ad infinitum. > > -----Original Message----- > From: Aaron Freeman [mailto:[EMAIL PROTECTED] > Sent: Monday, April 17, 2006 10:54 PM > To: Maven > Subject: Maven and WSAD or RAD > > Is anyone using Maven with either WebSphere Studio Applicaiton Developer > or Rational Application Developer? If so, how do you get the local > environments to work properly? There are some things that the local > environment needs to run, that are different than the way you would do > it for a Maven project. For instance, if you have a web project, you > have to put all the JAR files in the src/main/webapp/web-inf/lib folder > in order for them to be included in the runtime path for the local > environment. But as far as Maven goes, you shouldn't be putting these > files in that fold because it does that for you when it generates the > target. There is a similar issue with putting JAR files in the root of > the EAR file project, also. I've come up with some ways to get around > some of this, but it's really just a hack. > > Does anyone know of a good way to deal with this? > > Thanks!! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > *************************************************************** This email may contain confidential information, and is intended only for the named recipient and may be privileged. Distribution or copying of this email by anyone other than the named recipient is prohibited. If you are not the named recipient, please notify us immediately and permanently destroy this email and all copies of it. Internet email is not private, secure, or reliable. No member of the HSBC Group is liable for any errors or omissions in the content or transmission of this email. Any opinions contained in this email are solely those of the author and, unless clearly indicated otherwise in writing, are not endorsed by any member of the HSBC Group. *************************************************************** Ce courriel peut renfermer des renseignements confidentiels et privilégiés et s'adresse au destinataire désigné seulement. La distribution ou la copie de ce courriel par toute personne autre que le destinataire désigné est interdite. Si vous n'êtes pas le destinataire désigné, veuillez nous en aviser immédiatement et détruire de façon permanente ce courriel ainsi que toute copie de celui-ci. La transmission de courriel par Internet ne constitue pas un mode de transmission confidentiel, sécuritaire ou fiable. Aucun membre du Groupe HSBC ne sera responsable des erreurs ou des omissions relatives au contenu ou à la transmission de ce courriel. L'auteur de ce courriel est seul responsable des opinions émises dans ce courriel, lesquelles, à moins d'un avis contraire fourni par écrit, ne sont pas endossées par aucun membre du Groupe HSBC. ***************************************************************
