Using maven in eclipse
I see lot of discussion using maven eclipse plugin to import the project in eclipse. I am wondering why we need to do this as m2eclipse seems to be working perfectly fine and works directly with pom file. So far, m2eclipse has worked flawlessly for me. Is there a preferred plugin to use because of drawbacks/issues in other? Thanks, Niranjan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using maven in eclipse
On Tue, Jul 5, 2011 at 3:31 PM, Niranjan Rao nhr...@gmail.com wrote: I see lot of discussion using maven eclipse plugin to import the project in eclipse. I am wondering why we need to do this as m2eclipse seems to be working perfectly fine and works directly with pom file. So far, m2eclipse has worked flawlessly for me. Is there a preferred plugin to use because of drawbacks/issues in other? maven eclipse plugin (m-e-p) predates m2e. For a lot of people it works well enough and there is little benefit it reconfiguring their tooling to take advantage of m2e. For others some of the more complicated builds don't work as expected in m2e but work fine in m-e-p. YMMV. If you are happy with m2e, I wouldn't worry about m-e-p except to remember its in your tool box if you happen to need it. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using maven with eclipse
Hi Farrukh, If you're interested in development that involves the maven-eclipse-plugin, I created a series of tutorials (80+) a few months ago that cover Java development using Eclipse and Maven. The main approach using this technique is to execute maven commands on projects via Eclipse external tool configurations (so that you can click on a project and run a maven goal on that project). In this approach, Eclipse/Maven integration is very minimal (you basically let maven be maven most of the time). Topics include Eclipse user libraries, web applications, and a multi-module project. The tutorials are located at: http://www.avajava.com/tutorials/categories/maven http://www.avajava.com/tutorials/categories/maven If you're interested in tightly integrated features rather than the bare bones approach, the m2eclipse plugin is great. The ability to search for classes and automatically add a dependency to your project in Eclipse is a really fantastic feature. Deron Eriksson -- View this message in context: http://www.nabble.com/Using-maven-with-eclipse-tp21478705p21498725.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using maven with eclipse
Hello, I am experienced with maven but new to Eclipse IDE. I have used maven with Netbeans IDE and the mevenide Netbeans plugin. WHat I liked about it was how Netbeans was completely driven by the pom configuration and how natural and familiar everything was for a maven user. I would like to try Eclipse IDE with my existing multi-module project. What is the best approack for doing this? Which plugin should I use? Please share any links and pointers. Thanks. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using maven with eclipse
On Thursday 15 January 2009 Farrukh Najmi wrote: I am experienced with maven but new to Eclipse IDE. I have used maven with Netbeans IDE and the mevenide Netbeans plugin. WHat I liked about it was how Netbeans was completely driven by the pom configuration and how natural and familiar everything was for a maven user. I would like to try Eclipse IDE with my existing multi-module project. What is the best approack for doing this? Which plugin should I use? Please share any links and pointers. Thanks. See [0] for a comparison of the available plugins. The maven-eclipse-plugin just creates eclipse configuration files for your projects, no further intergration. This is simple, quite robust but doesn't provide as much comfort as the other two options. I didn't use m2eclipse or q4e recently but they follow a completely different approach. They are plugins for eclipse and try to adapt your IDE and add new features to it. If you search the list archive you should find some more information. This question is asked every now and then. hth, - martin [0] http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration signature.asc Description: This is a digitally signed message part.
RE: Using maven with eclipse
Try this if you want an Eclipse plug-in to manage the integration: http://m2eclipse.sonatype.org/ [1] Try this if you want a Maven plug-in instead: http://maven.apache.org/plugins/maven-eclipse-plugin/ [2] I tend to lean to [2], but then I'm happier just using command line mojos to get some of the additional value add that's in [1] (and it does have some pretty slick features, which you'll see if you try it). For example, I'd do something like mvn dependency:tree deps.log etc. Just feels like an instinctively lighter approach which I prefer. Adam -Original Message- From: Farrukh Najmi [mailto:farr...@wellfleetsoftware.com] Sent: 15 January 2009 14:30 To: users@maven.apache.org Subject: Using maven with eclipse Hello, I am experienced with maven but new to Eclipse IDE. I have used maven with Netbeans IDE and the mevenide Netbeans plugin. WHat I liked about it was how Netbeans was completely driven by the pom configuration and how natural and familiar everything was for a maven user. I would like to try Eclipse IDE with my existing multi-module project. What is the best approack for doing this? Which plugin should I use? Please share any links and pointers. Thanks. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Using maven with eclipse
Adam Leggett wrote: I tend to lean to [2], but then I'm happier just using command line mojos to get some of the additional value add that's in [1] (and it does have some pretty slick features, which you'll see if you try it). For example, I'd do something like mvn dependency:tree deps.log etc. Just feels like an instinctively lighter approach which I prefer. The m2eclipse provides a nice an interactive UI for that command. You can see how it look like at http://docs.codehaus.org/display/M2ECLIPSE/Maven+POM+editor#MavenPOMeditor-DependencyHierarchyviewer The upcoming m2eclipse 0.9.7 release should be very exiting. The following wiki page provides and overview of the new and noteworthy features http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy#NewandNoteworthy-latest regards, Eugene -- View this message in context: http://www.nabble.com/Using-maven-with-eclipse-tp21478705p21480290.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using maven with eclipse
there's also Eclipse IAM (formerly Q4E) http://code.google.com/p/q4e/ re: dependency tree, I use all the time Q4E dependency analysis http://code.google.com/p/q4e/wiki/DependencyAnalysis On Thu, Jan 15, 2009 at 3:43 PM, Adam Leggett adam.legg...@upco.co.uk wrote: Try this if you want an Eclipse plug-in to manage the integration: http://m2eclipse.sonatype.org/ [1] Try this if you want a Maven plug-in instead: http://maven.apache.org/plugins/maven-eclipse-plugin/ [2] I tend to lean to [2], but then I'm happier just using command line mojos to get some of the additional value add that's in [1] (and it does have some pretty slick features, which you'll see if you try it). For example, I'd do something like mvn dependency:tree deps.log etc. Just feels like an instinctively lighter approach which I prefer. Adam -Original Message- From: Farrukh Najmi [mailto:farr...@wellfleetsoftware.com] Sent: 15 January 2009 14:30 To: users@maven.apache.org Subject: Using maven with eclipse Hello, I am experienced with maven but new to Eclipse IDE. I have used maven with Netbeans IDE and the mevenide Netbeans plugin. WHat I liked about it was how Netbeans was completely driven by the pom configuration and how natural and familiar everything was for a maven user. I would like to try Eclipse IDE with my existing multi-module project. What is the best approack for doing this? Which plugin should I use? Please share any links and pointers. Thanks. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
I have a multi-module project and I am trying to get the right set up to use Maven with Eclipse. I have a question below on mvn eclipse:eclipse, but some background first. I used to use m2eclipse with Eclipse 3.1 but as the projects have grown, m2eclipse has shown to have problems. For example in a multi-module project, each module might want different versions of a jar file in the path (say in different WAR files). m2eclipse seems to load all the different source directories up into one mega-project, and come up with a single list of all dependencies flattened across projects. When m2eclipse worked, I sometimes got different versions of artifacts in the dependency list. Frequently it just refused to work, not finding all the dependencies correctly - which is probably a bug. However regardless of any possible bugs, the basic premise seems wrong - each module should have its own dependencies worked out as they may *want* different versions of jar files. mvn eclipse:eclipse therefore looks a better way to go. I can check out a SVN tree, run mvn eclipse:eclipse, then load up all the modules as separate projects with only the jar file dependencies for that module included. This works much more reliably - no problems so far. However, because it creates a project per module, I cannot use the global Eclipse SVN support for tagging, branching, switching etc. I cannot do this from the top of the tree. I have to go back to the command line. I just downloaded Eclipse Europa (3.3) and it (as well as 3.2 I believe) supports nested projects. That is, it appears I can have a .project file in the root directory plus one in each module directory. (I am having a little trouble with Subclipse and Subversive, but I think they will be resolved so I am going to assume they work.) This looks almost ideal, which leads me to finally to my question... Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Eclipse can now handle nested projects, so it will load them all up (it used to refuse to load up child directory projects under a parent directory project). I saw a hack somewhere of changing the root pom file to temporarily use jar packaging, then put it back to pom packaging - but this is pretty ugly. Now that Eclipse supports nested projects, is there any reason not to do this? It would give me the ability to do all the svn commands from inside Eclipse from the root package (I don't need or want to compile any Java code from the root package - I just want to be able to explore the tree, do 'sync with repository', commits, svn switches etc) plus each module would get its own correct dependency list as occurs now. I would do all compiles in the module directories. Is this possible now? (I don't think so.) Can it be added? Would it allow what I am trying to do? Thanks! Alan Kent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
Alan Kent wrote: Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Not that I know of, but this works for me: 1. Check out the parent module into your workspace. 2. mvn eclipse:eclipse to create the various .project and .classpath files in the sub-modules. 3. Switch to the Java perspective in Eclipse. 4. Select the parent module and hit F5 to refresh (just for grins). 5. Choose File-Import..., Existing Projects into Workspace, and browse in your workspace into your parent module. 6. Select one of the sub-modules, make sure Copy projects into workspace is /not/ checked, and hit Finish. 7. Lather, rinse, and repeat steps 5 and 6 with the other submodules. In this way, you can do all of your SCM in Eclipse via the parent module, yet play with the submodules as proper Java projects. As far as I know, this is the recommended way to develop a multi-module project with Eclipse. Someone please correct me if I'm wrong. -- -Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
An interesting message on the Maven User's list, especially for those (Daryoush!) who have expressed frustration about the inability to mass-perforce-enable all those Eclipse projects that you get when using mvn eclipse:eclipse. I'm not sure I understand completely where he's coming from, but basically it seems like a way to maintain an RRmodules Eclipse project, for the purpose of SCM, and also a bunch of subprojects, for mvn eclipse:eclipse. I'm not positive that this mixture of things will cause Perforce to always check things out automatically if the RRmodules project is Perforce-enabled and the others are not, but it seems worth a try, because it seems to be working for this guy, and I doubt he'd be so enthusiastic if that part didn't work. The downside, which I have discovered myself by accident, is that with this setup you can no longer mass-import Eclipse projects at the RRmodules level, but instead have to do your importing iteratively, one level down. Not a big deal for ongoing updates, but somewhat of a pain the very first time. Happy 4th! Especially to Balazs, who's actually working today, presumably because his East European upbringing didn't instill an irresistable compulsion to grill something outdoors on this special day. -- Bryan -Original Message- From: Greg Thompson [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 5:53 AM To: Maven Users List Subject: Re: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects Alan Kent wrote: Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Not that I know of, but this works for me: 1. Check out the parent module into your workspace. 2. mvn eclipse:eclipse to create the various .project and .classpath files in the sub-modules. 3. Switch to the Java perspective in Eclipse. 4. Select the parent module and hit F5 to refresh (just for grins). 5. Choose File-Import..., Existing Projects into Workspace, and browse in your workspace into your parent module. 6. Select one of the sub-modules, make sure Copy projects into workspace is /not/ checked, and hit Finish. 7. Lather, rinse, and repeat steps 5 and 6 with the other submodules. In this way, you can do all of your SCM in Eclipse via the parent module, yet play with the submodules as proper Java projects. As far as I know, this is the recommended way to develop a multi-module project with Eclipse. Someone please correct me if I'm wrong. -- -Greg - 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]
RE: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
Sorry. Not intended for the list. Apologies. -Original Message- From: Bryan Loofbourrow [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 2:43 PM To: *Qpass - Content Catalog Discussion Cc: Maven Users List Subject: FW: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects An interesting message on the Maven User's list, especially for those (Daryoush!) who have expressed frustration about the inability to mass-perforce-enable all those Eclipse projects that you get when using mvn eclipse:eclipse. I'm not sure I understand completely where he's coming from, but basically it seems like a way to maintain an RRmodules Eclipse project, for the purpose of SCM, and also a bunch of subprojects, for mvn eclipse:eclipse. I'm not positive that this mixture of things will cause Perforce to always check things out automatically if the RRmodules project is Perforce-enabled and the others are not, but it seems worth a try, because it seems to be working for this guy, and I doubt he'd be so enthusiastic if that part didn't work. The downside, which I have discovered myself by accident, is that with this setup you can no longer mass-import Eclipse projects at the RRmodules level, but instead have to do your importing iteratively, one level down. Not a big deal for ongoing updates, but somewhat of a pain the very first time. Happy 4th! Especially to Balazs, who's actually working today, presumably because his East European upbringing didn't instill an irresistable compulsion to grill something outdoors on this special day. -- Bryan -Original Message- From: Greg Thompson [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 5:53 AM To: Maven Users List Subject: Re: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects Alan Kent wrote: Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Not that I know of, but this works for me: 1. Check out the parent module into your workspace. 2. mvn eclipse:eclipse to create the various .project and .classpath files in the sub-modules. 3. Switch to the Java perspective in Eclipse. 4. Select the parent module and hit F5 to refresh (just for grins). 5. Choose File-Import..., Existing Projects into Workspace, and browse in your workspace into your parent module. 6. Select one of the sub-modules, make sure Copy projects into workspace is /not/ checked, and hit Finish. 7. Lather, rinse, and repeat steps 5 and 6 with the other submodules. In this way, you can do all of your SCM in Eclipse via the parent module, yet play with the submodules as proper Java projects. As far as I know, this is the recommended way to develop a multi-module project with Eclipse. Someone please correct me if I'm wrong. -- -Greg - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven as Eclipse class-path container
On Tue, 8 Nov 2005, [iso-8859-1] Jörg Schaible wrote: A problem might be that eclipse doesn't have the concept of scopes for its dependencies. It has. You can define dependencies to be exported. Isn't that on by default? And does that provide for 'test' dependencies not being visible in the main sources? And for 'runtime' dependencies not being visible in main/test sources, but only runtime? Btw I think that the maven2 plugin for eclipse will provide this support. It's not public yet and in the early stages of development. -- Kenney - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven as Eclipse class-path container
Kenney Westerhof wrote on Tuesday, November 08, 2005 9:25 AM: On Tue, 8 Nov 2005, [iso-8859-1] Jörg Schaible wrote: A problem might be that eclipse doesn't have the concept of scopes for its dependencies. It has. You can define dependencies to be exported. Isn't that on by default? And does that provide for 'test' dependencies not being visible in the main sources? And for 'runtime' dependencies not being visible in main/test sources, but only runtime? OK. I have to redefine my statement. You can explicitly export your dependencies, but your source folders are unfortunately always exported (unfortunately). This forces test cases always into the classpath of the child projects :( - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using Maven as Eclipse class-path container
Hi, I'd like to know if there is, or if there are any plans to create, an Eclipse plugin that cann add a Maven2 class-path container to a project, so there is a way to use the Maven artifact resolver (adding dependencies automatically to the Eclipse classpath) inside Eclipse. This would be especially useful for transitive depencies... The idea for this stems from the Necessitas Ivy plugin for Eclipse: http://kevin.oneill.id.au/2005/06/06/necessitas-jar-management-for-eclipse Are there any informations about this topic? Maybe the soon-to-be released M2 Eclipse plugin (http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do this? Thanks, Michael Böckling - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Maven as Eclipse class-path container
On 11/8/05, Michael Böckling [EMAIL PROTECTED] wrote: Are there any informations about this topic? Maybe the soon-to-be released M2 Eclipse plugin (http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do this? Correct, and more. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Maven as Eclipse class-path container
Sounds like a good idea. I think the eclipse plugin works only in the opposite direction, generating .classpath etc files for eclipse to use. A problem might be that eclipse doesn't have the concept of scopes for its dependencies. Marcel --- Michael Böckling [EMAIL PROTECTED] wrote: Hi, I'd like to know if there is, or if there are any plans to create, an Eclipse plugin that cann add a Maven2 class-path container to a project, so there is a way to use the Maven artifact resolver (adding dependencies automatically to the Eclipse classpath) inside Eclipse. This would be especially useful for transitive depencies... The idea for this stems from the Necessitas Ivy plugin for Eclipse: http://kevin.oneill.id.au/2005/06/06/necessitas-jar-management-for-eclipse Are there any informations about this topic? Maybe the soon-to-be released M2 Eclipse plugin (http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do this? Thanks, Michael Böckling - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven as Eclipse class-path container
Marcel Schutte wrote on Tuesday, November 08, 2005 8:48 AM: Sounds like a good idea. I think the eclipse plugin works only in the opposite direction, generating .classpath etc files for eclipse to use. A problem might be that eclipse doesn't have the concept of scopes for its dependencies. It has. You can define dependencies to be exported. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best approach in using maven w/ eclipse
Thanks. I am also using Maven 1.0.2. I havent really looked at the newer version of Maven and I having been trying to get Maven 1.0.2 to work for my project. Hopefully it isnt too different. For the tomcat configuration, you've just added a context in conf/server.xml? I'll try that tomorrow. I think that its a better flow than what I have as I'd like a reduced develop-deploy-test cycle. The maven tomcat plugin is good but Once you have installed the application you can see modifications to the app reflected in the container by calling the tomcat:reload task. as stated on http://www.codeczar.com/products/maven-tomcat-plugin/index.html. I dont really want to be calling the tomcat:reload task every single time I make a change to say a jsp. I agree, I will be creating an artifact for each project. I still need to deploy it either as ear or if needs be as independendent wars. Also possibly in the future, I may need to include this wars in other ears. So basically, I have created something like this in eclipse: WebProjectA WebProjectB WebProjectC ModelProjectA EnterpriseProjectA EnterpriseProjectA will be my enterprise application that will just have an META-INF/application.xml with my project.xml. I've gotten it to work and not sure if its the proper thing to do. My steps: 1) I've modified application.xml to include the necessary artifacts. 2) Generated the artifact for each one individually (which I find a little time consuming but maybe there's already a plugin that someone can recommend or maybe script without using the multiproject plugin) 3) Installed all the artifacts into my local maven repository 4) Executed the maven ear:ear goal. Im still working with it, but if anyone has done something similar, please do discuss. Thanks. Jade --- Doug Douglass [EMAIL PROTECTED] wrote: Yes, Sysdeo Tomcat plugin. Web app work flow is similar to what you describe, but we have Tomcat and the Tomcat plugin configured to use context configuration files and just point the context to the target/artifactId directory of the webapp project. Therefore, the work flow is: 1) make a change in Eclipse 2) Start Tomcat, if it isn't already started 3) execute maven war:webapp 4) test/refresh in browser 5) repeat Most changes are picked up automatically by Tomcat, though some are not (e.g., changes to Spring beans configuration), so I may add the clean goal as part of the maven command, or just restart Tomcat. Though, as I think about it, using a Maven plugin may make more sense as it's configuration travels in the POM instead of in the IDE configuration. H, I'll have to play with the Maven tomcat plugin. As for use of multiproject, we don't have all the Maven sub-projects in one Eclipse project. We have one Eclipse project per Maven sub-project, separating out almost everything but presentation from the webapp project. The only downside to this is not being able to have an Eclipse project for the Maven parent project. Though, all that's in the parent project is project.xml, project.properties, Eclipse java code/style templates, and a license/header file (for checkstyle plugin). Each sub-project sets the maven.multiproject.type property approrpiately (e.g., maven.multiproject.type=war:war for the webapp, maven.multiproject.type=jar:jar for most of the others) Perhaps I could set maven.multiproject.type=jar:deploy or some such for the other projects? Haven't tried. Can't help you out with EAR projects, we haven't done any. From what I've read on this list it appears similar to the multi-project layout we've already got. We try very hard to stick with the Maven mantra one artifact, one project. We've found that only the most trivial project are hindered by this, and that it has helps us design more and better reusable packages. Cheers, DD P.S. All of this is with Maven 1.0.2. jk jk wrote: Thanks Doug. For the tomcat plugin, Im presumming your referring to the Sysdeo tomcat plugin. I also have that installed in eclipse and use it to start stop tomcat. Can you list down the flow of how you would make a change in your webapp and deploy it when actively developing? For example, this is what Im doing. 1) Make a change in eclipse 2) Using the Systedo tomcat plugin in eclipse, start tomcat 3) Open command prompt, execute maven tomcat:install 4) Test out change in browser. 5) Make a change in eclipse again if I want to 6) In command prompt, execute maven tomcat:reload 7) Test out change in browser. Also, Im trying to setup something similar to what you had done with the multiproject. But to use multiproject in eclipse, I would have to create one root project and create 4 subprojects within that project. I dont really want to do that as I still want to have separate projects within eclipse which means I will opt not to use multiproject. Can someone show me an example of an
RE: Best approach in using maven w/ eclipse
Yes, I agree. I think because I will be using Maven
on the command prompt more often, I will use the maven
script you provided. Thanks Alex.
Jade
--- A. Shneyderman [EMAIL PROTECTED] wrote:
If you run command line I can not see the need for
tomcat plugin. Just make
maven assemble and deploy your application.
The following maven.xml works magic for me:
?xml version=1.0?
project xmlns:ant=jelly:ant
goal name=app:deploy prereqs=war:war
ant:unwar
src=${maven.build.dir}/${pom.artifactId}.war
dest=${tomcat.home}/webapps/${pom.artifactId} /
/goal
goal name=app:redeploy
prereqs=app:deploy,app:stop,app:start /
goal name=app:start prereqs=app:anttaskdefs
ant:start url=${tomcat.manager.url}
username=${tomcat.manager.username}
password=${tomcat.manager.password}
path=/${pom.artifactId} /
/goal
goal name=app:stop prereqs=app:anttaskdefs
ant:stop url=${tomcat.manager.url}
username=${tomcat.manager.username}
password=${tomcat.manager.password}
path=/${pom.artifactId} /
/goal
goal name=app:list prereqs=app:anttaskdefs
ant:list url=${tomcat.manager.url}
username=${tomcat.manager.username}
password=${tomcat.manager.password}
/
/goal
goal name=app:anttaskdefs
ant:taskdef name=list
classname=org.apache.catalina.ant.ListTask
ant:classpath
ant:pathelement
path=${tomcat.home}/server/lib/catalina-ant.jar /
/ant:classpath
/ant:taskdef
ant:taskdef name=stop
classname=org.apache.catalina.ant.StopTask
ant:classpath
ant:pathelement
path=${tomcat.home}/server/lib/catalina-ant.jar /
/ant:classpath
/ant:taskdef
ant:taskdef name=start
classname=org.apache.catalina.ant.StartTask
ant:classpath
ant:pathelement
path=${tomcat.home}/server/lib/catalina-ant.jar /
/ant:classpath
/ant:taskdef
/goal
/project
You will need to create some maven vars for it to
work. In your home
directory setup a build.properties file and include
the following:
tomcat.home=C:/tc4131
tomcat.manager.url=http://localhost:8080/manager
tomcat.manager.username=user
tomcat.manager.password=secret
apps.dir=webapps
And yeah enable manager on tomcat if you try to make
any use of the goals
above.
By the way the same worked out even with mavenIDE
that way you do not even
have to do any CTRL+TAB to switch to maven prompt.
Alex.
-Original Message-
From: jk jk [mailto:[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 3:21 PM
To: Maven Users List
Subject: Re: Best approach in using maven w/ eclipse
Thanks Doug. For the tomcat plugin, Im presumming
your referring to the
Sysdeo tomcat plugin. I also have that installed in
eclipse and use it to
start stop tomcat. Can you list down the flow of
how you would make a
change in your webapp and deploy it when actively
developing? For example,
this is what Im doing.
1) Make a change in eclipse
2) Using the Systedo tomcat plugin in eclipse, start
tomcat
3) Open command prompt, execute maven tomcat:install
4) Test out change in browser.
5) Make a change in eclipse again if I want to
6) In command prompt, execute maven tomcat:reload
7) Test out change in browser.
Also, Im trying to setup something similar to what
you had done with the
multiproject. But to use multiproject in eclipse, I
would have to create one
root project and create 4 subprojects within that
project. I dont really
want to do that as I still want to have separate
projects within eclipse
which means I will opt not to use multiproject. Can
someone show me an
example of an eclipse EAR project that uses maven
to build the dependencies
on the projects within eclipse?
Thanks.
Jade
--- Doug Douglass [EMAIL PROTECTED] wrote:
Jade,
We used to use MyEclipse but have let our
subscriptions lapse on
purpose. In general, I think MyEclipse is a decent
set of features for
the $$$, though the XML editor seemed a bit buggy.
We have found we can
do more with less (maven, mavenide, Tomcat plugin,
etc) as you seem to
have found. While at first the MyEclipse way of
allowing editting of
webapp content (e.g., jsp, etc) in place seems a
time saver, it
presumes there is no build process for any
RE: Best approach in using maven w/ eclipse
Hi Patrick, WTP does sound pretty good and I might try it out down the road. When you were using MyEclipse or maybe this actually applies to just eclipse, do you need to execute, maven eclipse goal to generate the MAVEN_REPO variables in the build path every single time you add a dependency in your project.xml? Also, when I run maven eclipse goal and I refresh my eclipse project, it removes all my natures/capabilites (hibernate, struts, etc) for my project which is very annoying. I have to add those natures/capabilites to the project again. Does this happen to you? Thanks. Jade --- Patrick Roumanoff [EMAIL PROTECTED] wrote: Hi, I don't know if it's of any interest to you, but I managed to use the newly released WTP (http://www.eclipse.org/webtools/ )to do just that. I like WTP a lot as with my setup it seems much faster/stable than myEclipse for jsp editing. Moreover the deployement is much closer to a real one because it allows you to build the dependant jars and use the maven repository, as maven would do, but within eclipse. With WTP you get a real build process to a have a working webapp (copy files across, assemble jar, copy maven dependencies). WTP also deploys the webapp to the webserver of your choice (tomcat included) But it doesn't come free, you have to configure this build process in a new format (.wtpmodules). It's still a bit of a pain to configure, but I think it's worth the effort. What would be nice is to have either the eclipse maven plugin or the mevenide eclipse plugin updated to generate/synchronize those .wtpmodules for you. details at http://roumanoff.blogspot.com/ cheers, Patrick -Original Message- From: Doug Douglass [mailto:[EMAIL PROTECTED] Subject: Re: Best approach in using maven w/ eclipse The risk associated with this presumption is that there typically (hopefully always) IS a build process, but it is being subverted. Anyone know if there is a Tomcat Eclipse plugin that allows you to edit JSP live in the IDE (i.e. hit the page, make a change and refresh the browser)? I ask because a co-worker showed me that it is possible in IDEA. Repeating your workflow below 100 times as you are authoring and testing a complex page rapidly grows tiresome. NOTICE This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Best approach in using maven w/ eclipse
Have you considered looking at the documentation for the eclipse plugin? ;-) Google maven eclipse and look at the properties. -Original Message- From: jk jk [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 26, 2005 3:08 AM To: Maven Users List Subject: RE: Best approach in using maven w/ eclipse Also, when I run maven eclipse goal and I refresh my eclipse project, it removes all my natures/capabilites (hibernate, struts, etc) for my project which is very annoying. I have to add those natures/capabilites to the project again. Does this happen to you? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Best approach in using maven w/ eclipse
-Original Message- From: jk jk [mailto:[EMAIL PROTECTED] WTP does sound pretty good and I might try it out down the road. When you were using MyEclipse or maybe this actually applies to just eclipse, do you need to execute, maven eclipse goal to generate the MAVEN_REPO variables in the build path every single time you add a dependency in your project.xml? The MAVEN_REPO variable is an eclipse classpath variable. I use mevenide to synchronize my project.xml with my .classpath And yes, I need to syncronize everytime a dependency is added (either in .classpath or in project.xml). Also, when I run maven eclipse goal and I refresh my eclipse project, it removes all my natures/capabilites (hibernate, struts, etc) for my project which is very annoying. I have to add those natures/capabilites to the project again. Does this happen to you? If you are using the eclipse maven plugin you have to regenerate your eclipse project files every time you modify your project.xml. To avoid loosing your natures builders, you can use the maven.eclipse.projectnatures maven.eclipse.buildcommands properties. But this is a one way process. With mevenide it's a two way process and you won't loose your nature as only .classpath and project.xml are updated. cheers, Patrick NOTICE This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best approach in using maven w/ eclipse
Thanks Doug. For the tomcat plugin, Im presumming your referring to the Sysdeo tomcat plugin. I also have that installed in eclipse and use it to start stop tomcat. Can you list down the flow of how you would make a change in your webapp and deploy it when actively developing? For example, this is what Im doing. 1) Make a change in eclipse 2) Using the Systedo tomcat plugin in eclipse, start tomcat 3) Open command prompt, execute maven tomcat:install 4) Test out change in browser. 5) Make a change in eclipse again if I want to 6) In command prompt, execute maven tomcat:reload 7) Test out change in browser. Also, Im trying to setup something similar to what you had done with the multiproject. But to use multiproject in eclipse, I would have to create one root project and create 4 subprojects within that project. I dont really want to do that as I still want to have separate projects within eclipse which means I will opt not to use multiproject. Can someone show me an example of an eclipse EAR project that uses maven to build the dependencies on the projects within eclipse? Thanks. Jade --- Doug Douglass [EMAIL PROTECTED] wrote: Jade, We used to use MyEclipse but have let our subscriptions lapse on purpose. In general, I think MyEclipse is a decent set of features for the $$$, though the XML editor seemed a bit buggy. We have found we can do more with less (maven, mavenide, Tomcat plugin, etc) as you seem to have found. While at first the MyEclipse way of allowing editting of webapp content (e.g., jsp, etc) in place seems a time saver, it presumes there is no build process for any of that content. This quickly turned out not to be the case on the project we purchased the subscriptions for, which led to a very awkward build/deploy process that we, unfortunately, had to expose to our customer. Toward the end of that project, I switched to maven for the build (multiproject with 4 interrelated subprojects) and have never looked back. Yes, during development with Eclipse I almost always have a command prompt up for running maven goals. It's what I'm used to doing I have not used the tomcat plugin for Maven, only the one for Eclipse and it seems to work fine. HTH, Doug jk jk wrote: Hi all, Im getting setup to use Maven on a new project and would like to know the best approach in intergrating Maven with development, specifically using Eclipse (w/ MyEclipse plugin). Its usually a preference thing, but any feedback would assist me. After working with Maven goals on Eclipse as opposed to command prompt, I find it faster to use the command prompt then executing maven goals in eclipse. The only thing with this approach is that you would always need a command prompt while you're developing rather just dealing with your IDE. Do most use the command prompt to execute maven goals? When developing and then testing the web app, I find it easy to use myeclipse to allow me to automatically deploy my web app in exploded archive in Tomcat. But once you adhere to Maven's recommended directory structure, it doesnt work with Myeclipse. So I've resorted to using the Tomcat plugin for Maven (using the maven tomcat:install or tomcat:reload goals). But even then, it sometimes doesnt work. Does anyone have the same issue? Thanks. Jade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Best approach in using maven w/ eclipse
If you run command line I can not see the need for tomcat plugin. Just make
maven assemble and deploy your application.
The following maven.xml works magic for me:
?xml version=1.0?
project xmlns:ant=jelly:ant
goal name=app:deploy prereqs=war:war
ant:unwar src=${maven.build.dir}/${pom.artifactId}.war
dest=${tomcat.home}/webapps/${pom.artifactId} /
/goal
goal name=app:redeploy prereqs=app:deploy,app:stop,app:start /
goal name=app:start prereqs=app:anttaskdefs
ant:start url=${tomcat.manager.url}
username=${tomcat.manager.username}
password=${tomcat.manager.password}
path=/${pom.artifactId} /
/goal
goal name=app:stop prereqs=app:anttaskdefs
ant:stop url=${tomcat.manager.url}
username=${tomcat.manager.username}
password=${tomcat.manager.password}
path=/${pom.artifactId} /
/goal
goal name=app:list prereqs=app:anttaskdefs
ant:list url=${tomcat.manager.url}
username=${tomcat.manager.username}
password=${tomcat.manager.password}
/
/goal
goal name=app:anttaskdefs
ant:taskdef name=list
classname=org.apache.catalina.ant.ListTask
ant:classpath
ant:pathelement
path=${tomcat.home}/server/lib/catalina-ant.jar /
/ant:classpath
/ant:taskdef
ant:taskdef name=stop
classname=org.apache.catalina.ant.StopTask
ant:classpath
ant:pathelement
path=${tomcat.home}/server/lib/catalina-ant.jar /
/ant:classpath
/ant:taskdef
ant:taskdef name=start
classname=org.apache.catalina.ant.StartTask
ant:classpath
ant:pathelement
path=${tomcat.home}/server/lib/catalina-ant.jar /
/ant:classpath
/ant:taskdef
/goal
/project
You will need to create some maven vars for it to work. In your home
directory setup a build.properties file and include the following:
tomcat.home=C:/tc4131
tomcat.manager.url=http://localhost:8080/manager
tomcat.manager.username=user
tomcat.manager.password=secret
apps.dir=webapps
And yeah enable manager on tomcat if you try to make any use of the goals
above.
By the way the same worked out even with mavenIDE that way you do not even
have to do any CTRL+TAB to switch to maven prompt.
Alex.
-Original Message-
From: jk jk [mailto:[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 3:21 PM
To: Maven Users List
Subject: Re: Best approach in using maven w/ eclipse
Thanks Doug. For the tomcat plugin, Im presumming your referring to the
Sysdeo tomcat plugin. I also have that installed in eclipse and use it to
start stop tomcat. Can you list down the flow of how you would make a
change in your webapp and deploy it when actively developing? For example,
this is what Im doing.
1) Make a change in eclipse
2) Using the Systedo tomcat plugin in eclipse, start tomcat
3) Open command prompt, execute maven tomcat:install
4) Test out change in browser.
5) Make a change in eclipse again if I want to
6) In command prompt, execute maven tomcat:reload
7) Test out change in browser.
Also, Im trying to setup something similar to what you had done with the
multiproject. But to use multiproject in eclipse, I would have to create one
root project and create 4 subprojects within that project. I dont really
want to do that as I still want to have separate projects within eclipse
which means I will opt not to use multiproject. Can someone show me an
example of an eclipse EAR project that uses maven to build the dependencies
on the projects within eclipse?
Thanks.
Jade
--- Doug Douglass [EMAIL PROTECTED] wrote:
Jade,
We used to use MyEclipse but have let our subscriptions lapse on
purpose. In general, I think MyEclipse is a decent set of features for
the $$$, though the XML editor seemed a bit buggy.
We have found we can
do more with less (maven, mavenide, Tomcat plugin,
etc) as you seem to
have found. While at first the MyEclipse way of allowing editting of
webapp content (e.g., jsp, etc) in place seems a time saver, it
presumes there is no build process for any of that content.
This quickly turned
out not to be the case on the project we purchased the subscriptions
for, which led to a very awkward build/deploy process that we,
unfortunately, had to expose to our customer. Toward the end of that
project, I switched to maven
Re: Best approach in using maven w/ eclipse
Yes, Sysdeo Tomcat plugin. Web app work flow is similar to what you describe, but we have Tomcat and the Tomcat plugin configured to use context configuration files and just point the context to the target/artifactId directory of the webapp project. Therefore, the work flow is: 1) make a change in Eclipse 2) Start Tomcat, if it isn't already started 3) execute maven war:webapp 4) test/refresh in browser 5) repeat Most changes are picked up automatically by Tomcat, though some are not (e.g., changes to Spring beans configuration), so I may add the clean goal as part of the maven command, or just restart Tomcat. Though, as I think about it, using a Maven plugin may make more sense as it's configuration travels in the POM instead of in the IDE configuration. H, I'll have to play with the Maven tomcat plugin. As for use of multiproject, we don't have all the Maven sub-projects in one Eclipse project. We have one Eclipse project per Maven sub-project, separating out almost everything but presentation from the webapp project. The only downside to this is not being able to have an Eclipse project for the Maven parent project. Though, all that's in the parent project is project.xml, project.properties, Eclipse java code/style templates, and a license/header file (for checkstyle plugin). Each sub-project sets the maven.multiproject.type property approrpiately (e.g., maven.multiproject.type=war:war for the webapp, maven.multiproject.type=jar:jar for most of the others) Perhaps I could set maven.multiproject.type=jar:deploy or some such for the other projects? Haven't tried. Can't help you out with EAR projects, we haven't done any. From what I've read on this list it appears similar to the multi-project layout we've already got. We try very hard to stick with the Maven mantra one artifact, one project. We've found that only the most trivial project are hindered by this, and that it has helps us design more and better reusable packages. Cheers, DD P.S. All of this is with Maven 1.0.2. jk jk wrote: Thanks Doug. For the tomcat plugin, Im presumming your referring to the Sysdeo tomcat plugin. I also have that installed in eclipse and use it to start stop tomcat. Can you list down the flow of how you would make a change in your webapp and deploy it when actively developing? For example, this is what Im doing. 1) Make a change in eclipse 2) Using the Systedo tomcat plugin in eclipse, start tomcat 3) Open command prompt, execute maven tomcat:install 4) Test out change in browser. 5) Make a change in eclipse again if I want to 6) In command prompt, execute maven tomcat:reload 7) Test out change in browser. Also, Im trying to setup something similar to what you had done with the multiproject. But to use multiproject in eclipse, I would have to create one root project and create 4 subprojects within that project. I dont really want to do that as I still want to have separate projects within eclipse which means I will opt not to use multiproject. Can someone show me an example of an eclipse EAR project that uses maven to build the dependencies on the projects within eclipse? Thanks. Jade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Best approach in using maven w/ eclipse
Anyone know if there is a Tomcat Eclipse plugin that allows you to edit JSP live in the IDE (i.e. hit the page, make a change and refresh the browser)? I ask because a co-worker showed me that it is possible in IDEA. Repeating your workflow below 100 times as you are authoring and testing a complex page rapidly grows tiresome. mike -Original Message- From: Doug Douglass [mailto:[EMAIL PROTECTED] Sent: Monday, July 25, 2005 3:11 PM To: Maven Users List Subject: Re: Best approach in using maven w/ eclipse Yes, Sysdeo Tomcat plugin. Web app work flow is similar to what you describe, but we have Tomcat and the Tomcat plugin configured to use context configuration files and just point the context to the target/artifactId directory of the webapp project. Therefore, the work flow is: 1) make a change in Eclipse 2) Start Tomcat, if it isn't already started 3) execute maven war:webapp 4) test/refresh in browser 5) repeat Most changes are picked up automatically by Tomcat, though some are not (e.g., changes to Spring beans configuration), so I may add the clean goal as part of the maven command, or just restart Tomcat. Though, as I think about it, using a Maven plugin may make more sense as it's configuration travels in the POM instead of in the IDE configuration. H, I'll have to play with the Maven tomcat plugin. As for use of multiproject, we don't have all the Maven sub-projects in one Eclipse project. We have one Eclipse project per Maven sub-project, separating out almost everything but presentation from the webapp project. The only downside to this is not being able to have an Eclipse project for the Maven parent project. Though, all that's in the parent project is project.xml, project.properties, Eclipse java code/style templates, and a license/header file (for checkstyle plugin). Each sub-project sets the maven.multiproject.type property approrpiately (e.g., maven.multiproject.type=war:war for the webapp, maven.multiproject.type=jar:jar for most of the others) Perhaps I could set maven.multiproject.type=jar:deploy or some such for the other projects? Haven't tried. Can't help you out with EAR projects, we haven't done any. From what I've read on this list it appears similar to the multi-project layout we've already got. We try very hard to stick with the Maven mantra one artifact, one project. We've found that only the most trivial project are hindered by this, and that it has helps us design more and better reusable packages. Cheers, DD P.S. All of this is with Maven 1.0.2. jk jk wrote: Thanks Doug. For the tomcat plugin, Im presumming your referring to the Sysdeo tomcat plugin. I also have that installed in eclipse and use it to start stop tomcat. Can you list down the flow of how you would make a change in your webapp and deploy it when actively developing? For example, this is what Im doing. 1) Make a change in eclipse 2) Using the Systedo tomcat plugin in eclipse, start tomcat 3) Open command prompt, execute maven tomcat:install 4) Test out change in browser. 5) Make a change in eclipse again if I want to 6) In command prompt, execute maven tomcat:reload 7) Test out change in browser. Also, Im trying to setup something similar to what you had done with the multiproject. But to use multiproject in eclipse, I would have to create one root project and create 4 subprojects within that project. I dont really want to do that as I still want to have separate projects within eclipse which means I will opt not to use multiproject. Can someone show me an example of an eclipse EAR project that uses maven to build the dependencies on the projects within eclipse? Thanks. Jade - 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]
RE: Best approach in using maven w/ eclipse
Hi, I don't know if it's of any interest to you, but I managed to use the newly released WTP (http://www.eclipse.org/webtools/ )to do just that. I like WTP a lot as with my setup it seems much faster/stable than myEclipse for jsp editing. Moreover the deployement is much closer to a real one because it allows you to build the dependant jars and use the maven repository, as maven would do, but within eclipse. With WTP you get a real build process to a have a working webapp (copy files across, assemble jar, copy maven dependencies). WTP also deploys the webapp to the webserver of your choice (tomcat included) But it doesn't come free, you have to configure this build process in a new format (.wtpmodules). It's still a bit of a pain to configure, but I think it's worth the effort. What would be nice is to have either the eclipse maven plugin or the mevenide eclipse plugin updated to generate/synchronize those .wtpmodules for you. details at http://roumanoff.blogspot.com/ cheers, Patrick -Original Message- From: Doug Douglass [mailto:[EMAIL PROTECTED] Subject: Re: Best approach in using maven w/ eclipse The risk associated with this presumption is that there typically (hopefully always) IS a build process, but it is being subverted. Anyone know if there is a Tomcat Eclipse plugin that allows you to edit JSP live in the IDE (i.e. hit the page, make a change and refresh the browser)? I ask because a co-worker showed me that it is possible in IDEA. Repeating your workflow below 100 times as you are authoring and testing a complex page rapidly grows tiresome. NOTICE This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Best approach in using maven w/ eclipse
Hi all, Im getting setup to use Maven on a new project and would like to know the best approach in intergrating Maven with development, specifically using Eclipse (w/ MyEclipse plugin). Its usually a preference thing, but any feedback would assist me. After working with Maven goals on Eclipse as opposed to command prompt, I find it faster to use the command prompt then executing maven goals in eclipse. The only thing with this approach is that you would always need a command prompt while you're developing rather just dealing with your IDE. Do most use the command prompt to execute maven goals? When developing and then testing the web app, I find it easy to use myeclipse to allow me to automatically deploy my web app in exploded archive in Tomcat. But once you adhere to Maven's recommended directory structure, it doesnt work with Myeclipse. So I've resorted to using the Tomcat plugin for Maven (using the maven tomcat:install or tomcat:reload goals). But even then, it sometimes doesnt work. Does anyone have the same issue? Thanks. Jade ___ Post your free ad now! http://personals.yahoo.ca - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
