• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Multi-Module large project building problem

 
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
VenGard ERP description: VenGard ERP has 20 module mentioned this figure. One module depends on other module. Like: Sales depends three module on inventory, order management, accounting.
So, My JAVA EE EAR structure is: Every module is EJB jar . for building project we use maven . for one module , one programmer is responsible.

Problem is: Development time problem


Building time related problem : When occur a business problem (changes) in one module , we need to build all module .
it takes lot of time (5 mins) for building EAR File in development time . in some moment it is very critical .


Building time Error : when a programmer try to fixing a bug for a particular module (inventory), he need to build all module . so, if occur any building error from other module(sales)
he cannot identified easily from other module bug in EAR file building time .

My Expectation : when problems comes from a particular module , we want to build and test only this module not all module , it save lot of time and hassle .



We want to build all modules only one time (release, regression test).



please help me ?


p22.png
[Thumbnail for p22.png]
p11.png
[Thumbnail for p11.png]
 
Ranch Hand
Posts: 378
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
See if this approach might help you..

Consider using a Continous Integration (CI) environment with jenkins combined with your scm and a nexus repository so that jenkins will publish build artifacts in to nexus. When you do a maven build maven should download and cache your dependencies e.g. sales-core etc. and in subsequent builds the build will use the downloaded artifacts now in your local repository. You can use the maven release plugin through jenkings to manage your release procedure. On committs to scm or releasing there would be a new download during a local build but this should be a one time activity for a given commit or release. Hope this helps..
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic