version control - Recommended way to organize JSF big application on daily builds -



version control - Recommended way to organize JSF big application on daily builds -

we working in big team, building web application in jsf, each developer develops new task. example: user management, security, scheme parameters etc.

we need create daily task build war svn.

we know how utilize daily builder, svn etc.

our question how save per module? recommended way build packages web application jsf it's build on mvc module , pages part of bean? should utilize many wars/packages?

i need save per module, since days there errors in 1 module shouldn't uploaded rest of modules. (i know how compile , find decide if upload or not).

you utilize "work branch(es)" (or "module branches") in development of module occur. trunk contain everything, developers working on given "module branch" merge trunk work every day publish trunk 1 time work done (done includes tests passing). like (picture version command multiple agile teams):

the above image illustrates "work branches" per team approach 1 imagine using finer grained approach , utilize work branches per modules. principles similar.

then set trunk , "work branches" under continuous integration.

version-control web-applications jsf continuous-integration dailybuilds

Comments

Popular posts from this blog

java - How to set log4j.defaultInitOverride property to false in jboss server 6 -

c - GStreamer 1.0 1.4.5 RTSP Example Server sends 503 Service unavailable -

Using ajax with sonata admin list view pagination -