Hi Max,<div><br></div><div>About your "server" question in the last sentence. If you refer to my post, I was trying to make an analogy:</div><div><br></div><div>server <-> applications == Forge core <-> Forge plugins</div>
<div><br></div><div>Please, let us not go to p2, tycho and Equinox? :-)</div><div><br></div><div>I think that the most unobtrusive OSGi for Forge would be the bnd stuff described by Paul. However, I am not sure how does bnd restrict the number of exported packages by a plugin. If it exports everything, then why do we use OSGi at all?</div>
<div><br></div><div>Cheers,</div><div>Ivan<br><br><div class="gmail_quote">On Wed, Sep 26, 2012 at 3:46 PM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:max.andersen@redhat.com" target="_blank">max.andersen@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
>> Hi Paul !<br>
>><br>
>> I watched your presentation and I found it very nice. As in Forge 2.0, we are totally rewriting the core, so full backward compatibility shouldn't be possible in a first glance.<br>
>><br>
>> Lincoln already started something in the 2.0 branch using JBoss Modules and also started to hack it a little deeper.<br>
>><br>
>> As for me, I am also not a big fan of JBM, probably because it may be lacking some reference docs, which leads to deep diving into the code itself to better understand it.<br>
>><br>
>> In terms of being future-proof, OSGi might sound a better path to go. However I am afraid that we may be wanting to kill a mosquito with a cannon, or in other words, trying to cram a technology which may hinder the adoption on Forge in future versions.<br>
>><br>
>> In case we adopt it, I hope that in the future this bnd plugin could be part of JBoss Tools and we could call it "Forge Developer Platform" or something :)<br>
<br>
</div>would need someone to maintain work on it and make sure it does not conflict with using tycho/p2 for osgi development which is the osgi tools used in eclipse land.<br>
<br>
note, Forge moving to osgi doesn't make it easier to use from JBoss Tools, it probably makes it harder - unless the choice is osgi equinox and something compatible with<br>
Eclipse plugins/osgi....<br>
<br>
btw. anyone able to outline me why forge 2 is needed and why the word "server" is now used for Forge ?<br>
<span class="HOEnZb"><font color="#888888"><br>
/max<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div></blockquote></div><br></div>