Afaik, Felix can already load exploaded bundles - and I guess this integration into Eclipse shouldn't be too hard. Maybe my previous wording was not good, I think this is an important area where we're currently lacking tooling, however I wouldn't see this as Sling's primary goal to provide tools for that; I would rather love to reuse others work.
Carsten 2013/6/3 Robert Munteanu <romb...@apache.org> > On Mon, 2013-06-03 at 14:21 +0200, Dominik Süß wrote: > > When skipping Javacode and Bundles (which I'm not so happy with) one > option > > would also be to have something like a ResourceProvider that for "dev" > time > > redirects and takes data from the FS. As long as we have the mentioned > same > > machine scenario the synchronisation is IMHO not necessary, better have a > > FS Resourceprovider that gets more capabilities than the current one. IDE > > support could even have some trigger to switch between FS-mode and > > Repo-Mode with an automatic deployment/push when switching. > > > > WDYT? > > > > I think that the difference between java sources and other content is > that, unless you use an agent such as JRebel, a java class change leads > to a full deploy of the bundle, which is likely not instantaneous. > > One was I can possibly see this working is: > > - teach Felix to load exploded bundles ( if it doesn't already know ) > - map the bundle's target directory to a '..../install' directory in the > repository using your FS Resourceprovider idea > - have the bundles reloaded using the JCR installer whenever the install > location receives changes > > There are a lot of details to take care of though. The work done for the > Felix SCR plugin means that you should get a full bundle structure in > Eclipse ( SCR / Metatype XML files, complete manifest ) but I'm not sure > about IntelliJ, where you probably need to manually 'Make' the module. > > Robert > > -- Carsten Ziegeler cziege...@apache.org
