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. > Hmmmm, 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] > > __________________________________________________ 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]
