Skip to Content
avatar image
Former Member

component dependency and fullback procedure

Hi, we have deployment questions regarding to component dependency and fallback procedure. We have 3 web projects under development and a shared component that would be shared among the 3 projects. Our question is:

  1. The 3 projects are mutual independent in functional, except the shared component. In common practice, are we recommended to seperate them into 4 tracks (3 for projects and 1 for shared component)?
  2. The shared component has many released revisions. The 3 projects wish to depend on different component revision. How do we achieve it? for example, shared component has rev.1, rev.2, rev.3, project A use rev.1, project B use rev. 2, project C use rev.3. The kind of practice iscommonly using in Marven2 or tranditional J2EE WAR project (put in WEB-INF/lib).
  3. Continue 2, how do we achieve in production runtime?
  4. Once deployed in prouduction and found mis-functional as expect, how do we fullback to previous revision?


Thanks for the help.

Jack

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 25, 2012 at 11:07 AM

    are they deployed to same server?

    if you want to achieve 2, 4 track are needed.

    Add comment
    10|10000 characters needed characters exceeded