[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [xtext-dev] Working sets broken
|
The idea is to have those things in the workspace where we're
developing against the HEAD.
This is the case for MWE, Xpand, Xtext and EMF (as we want to use https://bugs.eclipse.org/bugs/show_bug.cgi?id=247130)
.
I don't think we should use the latest UML2 nor Xerces.
So I'ld say we should have these things bundled and version in the
target.
Cheers,
Sven
On Feb 10, 2009, at 10:25 PM, Peter Friese wrote:
Thx for looking, but I still had some issues.
Although I am not sure why we checked out certain dependencies in
the first place, I did just the same for all things that were
missing in my workspace:
- some pieces of UML2
- some pieces of EMF
- even Xerces and friends (yuk!)
As I am not sure what the rationale behind checking out the
dependencies vs. just installing the respective bundles into the
workbench was, I did not check in my changes, but instead created a
patch:
<workingsets-patch.txt>
Cheers,
Peter
On 10.02.2009, at 15:30, Sven Efftinge wrote:
I've just fixed that in CVS.
(Seems that the project set export wizard is not creating CVS
location entries for closed projects.)
On Feb 10, 2009, at 9:18 PM, Peter Friese wrote:
Hi,
I just imported the updated working set into my workspace and am
getting tons of red crosses. Appears to me the EMF bundles are
well listed in the "EMF" working set, but no information is
supplied on where to obtain them.
Anybody fixed this yet?
Peter
_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/xtext-dev
_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/xtext-dev
_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/xtext-dev
