Hi Benoît, I've made some progress over the coming days following similar steps to those you describe below.
One thing I can help with is your questions with respect to eh Javascript, images, CSS. 1st thing you need to do is to make a decision as to whether you want to store these resources in the file system or the repository. I think STK stores these in the repository, but for my projects, I find it easier to maintain these on the file system. In that case, to include these web resource in your you module you just need to place them in this directory format of the module and Magnolia will automatically extract them from the JAR and put them in the right place. See the sample module for an example: magnolia-module-samples\src\main\resources\mgnl-files\docroot\samples\samples.css puts this file in here when the module is installed apache-tomcat-5.5.27\webapps\magnoliaAuthor\docroot\samples\samples.css I hope that helps. If you want to store these in the repository, then I'm sure you can just add them into the appropriate repository and location, export the XML and package that XML in your module similar to this sample one: magnolia-module-samples\src\main\resources\mgnl-bootstrap-samples\samples\website.products-freemarker.xml I will keep this mailing list posted as my team and I learn more... Cheers, Brent -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Benoit Segaert Sent: Wednesday, 15 July 2009 5:54 PM To: Magnolia User-List Subject: RE: [magnolia-user] Developing Magnolia Projects using SVN Brent, I currently starting a new project with the version 4.1. I followed the same reflection. I effectively started with the Maven archetype that create an example of module. It helps you to generate a new module. By default, it generate a module with the name mymodule. I changed it to the project name. It is the startup to publish code into Magnolia. My module is maintained in SVN. As I want to use the Templating Kit, I checkout the templating kit modules. I quickly understood how to deploy new templates and paragraphs in the Templating Kit. But I still working on the deployment of the javascript, images and CSS. I probably need to create a new theme module like the magnolia-theme-pop module. Unfortunately, the Templating Kit is not yet documented. So, I will be happy if we can exchange our different investigations Benoît -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Brent McArthur Sent: lundi 13 juillet 2009 12:36 To: Magnolia User-List Cc: Magnolia User-List Subject: Re: [magnolia-user] Developing Magnolia Projects using SVN Thanks for that Igor. We're using magnolia 4.1. Based on what you've said it sounds like I've been thinking about this in the wrong way. Are you saying that developing even the most basic websites that only have a few templates / dialogs you should always package those sites as jar modules and deploy them in the same way I did forthe STK? For some strange reason I had in my head that modules are only used for deploying websites that need java components (to integrate with a 3rd party web service for example) Cheers Brent On 13/07/2009, at 7:05 PM, "Igor Klimer" <[email protected]> wrote: > > I'm not sure I understood you correctly but you can store all the > things you mentioned in your filesystem - no need to keep it in JCR > (imho, that doesn't have much advantages, that's why I "extracted" all > the templates, dialog definitions, etc, to the filesystem and can put > them under SCM). > You do this by simply changing the addresses of all the relevant > resources to point to files existing in for example your docroot. > You didn't write which version of Magnolia you are working with but > for example thhh 3.6.x branch has an Maven archetype for modules that > would give you a ready-to-work-with module structure. For more recent > versions, like 4.1.x I found that looking at existing modules on SVN > is the best way to go. > > HTH & best regards, > Igor Klimer > > > On Mon, Jul 13, 2009 at 10:04 AM, Brent McArthur<[email protected] > > wrote: >> Hi Everyone, >> >> >> >> I've found this mailing list really helpful in learning Magnolia s >> o 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]> >> ---------------------------------------------------------------- >> > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
