Community
Participate
Working Groups
Created attachment 187847 [details] workspace customBuildCallbacks Hello, customBuildCallbacks seems to be ignored when using buckminster headless (I haven't test non-headless). I am using the latest buckminster with pde, cvs and subversive installed. You can find attached a simple workspace based on com.example.mail that triggers the problem : icons.zip should be in the plugin, and is not. plugin export in an eclipse (same machine and OS) works just fine. I am running out of ideas here. Thanks.
This is per desing. The customBuildCallbacks i part of of the ant-script suite generated from PDE. Buckminster never generates those ant-scripts and no calls are made to them. Buckminster uses a lot of functionality provided by classes in the PDE, but we never ask PDE to generate scripts that we then can call on. That would be a very bad fit with the current model. If you want to customize what Buckminster does, you will have to do that in a declarative way that fits into the Buckminster model (by overriding actions in a cspex file).
do you think I can write an action in a generic way that "automatically" read customBuildCallbacks and execute the correct ant script ? (let's say that I only need post/pre.gather.bin.parts) I have generated customBuildCallbacks and I really don't want to have to write a non generated action for each of them, that can get out of sync anytime... I think this should really be stated clearly somewhere, because PDE support is "advertised" but it is not true for all the PDE mechanisms, this is confusing :) Afterwards I found the info in the buckybook but you have to read it really carefully to do not miss the information. Thanks !
(In reply to comment #2) > do you think I can write an action in a generic way that "automatically" read > customBuildCallbacks and execute the correct ant script ? (let's say that I > only need post/pre.gather.bin.parts) > I think that will be difficult given that the structure and properties expected by such scripts aren't present when you use Buckminster. > I think this should really be stated clearly somewhere, because PDE support is > "advertised" but it is not true for all the PDE mechanisms, this is confusing > :) > Afterwards I found the info in the buckybook but you have to read it really > carefully to do not miss the information. > I don't disagree. But to our defense I'd say that the information is there and as most other projects, we tend to advertise what's positive. The buckybook is meant to be read carefully ;-). Opinions on it's content and organization is of course always welcome.
