Announcement Announcement Module
Collapse
No announcement yet.
Standard Svn structure for Bundles Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Standard Svn structure for Bundles

    Is there any standard svn structure for maintaing code in SVN

    We see that there are two approaches , is there any advantage in terms of maintainance , versioning , parallel release etc

    Usecase :
    Com
    Com.test.package1
    Com.test.package2
    Com.test.package3

    Assuming we have package structure like – and we want package1 and package2 to be part of bundle and package 3 to be part of bundle 2 . How should the svn structure look like

    Option1

    Bundle1

    Trunk/
    Com.test.package1

    Com.test.package2
    Config
    META-INF
    /spring/ xmls…


    Bundle2
    Trunk/
    Com.test.package3
    Config
    META-INF
    /spring/ xmls…

    Option2
    Blabla/
    Trunk/
    Com.test.package1
    Com.test.package2
    Com.test.package3
    Config
    META-INF1
    /spring/ xmls…
    META-INF2
    /spring/ xmls

    Now the build.xml decides which config to be added when building the bundle

    Is there any recommended standard ?

  • #2
    one advantage i figured out with 2nd approach is that it is easier to maintian when we have multiple versions of teh bundle.

    In approach1 there will be redundancy.

    Comment

    Working...
    X