Hi Everyone, I've found this mailing list really helpful in learning Magnolia so I thought I would try my luck again.
Myself and my team have now done a successful demonstration to a client using Magnolia and we are proceeding to a proper project based on Magnolia which I'm stoked about. However, as with all of our other Java based projects I want to ensure all of our code is properly version controlled. Does anyone have any suggestions as to how best setup a project where changes can be made using eclipse and checked in to SVN? To give you a more detailed list of what I want managed by SVN: 1. JSP templates 2. JSP paragraphs 3. Template definitions 4. Paragraph definitions 5. Dialogues 6. Other repository configuration 7. Any java classes we write Basically, I want to be able to checkin all "non-content" related project information into SVN so we can tag, branch, etc. What do you all recommend for doing this? For our demo we did manual import and export of sections of the appropriate repository but in larger projects with larger teams this is just not sustainable. The overheads are too much. Do we need to write a bunch of scripts to do it or do they already exist? Any help would be much appreciated! Thanks, Brent ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
