Best practice for version control of a custom open source project

Question

I am using an open source Java project and had to make some changes to our site. I downloaded the source code through Subversion, changed two files and created a custom JAR file. Now I need to save these user changes in the OUR Subversion version control system. What is the best way to do this?

Should I check the whole marked open source version on our system and then create a branch with our change in it? Or should I just register our user files and rely on an open source tag to always be around? Or maybe something else?

Answer 1

Take a look at the Subversion vendor branches , which are designed to "support [custom] third-party data modifications in your own version control system." It looks like what you want. You must create a vendor branch for an open source Java project in your main repo (from their latest version of SVN to your changes). Then check your modifications. In the future, you can unite in upward changes.

Answer 2

Subversion is free and available online , with a section on repository layout choices .

Subversion - " " , , : trunk, ; , ; , , , .

, , .

Answer 3

, , , ( ...)

, .