| Status of b3 building tool [message #633587] |
Mon, 18 October 2010 09:06  |
Eclipse User |
|
|
|
Hello,
It has been relatively quiet of late and I am wondering, what is the
progress of b3 based build tooling (as opposed to b3 aggregator which
seems to be working and being used based on the latest traffic in this
newsgroup)
I understand that model and language part is relatively ready.
What is the status of the engine implementation?
There was some talk of build debugging support - any progress there?
As this seems to be a modelling subproject, maybe I am looking in the
wrong direction?
--
Roland Tepp
|
|
|
| Re: Status of b3 building tool [message #633605 is a reply to message #633587] |
Mon, 18 October 2010 10:15  |
| Eclipse User |
|
|
|
Hi Roland,
The reason for things being quiet for some time is that we have been
engaged using b3 in an application. As a result we have handled many
issues regarding packaging b3 as an RCP application, and fixing lots of
small bugs found when starting to use the b3 DSL to solve a real world
problem.
As you can see on the home page, there was a dip in commits in
september, but other than that there is quite a lot of activity:
http://www.eclipse.org/modeling/emft/b3/
Many issues in the area of type inference, code completion, and
validation have been found and corrected over the last couple of weeks.
The b3 model and language are quite stable, there are a few outstanding
issues that I expect will have minor impact on model/grammar.
Regarding build debugging - we have not yet started on this. The initial
idea was to try to reuse the JDT debugger, and let b3 generate
bytecodes. In practice this turned out to be more problematic than first
anticipated as it is too hard to present meaningful context information.
Also, when debugging a build there are other questions that you as
developer would like to have answered than the typical "what is the
value of this variable", and "how did I get here" - I am thinking about
queries regarding components, queries to repositories, debugging the
resolution process etc. So instead of the JDT debugger, the general
debugging support looks promising and should not be very difficult to
implement. (Help in this area is much appreciated).
For building, we still recommend using Buckminster as it is production
quality.
Regards
- henrik
On 10/18/10 3:06 PM, Roland Tepp wrote:
> Hello,
>
> It has been relatively quiet of late and I am wondering, what is the
> progress of b3 based build tooling (as opposed to b3 aggregator which
> seems to be working and being used based on the latest traffic in this
> newsgroup)
>
> I understand that model and language part is relatively ready.
>
> What is the status of the engine implementation?
> There was some talk of build debugging support - any progress there?
>
> As this seems to be a modelling subproject, maybe I am looking in the
> wrong direction?
>
|
|
|
|
|
|
|
| Re: Status of b3 building tool [message #638419 is a reply to message #634430] |
Thu, 11 November 2010 04:23 |
| Eclipse User |
|
|
|
21.10.2010 19:31, Henrik Lindberg kirjutas:
> That was how the ideas around b3 started. PDE/Build consists of two
> parts - the actual building, and the headless generated ANT scripts. The
> part of PDE/Build that many do not like is the generated ANT script. The
> idea for b3 is to use the same approach as in Buckminster - i.e. to call
> the underlying PDE logic that performs the actual building.
> That underlying logic will probably never be replaced, and the PDE/Build
> (the headless part) will in any scenario be around for quite some time
> as many depend on it.
So, I assume, the short answer is "No" there are currently no plans to
replace headless (generated ANT scripts) way of building with b3?
--
Roland Tepp
|
|
|
Powered by
FUDForum. Page generated in 0.03969 seconds
Home