[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [xtext-dev] MWE/Xpand tooling
|
All,
given all the hassle we had with the PSFs and given that we want to
eat our own dog food (i.e. Xpand, MWE), I suggest we try to coordinate
work on this a bit.
Here are a few things that came to my mind:
1) we need to define a workbench setup, i.e.
a) which version of Eclipse we use to develop on
b) how to integrate our dogfood into the development workbench (use p2
update site, download as zip, which versions do we use)
2) this configuration and the setup process should be documented in
the wiki. We already have a page for that, however it is a bit outdated
3) we need to make sure the PSFs work reliably. Jan's tool is one step
in this direction. However I guess we need to test the PSFs each time
we change them significantly.
This might sound like a lot of work, but I guess we need to do that in
order to have a reliable work environment. Eventually, it will save us
time.
I am willing to work on this, however, I need some input regarding (1).
More comments below.
On 12.02.2009, at 04:02, Jan Köhnlein wrote:
AFAIK, all builds have to be manually "promoted" to be available as
an update site.
Thanks for caring for the docs. BTW they could need some rework,
They're still referring to the oAW way of doing. E.g., is there
still a way to have shortened names "oaw.XmiWriter" as class names
in MWE configs?
You're right. I am filing a bug as we're talking. I guess it would be
good to have a thorough look at the documentation as soon as we have
the Eclipse 3.5M5 Xtext distro Patrick is working on. However, in the
meantime, let's collect things we need to look at (such as the
shortcut name Jan mentioned). Here is the link to the bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=264702
Peter
