I have made a joomla component that I want to put on SVN. The problem is that Joomla components have bits and pieces scattered all over the place. What is the best way to handle this with SVN considering I still want to be able to version the application, without including all the core joomla code website code?
I ended up using symlinks in Window 7 like Linux has
http://www.howtogeek.com/howto/windows-vista/using-symlinks-in-windows-vista/
And a nice utility for making linking really easy http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html
You can have the project exactly as you would have it in the installer and link the directories and language files to their respective place in the Joomla hierarchy. This also allows you to have multiple Joomla version installed and using a single repository your can test them all! Works great :)
This is how I organise my component files within my svn. Assume that my component name is comname.
repository/components/comname/trunk/
comname
comname_admin
com_comname.xml
com_comname-1.0.zip
license.txt
comname_userguide.doc
comname_userguide.pdf
All your front end code should be in comname folder while all your admin code should be in comname_admin. This is the standard way in which to layout a Joomla component structure.
You can then tag your versions and keep them in repository/components/comname/tags/1.0 for example.
Hope that helps. Cheers
One way of doing it would be to create the necessary empty directory structure and place your custom files in there.
Your Joomla component should be largely self-contained. In some cases you may have a library but really the only people who should creating libraries are if you have multiple components, plugins, and modules that need to share code.
Version the com_mycomponent folder - everything you need should be that folder. If you have files scattered all over the file system then there's a problem with your component design.
EDIT - Also, I've found its easier to version the entire Joomla installation. As the number of extensions you've written goes up, this reduces the number of folders you need to hunt down and click "commit"/"update". Version your entire site, and that way you can just commit the entire thing in go.