|
| Re: Buckminster & PDE [message #385778 is a reply to message #385777] |
Mon, 01 June 2009 09:52  |
|
Hi Alex,
Keep in mind that neither PDE build, nor the P2 publisher has been released yet. What's available are bleeding edge
release candidates. Buckminster consumes that technology so some lag is to be expected. We try to reuse as much as
possible of the PDE build code but time constraints, the need to work around bugs, and the need to do everything
headlessly, forced us to write some code in parallel.
We have every intention of unifying our efforts with PDE build as soon as time permits. One of our objectives moving
forward is to increase our involvement in PDE build and help driving it forward.
Kind Regards,
Thomas Hallgren
Alex Chatziparaskewas wrote:
> Hi
>
> Just a quick question to broaden my knowledge about buckminster. And
> please do not understand me wrong. After years of PDE digging and trying
> to explain to other how headless PDE (and Ant) works and seeing
> developers struggling with the complexity and its 'knottyness', I would
> always now recommend to go with buckminster. Simply because PDE does not
> seem to get any easier, while buckminster does get better and better ...
>
> However, back to my question. My understanding of buckminster was always
> that it something like a 'front-end' to (parts of) other build tools, in
> particular the PDE build. Lately though, I am surprised about some of
> the issues I am running into. E.g. exporting features from a workspace,
> I would have just assumed that it is just the 'headless' interface to
> PDE's feature export dialog. However, this does not seem to be the case.
> While the PDE export still works nicely on my stuff, the buckminster
> build does not. So my question(s): At which level does buckmninster hook
> in? Does it 're-implement' some of the PDE features?
> Thanks & Regards
> Alex
>
|
|
|
Powered by
FUDForum. Page generated in 0.02519 seconds
] 
Search
Help
Register
Login
Home
