Re: Not building EAR for an application

2006-02-27 Thread Emmanuel Venisse
Ah, you have one cvs modules by project module. It's really strange to use this structure in CVS, generally a CVS module is used for a complete project with some subdirectories for project modules. In your case, you can't use a parent pom without some work. I have 2 work around: - Refactor you

Re: Not building EAR for an application

2006-02-26 Thread Emmanuel Venisse
ok you don't use the standard maven layout. If you want to build all in one time, you should add a new pom in the root directory of your parent pom and add one module in it (the parent pom), so all your modules will be checkout in the correct directory structure Emmanuel Sanjay Choudhary a é

Re: Not building EAR for an application

2006-02-25 Thread Sanjay Choudhary
Hi Emmanuel I like option 2 and I tried it too but it doesn't work My Parent pom has module definition as below: ../common ../ejb1 ../ejb2 ../war1 ../java1 ../ear But since Continuum uses number instead of folder name -N option doesn't work. Is th

Re: Not building EAR for an application

2006-02-25 Thread Emmanuel Venisse
Actually a build start only if you have some changes in scm for your project. In future, we'll can start a build if a dependecies is new. If you want the latest EAR, without changes in your EAR project, you must build it manually from Continuum. or you can build all from parent project if you r

Not building EAR for an application

2006-02-24 Thread Sanjay Choudhary
Hi All, We hv. and application building thru continuum Our application is a normal J2EE application pom.xml EAR Project EJB1 Project EJB2 Project Jar Project Jar Project War Project Each of them has pom.xml. Now if we have change in Jar Project and EJB1 project, continuum builds the proj