I'm not quite sure I follow. Between eclipse:eclipse, install:install-file, the maven dependencies plugin and the various options you have with the POM, I haevn't had a reason to code a custom eclipse plugin.
Every one of my dependencies is managed inside the POM.xml file and I am using WSAD 5.1 (based on Eclipse 2.1) -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 Kathryn Huxtable <[EMAIL PROTECTED]> 04/18/2006 12:46 PM Please respond to "Maven Users List" To: Maven Users List <[email protected]> cc: Subject: Re: Using maven to setup Eclipse plugin project Our Ref: Your Ref: But it doesn't do what one really wishes if one is using the M2Eclipse plugin in eclipse, which is to get the dependencies from the POM file. A fairly standard .classpath file using the M2Eclipse plugin would look something like: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="src" path="src/main/java"/> <classpathentry kind="src" path="src/main/resources"/> <classpathentry output="target/test-classes" kind="src" path="src/test/java"/> <classpathentry output="target/test-classes" kind="src" path="src/test/resources"/> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/> <classpathentry kind="output" path="target/classes"/> </classpath> See the difference? I find the eclipse plugin in Maven to be irrelevant, unless I'm distributing the project to another institution. -K -- Kathryn Huxtable Middleware Architect Core Middleware Information Technology, a division of Information Services The University of Kansas On 4/18/06 2:31 PM, "Mark Misurak" <[EMAIL PROTECTED]> wrote: > Yes, there's a Maven plugin called Eclipse. Run the default goal just > once at the commandline, and your .classpath will be set for you. Just > don't forget to set the MAVEN_REPO variable in your build path before > you do so (Window -> Preferences -> Java -> Build Path -> Classpath > Variables). If you're using Maven 2, set the M2_REPO variable instead. > >>>> [EMAIL PROTECTED] 04/18/06 2:22 pm >>> > > Hello K. > > Thank you for the reply. I need everyone in our team to run maven and > setup > the plugin project in Eclipse. I cannot expect them to change .classpath > file manually. Does maven have a command maven eclipse plugin or > something > like that, so we can import the plugin project with its plugin > dependency > into Eclipse?? > > Thanks, > Hua > -- > View this message in context: > http://www.nabble.com/Using-maven-to-setup-Eclipse-plugin-project-t1468793.htm > l#a3974975 > Sent from the Maven - Users forum at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > This email and/or any documents in this transmission is intended for the > addressee(s) only and may contain legally privileged or confidential > information. Any unauthorized use, disclosure, distribution, copying or > dissemination is strictly prohibited. If you receive this transmission in > error, please notify the sender immediately and return the original. > > Ce courriel et tout document dans cette transmission est destiné à la personne > ou aux personnes à qui il est adressé. Il peut contenir des informations > privilégiées ou confidentielles. Toute utilisation, divulgation, distribution, > copie, ou diffusion non autorisée est strictement défendue. Si vous n'êtes pas > le destinataire de ce message, veuillez en informer l'expéditeur immédiatement > et lui remettre l'original. > > --------------------------------------------------------------------- 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. ***************************************************************
