|Re: [libra-dev] Juno dependencies in Libra framework UI?|
The OSGi Bundle Facet feature was introduced with Indigo and in Juno it is still compatible with the Indigo release train.
Naci already told you about the Framework Launchers. Indeed, from release perspective it is possible to downport the Framework Launchers to the Indigo stream. Then we can produce an extraordinary release of Libra for Indigo. However, this release won’t be part of the Indigo Simultaneous Release, which means it will not be available on the Eclipse Indigo update site. Only users and adopters that explicitly want this new release will actually use it. If you want to go this way, let me know. I will support the work with the release efforts.
Regarding lack of response in WTP. Indeed, some subprojects experience some stuffing problems. If you give me a list of bugs, I can raise them to the PMC. Sometimes, this helps to make the things run faster.
Thanks for the quick response, Naci.
For Virgo Tooling, I've more or less made up my mind not to rely on changes to WTP or PDE, as frustrating as those can be to extend. We've had to engineer around some of the WTP stuff as well. I'm just not confident in the ability to get any changes into WTP in a timely way. I'll admit that the main thing I'm going on there is a note I sent to wtp-dev re: the possibility of providing patches for other changes to WTP to support some UI stuff I wanted to do, and haven't received a response from that as yet or on related bugs. But the bottom-line for us is that we really need to support Indigo on a continuing basis and from what I've seen that means that we'll probably have to rely on the Indigo WTP builds. It's not an ideal situation, I know, and thanks for looking into it.
On 2012-04-23, at 2:33 PM, Naci Dai wrote:
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.