Thanks. There is still one part that I can't get working properly. I'm trying to assemble a full target platform for other Virgo IDE developers, so I'd like to make this work in general. Perhaps you have some insight. Please see below.
For reference, please see:
(I haven't even tried to get M2e to work with TP, but I'm expecting it to fail.. sigh :))
On 2012-07-04, at 7:12 AM, Borislav Kapukaranov wrote:
Have these changed recently, say as part of RC release? In particular I'm seeing unsatified dependencies in o.e.v.medic and o.e.v.util for aspectj.lang [1.6.12,2.0.0). This won't work under Juno as 2.2.0 is the only compatible release of that.
We haven't changed AspectJ - it is still the same 1.6.12. Medic, Util and Kernel resolve fine against it during a ripple. I can also see it published in our Virgo p2 repo.
Very oddly, it works ok when I install AJDT into my Eclipse Runtime, but as I say, it doesn't work when I try a pure target platform. In fact, I can't find a source for org.aspectj.lang at all. Instead, I have org.aspectj, org.aspectj.ajde, runtime, weaver and o.e.equino.weaver.aspectj. Where are you getting lang from?
Also, o.e.v.kernel.artifact wants o.e.v.kernel.servicability, which doesn't seem to be provided by the Kernel feature.
That's right, the o.e.v.k.serviceability comes from the nano feature called org.eclipse.virgo.core. That's been the case since 3.5.0.M1 or M2.
Got it, thanks.
Luckily, these don't seem to be affecting things at install time -- not sure why that is.
I guess that since you are composed with the full Virgo repository they are satisfied from there. Probably your target definition needs more stuff added?
No that's not it, see above. :)
virgo-dev mailing list
Miles T. Parker
Senior Solutions Architect
Committer, Eclipse Mylyn and Virgo
Project Lead, Model Focussing Tools and AMP