[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [libra-dev] Juno dependencies in Libra framework UI?


The framework UI depends on a patched version of wst.server.core (an attribute has been added to server extensions). ÂThis patch has not been back ported to WTP indigo builds. ÂAlso, there were dependencies on PDE provisional APIs in our indigo code, these have been turned into API with Juno so the code has been updated to use the new Juno API.

TheÂbest solution seems to be to use the indigo branch to backport framework ui and launchers support. Â To my knowledge WTP will not release SRs for indigo and helios.Â

I will spend some time on it this week. ÂKaloyan may have to look at the build.

On Mon, Apr 23, 2012 at 11:09 PM, Miles Parker <miles.parker@xxxxxxxxxxx> wrote:
Hi Libra team,

When importing Libra into my workspace, I'm seeing a number of version related dependency fails. For example, ..libra.framework.core wantsÂÂorg.eclipse.wst.server.core;bundle-version="1.1.403"ÂI notice also that you have the Juno update site in the build pom.Â

For Virgo, we're needing to target Indigo at least, and Helios if possible. I note that I can import libra.framework.editor.ui, and it builds against the older version ofÂlibra.framework.editor.core that I have, but of course that isn't a very stable solution. Can you give some details about what you're planning to support with which components so we can plan how we're going to consume them? At a minimum of course we'd need to be able to consume the stuff that was factored out of Virgo tooling.

I noticed that there is an Indigo branch, but it seems only to have the facet ui.



Miles T. Parker
Senior Engineer and Product Manager, Tasktop
Committer,ÂEclipse MylynÂandÂVirgo
Project Lead, Model Focussing Tools and AMP

libra-dev mailing list

Naci Dai - naci.dai@xxxxxxxxxxxxx
eteration a.s. itu ari-1 25 maslak istanbul tr
ph: +90 212 328 0825 - fax: +90 212 328 0521