<html><body bgcolor="#FFFFFF"><div>You do not necessarily have to refactor your code itself. You may only need to organize the code into a module (which is a folder that has specified directories for src, lib, resources, etc) that is referenced along with *kepler-2.0 in a new suite.</div><div><br></div><div>The details of how to make a module are in the build instructions:</div><div><br></div><a href="https://kepler-project.org/developers/teams/build/documentation/build-system-instructions">https://kepler-project.org/developers/teams/build/documentation/build-system-instructions</a><div><br></div><div>Overall, this task should be fairly straightforward.</div><div><br></div><div>It is possible that your code itself will need to be refactored itself to work with 2.0. It is impossible to tell. It entirely depends on whether any of the APIs that your plugin uses have changed. Therefore, there are no general instructions we could provide. It is possible that no code refactoring will be necessary.</div><div><div><br></div><div>You could seperate the task of making a module with the task of making that module compatible with 2.0. First, simple include your module in a suite that references *kepler-1.0. After you get that working, you know that you have structured your module correctly. You can then change *kepler-1.0 to *kepler-2.0 to see whether or not any code refactoring is necessary. Breaking this up into two stages like this may not really be necessary however, as making your plugin into a module should be fairly straightforward. It is up to you whether you want to break the task into two stages or just do it all at once.</div><div><br></div><div>Hope that helps!</div><div><br>Sent from my iPhone</div><div><br>On Apr 21, 2010, at 6:40 AM, tog <guillaume.alleon@gmail.com> wrote:<br><br></div><div></div><blockquote type="cite"><div>Hi David,<br><br>No this is all my question is about. I am aware that I will need to refactor my code but I would like to get some information on how to do it.<br><br>Guillaume<br><br><br><div class="gmail_quote">On Wed, Apr 21, 2010 at 6:07 PM, David Welker <span dir="ltr"><<a href="mailto:david.v.welker@gmail.com">david.v.welker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Is your plugin making use of the new module system, which is how plugins should now be made?<br>
<br>
Sent from my iPhone<div><div></div><div class="h5"><br>
<br>
On Apr 21, 2010, at 3:12 AM, tog <<a href="mailto:guillaume.alleon@gmail.com" target="_blank">guillaume.alleon@gmail.com</a>> wrote:<br>
<br>
</div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">
Dear all,<br>
<br>
I have a plugin for a grid middleware working with Kepler 1.0. Where can I find some documentation describing how to port that plugin onto Kepler 2.0 ?<br>
All documentations I have found so far is still for 1.0 (at least this is what tells the cover page).<br>
<br>
<br>
Best Regards<br>
Guillaume<br></div></div>
_______________________________________________<br>
Kepler-users mailing list<br>
<a href="mailto:Kepler-users@kepler-project.org" target="_blank">Kepler-users@kepler-project.org</a><br>
<a href="http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users" target="_blank">http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users</a><br>
</blockquote>
</blockquote></div><br><br clear="all"><br>-- <br>PGP KeyID: 1024D/69B00854 <a href="http://subkeys.pgp.net">subkeys.pgp.net</a><br><br><a href="http://cheztog.blogspot.com">http://cheztog.blogspot.com</a><br>
</div></blockquote></div></body></html>