We could move the ../../ resources into the various servers, but,
there are other languages other than Java, like the PHP Gadgets
server that would prefer them to be where they are. (Am I
representing that correctly PHP guys ?)
One solution might be to shift the javascript folder down one to make
space for a pom.xml to pack the resources into a jar that could then
be depended on rather than included via ../../
It would at lest keep the resources in a place that would make them
sharable without too much effort.
Just a thought ?
Ian
On 25 Apr 2008, at 17:18, Alexander Klimetschek wrote:
Hi all,
first of all hello everyone, I am new to this list. I am currently
working on integrating Shindig into Apache Sling [1], making it to
use JCR [2] as storage backend and osgi-bundlizing [3] it.
While building shindig for the first time and following the
instructions on the website, I noticed that you mention the rather
complicated way of using the Eclipse Maven2 plugin to import maven
projects into Eclipse. That's a valid way, but IMHO using "mvn
eclipse:eclipse" on the command line to create an Eclipse project
(and then importing it in Eclipse) is much simpler. AFAIK it's also
more widely used.
This would make the "Setting up an Eclipse project to build
Shindig" section on [4] shorter and simpler, which is good for
newbies ;-)
Regards,
Alex
[1] http://incubator.apache.org/sling
[2] http://jackrabbit.apache.org/
[3] http://felix.apache.org/
[4] http://incubator.apache.org/shindig/#tab-building
--
Alexander Klimetschek
[EMAIL PROTECTED]
>> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<
