Comments on: Tip: PDE Build and Binary Cycles http://code9.com/2008/10/28/tip-pde-build-and-binary-cycles/ Code 9 Sun, 01 Aug 2010 09:18:58 +0000 http://wordpress.org/?v=2.5.1 By: James http://code9.com/2008/10/28/tip-pde-build-and-binary-cycles/#comment-494 James Thu, 20 Nov 2008 16:48:08 +0000 http://code9.com/?p=97#comment-494 "...and discussing why cycles are evil in the first place...." Can you detail how you convinced your client that cycles are evil in the first place ? “…and discussing why cycles are evil in the first place….”
Can you detail how you convinced your client that cycles are evil in the first place ?

]]> By: zx http://code9.com/2008/10/28/tip-pde-build-and-binary-cycles/#comment-448 zx Sun, 02 Nov 2008 18:05:24 +0000 http://code9.com/?p=97#comment-448 @Gunnar, the key word is the "workspace." Since these artifacts exist in the workspace, it won't work :( I also assume your fragment is using Eclipse-ExtensibleAPI which is causing the cycle? @Ekke, good to hear! We should still talk at ESE to see how we can simplify your development workflows. @Gunnar, the key word is the “workspace.” Since these artifacts exist in the workspace, it won’t work :(

I also assume your fragment is using Eclipse-ExtensibleAPI which is causing the cycle?

@Ekke, good to hear! We should still talk at ESE to see how we can simplify your development workflows.

]]> By: ekke http://code9.com/2008/10/28/tip-pde-build-and-binary-cycles/#comment-437 ekke Wed, 29 Oct 2008 09:11:22 +0000 http://code9.com/?p=97#comment-437 hi chris, you made my day - thanks for this enhancement I was wishing since some time. ...seems that personal experiences sometimes fixes bugs sooner then reporting by bugzilla ;-) in my OSGI enterprise application I always run into this problem with 3rdParty bundles like SLF4J-API, EasyBeans, ... alone this bugfix is reason enough starting with 3.5M3 for daily work :-) ekke BTW: I had just prepared something to show you on Eclipse Summit Europe to demonstrate how hard it is to live with these 3rd party cycles. now perhaps I can show you some of my well-running things instead... ekke hi chris,

you made my day - thanks for this enhancement I was wishing since some time.

…seems that personal experiences sometimes fixes bugs sooner then reporting by bugzilla ;-)

in my OSGI enterprise application I always run into this problem with 3rdParty bundles like SLF4J-API, EasyBeans, …

alone this bugfix is reason enough starting with 3.5M3 for daily work :-)

ekke
BTW: I had just prepared something to show you on Eclipse Summit Europe to demonstrate how hard it is to live with these 3rd party cycles. now perhaps I can show you some of my well-running things instead…

ekke

]]> By: Gunnar http://code9.com/2008/10/28/tip-pde-build-and-binary-cycles/#comment-436 Gunnar Wed, 29 Oct 2008 07:07:32 +0000 http://code9.com/?p=97#comment-436 What about this one: * Plugin A * Plugin B (depends on A) * Fragment C (Host: A, depends on B) If you have all three loaded in your workspace, PDE won't be able to build the product because of cycles (3.4/3.5M2). Will that be fixed as well? Actually, you have a dependency but only because of the fragment. A and B can be compiled fine. The fragment is optional and can be compiled later. It just contributes an implementation to A which will be used by B *if* it is available. What about this one:
* Plugin A
* Plugin B (depends on A)
* Fragment C (Host: A, depends on B)

If you have all three loaded in your workspace, PDE won’t be able to build the product because of cycles (3.4/3.5M2). Will that be fixed as well?

Actually, you have a dependency but only because of the fragment. A and B can be compiled fine. The fragment is optional and can be compiled later. It just contributes an implementation to A which will be used by B *if* it is available.

]]>