Hi Guillaume,<br><br>Technically its possible to run a substantially streamlined version of Kepler that omits all or most of the actors and their supporting jar files. However, there are many relatively hidden dependencies that may be hard to resolve, and we do not currently have a mechanism for supporting a trimmed down version like this -- but we will as the modularization work I described earlier matures. That said, you can probably exclude most of the jar files in lib/jar as long as you include the lib/jar/base-jars set (which are required by the core) and omit all of the java code for actors from your build. You'll have to configure this manually at this point, which means tracking down all of the actor code which is spread across many java packages, but I know it has been done in the past. I would expect the process to be time consuming until we finish the modularization process and clarify all of the dependencies in the code. Hope this helps you out, <br>
<br>Matt<br><br><div class="gmail_quote">On Wed, Nov 5, 2008 at 1:23 PM, tog <span dir="ltr"><<a href="mailto:guillaume.alleon@gmail.com">guillaume.alleon@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Matt<br>
<br>
Thanks for your quick answer.<br>
I will try this new build system in a day or two.<br>
<br>
Could in the meantime someone comment on how to be able to have a<br>
custom Kepler with only my actor i.e. removing existing actors and how<br>
to add a new actor and its third-party jars.<br>
<br>
Thanks and Best Regards<br>
<br>
Guillaume<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
On Thu, Nov 6, 2008 at 2:17 AM, Matt Jones <<a href="mailto:jones@nceas.ucsb.edu">jones@nceas.ucsb.edu</a>> wrote:<br>
> Hi,<br>
><br>
> On Wed, Nov 5, 2008 at 8:43 AM, tog <<a href="mailto:guillaume.alleon@gmail.com">guillaume.alleon@gmail.com</a>> wrote:<br>
>><br>
>> Dear all,<br>
>><br>
>> Sorry for asking again some more questions :)<br>
>><br>
>> I have an actor that is using plenty of third-party jars (a lot of<br>
>> them may collide some existing ones). For example my actor is using<br>
>> jaxb with a different version than the one located in<br>
>> /Applications/Kepler-1.0.0/Kepler.app/Kepler/lib/jar/<br>
>><br>
>> I am therefore wondering if there is a way to isolate the loading of<br>
>> dependencies on a per actor basis ?<br>
><br>
> We're working on such a mechanism now. We've recognized this conflicting<br>
> jar problem for a while, and now we are working on a new, modular system in<br>
> which actors or packages of actors are created in independent modules and<br>
> can specify their own jar dependencies, even if they have conflicting<br>
> version requirements for a particular jar file. This is being accomplished<br>
> through the use of independent ClassLoaders for each of the modules.<br>
> Unfortunately, we are not done with this work yet and so it is not yet in<br>
> the default build for kepler.<br>
><br>
> However, if you want to experiment with our new build system, you could try<br>
> the alternate build which handles these module dependency conflicts. It is<br>
> a work in progress and is likely to still change substantially -- we're<br>
> actively working on it -- so be prepared for problems if you try this<br>
> system. Nevertheless, you might find it useful. To see the alternate build<br>
> instructions, visit this page:<br>
> <a href="https://dev.kepler-project.org/developers/teams/build/documentation/the-new-build-system" target="_blank">https://dev.kepler-project.org/developers/teams/build/documentation/the-new-build-system</a><br>
> Feedback on how that system works for you would be appreciated.<br>
><br>
><br>
>><br>
>> I have then noticed this file .classpath.default. My understanding is<br>
>> that this file is containing all the (existing) jars required for the<br>
>> existing actors.<br>
>> Does that mean that removing all these files + the actors definition<br>
>> located in /Applications/Kepler-1.0.0/Kepler.app/Kepler/kar/actors/<br>
>> will lead to a kind of "empty" Kepler ?<br>
>><br>
>> Therefore adding an actor is just:<br>
>> - creating a kar file putting in<br>
>> /Applications/Kepler-1.0.0/Kepler.app/Kepler/kar/actors/<br>
>> - adding the adequate dependencies in<br>
>> /Applications/Kepler-1.0.0/Kepler.app/Kepler/lib/jar<br>
>> - modifying accordingly the .classpath.default file<br>
>><br>
>> Am I right ?<br>
><br>
> No, the .classpath.default file is only used for the eclipse build.<br>
> Modifying it will not really affect how the ant build works.<br>
><br>
>><br>
>><br>
>> There is then still this issue of being able to use different jars of<br>
>> the same tools for different actors ?<br>
><br>
> Right -- having the build and runtime system support actors that require<br>
> conflicting jar files is a major requirement of the new build and runtime<br>
> system. We'll get it worked out as soon as possible.<br>
><br>
> Matt<br>
><br>
> --<br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
> Matthew B. Jones<br>
> Director of Informatics Research and Development<br>
> National Center for Ecological Analysis and Synthesis (NCEAS)<br>
> UC Santa Barbara<br>
> <a href="mailto:jones@nceas.ucsb.edu">jones@nceas.ucsb.edu</a> Ph: 1-907-523-1960<br>
> <a href="http://www.nceas.ucsb.edu/ecoinfo" target="_blank">http://www.nceas.ucsb.edu/ecoinfo</a><br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
><br>
<br>
<br>
<br>
</div></div><font color="#888888">--<br>
PGP KeyID:C1A0A73F FingerPrint:A4A2 73C0 E7D4 6437 8185 D05E ECF2<br>
AD84 C1A0 A73F<br>
<a href="http://cheztog.blogspot.com" target="_blank">http://cheztog.blogspot.com</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Matthew B. Jones<br>Director of Informatics Research and Development<br>National Center for Ecological Analysis and Synthesis (NCEAS)<br>
UC Santa Barbara<br><a href="mailto:jones@nceas.ucsb.edu">jones@nceas.ucsb.edu</a> Ph: 1-907-523-1960<br><a href="http://www.nceas.ucsb.edu/ecoinfo">http://www.nceas.ucsb.edu/ecoinfo</a><br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>