Request: Tutorial on SVN Project layouts

[emishz]

I basically want to make a 'fork' of L2J and add all my own custom enhancements etc to it - but also be able to keep in sync with your & everyone else of the main L2J project team. I'm not too familiar with SVN and the power of subversion - simply the checkout, edit, update etc.

This is kind of the map I want to setup for my design pattern - it's just not clicking in my head the proper way to set it up & maintain everything.

I'm not sure if your familiar with http://www.assembla.com but they have an SVN control for groups of team members on a particular project - regardless heres the map:


[ L2J Main Server Repository ]
|
| - Able to update to the latest L2J revision to keep sync.
| - Reference code somehow stored on Assembla and able to keep sync.
|
[ My Reference code ]
|
| - Able to 'merge' ( ? ) my custom content into the head project.
|
[ My Fork Project of L2J ]
|
\ _ [ Developer 1's work ]
|
| - Need a way to have all developers check out my fork's code & able to update it.
|
\ _ [ Developer 2's work ]

Anyway, thanks for any help from anyone.

[JIV]

eclipse have support for merging repositories but with more rework it will become more unusable so you will have to do it manually.

[emishz]

Thanks for the heads up