Refer to the Pentaho resource library structure for project resource management_yanchunlili’s blog

Recently, due to the need for data analysis, I was studying Pentaho, and additionally found that its resource library structure was very reasonable, so I modified my own project resource library as a reference.

In fact, the Pentaho resource library structure is consistent with the ideas written in “The Way of Version Control – Using CVS”, but it is more intuitive and easy to refer to through this example. It creates three subdirectories under each project directory : [b]trunk (trunk), branches (branch), tags (marker)[/b]. There are two types of branches in branches: [b] release branch (such as 1.2), experimental branch (such as upgrade-to-jboss-portal-2.4) [/b], the naming method of the branch is worth referring to, stored in tags by Component versions automatically generated by continuous integration tools such as CruiseControl and manually marked versions.

[img]http://www.iteye.com/topics/download/fd7d130a-80a2-40e8-80d8-77fc1aaf2fb9[/img]