As I said: STK looks in the repo _first_ and only looks in the classpath, if the resource is defined in the repo and its "bypass" checkbox is checked. What we often do is simply add empty resource nodes to the resources repo, check the "bypass" checkbox and then work with the resources in the classpath. Of course you will need to export these resource nodes and add them to your bootstrap folder for a proper module installation.
-will On 22.03.2012, at 13:23, Dominik Berger wrote: > Thanks Will for your quick respronse! > Actually this is not what i am looking for, the question is, how are > resources existing in the class path deployed to the repo? > I was actually expecting them to just be loaded when they exist in the > classpath, but i have seen, it is necessery to laod them via > bootstraping and adding an task in the version handler. > > Do you know if this is by default loaded if on module loading? > > Thanks and best regards > > dom > > ----- Ursprüngliche Mail ----- > Von: "Will Scheidegger" <[email protected]> > An: "Magnolia User-List" <[email protected]> > Gesendet: Donnerstag, 22. März 2012 12:16:45 > Betreff: Re: [magnolia-user] resource file loading by initialising of modules > > Hi Dominik > > > Resources (e.g. CSS files) can exist in the class path (i.e. > src/main/resources/templating-kit/themes/...) AND in the resources repository > (Menu "Templating-Kit" > "Resources"), which is not the same. STK looks in > the resources repository _first_. If you want to use the resources in the > class path you will still have to add a corresponding resource node to the > resources repository and configure it to be "bypassed": > > > > Hope this helps. > > > -will > > > > On 22.03.2012, at 10:59, Dominik Berger wrote: > > > > Hi all, > > we are trying to add some new resources files to the resources files in Admin > Central. > In the module the files are beneath > src/main/resources/templating-kit/themes... but in AdminCentral the resources > are not there. > Also after deleting the module version, the module itself and so on. > > Do we have to change something in the VersionHandler of the module? Or are we > something missunderstanding? > > Thanks for your ideas and best regards, > > Dominik > > > > -- > Freundliche Grüsse > > Dominik Berger > Senior IT Consultant > > > > bluesky IT-Solutions AG > Kaspar Pfeiffer-Strasse 4 > CH- 4142 Münchenstein > > Phone +41 61 415 21 00 > Mobile +41 79 276 41 16 > Web www.bluesky-it.ch > Mail [email protected] > > > ---------------------------------------------------------------- > For list details, see > http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: < [email protected] > > ---------------------------------------------------------------- > > > > > > ---------------------------------------------------------------- > For list details, see > http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
