Community
Participate
Working Groups
There is a preliminary RC3 composite repo for the soon to be RC3 version at Helios Staging - http://download.eclipse.org/releases/staging For Riena there is now only one entry "Riena Target Components". If I install just Riena Target Components and let p2 decide what else to choose, it will pick RAP for reasons that I dont quit understand. There are 5 bundles of Riena which have an optional dependency in their manifest.mf to say "org.eclipse.swt" and "org.eclipse.rap.rwt" (and others). Both dependencys are optional in manifest.mf. There is a p2.inf file that defines the RAP pieces as non-greedy. What actually happens is that it install org.eclipse.swt but non of the platform specific fragments. And it installs the rap bundles org.eclipse.rap.jface.databinding, org.eclipse.rap.jface, org.eclipse.rap.rwt, org.eclipse.rap.ui.workbench and org.eclipse.rap.ui. So you end up with something that you cannt use out of the box. What you have to do is install equinox target components, rcp sdk and then riena target components. That does the trick. Still I wonder what the reason is here. One of the bundles distributed with Riena "org.apache.commons.beanutils" imports org.apache.commons.logging. Now the Helios repo has the bundle org.apache.logging and org.slf4j.jcl which also exports org.apache.commons.logging. Now the slf4j bundles exports the version 1.1.1 of o.a.c.logging while the standalone bundle is 1.0.4. It picks the slf4j version which is unexpected but probably because its the higher version number. The same is true for an import or org.apache.commons.logging. It
christian, in target platforms it can help if you add under -environment ----implicite plugin dependencies <implicitDependencies> <plugin id="org.eclipse.jface"/> <plugin id="org.eclipse.swt"/> <plugin id="org.eclipse.ui"/> <plugin id="org.eclipse.jface.databinding"/> <plugin id="org.eclipse.ui.workbench"/> </implicitDependencies> -- with commons logging - in my TP I always use slf4j to provide the packages for commons logging etc, so this is ok for my situations (but was a problem with RC1 where wrong orbit bundles of slf4j caused problems, but this is fixed now) if you really need o.a.c.logging then perhaps also add it to implicite plugin dependencies or add the commons logging bundle to your TP: cmd-alt-shift-A on mac then select org.apache.commons.logging ekke
So the next step I did was that I installed Equinox Target Components and then RCP SDK. So I had o.e.jface and org.eclipse.swt and org.eclipse.swt.win32........ in my target platform together with many other components. Then I installed Riena Target Components and I get the RAP components in the target platform..... org.eclipse.rap.jface.databinding org.eclipse.rap.jface org.eclipse.rap.rwt org.eclipse.rap.ui.workbench org.eclipse.rap.ui So now I need to manually disable them in order to run my application (either in the target platform or the launch config). Pretty annoying.....
A workaround I have identified is to disable "Include required software" when you install Riena Target Components. That works ok, although its not very intuitive....
unfortunately, for many of these multiversion, cross platform , target platform cases it seem that you have to disable that option. That's why its there :-/ Perhaps you can enter a PDE bug to suggest improvements to this workflow.
(In reply to comment #3) > A workaround I have identified is to disable "Include required software" when > you install Riena Target Components. That works ok, although its not very > intuitive.... ..and it makes TP more complicated if you rely on this feature that dependencies will be fetched automatically
(In reply to comment #4) > unfortunately, for many of these multiversion, cross platform , target platform > cases it seem that you have to disable that option. That's why its there :-/ > Perhaps you can enter a PDE bug to suggest improvements to this workflow. from my POV: - checking 'include required software' should only include required, but not optional dependencies - there ould be 2nd option 'include also all optional dependencies' ekke
(In reply to comment #2) > So the next step I did was that I installed Equinox Target Components and then > RCP SDK. So I had o.e.jface and org.eclipse.swt and > org.eclipse.swt.win32........ in my target platform together with many other > components. > > Then I installed Riena Target Components and I get the RAP components in the > target platform..... > > org.eclipse.rap.jface.databinding > org.eclipse.rap.jface > org.eclipse.rap.rwt > org.eclipse.rap.ui.workbench > org.eclipse.rap.ui > > So now I need to manually disable them in order to run my application (either > in the target platform or the launch config). Pretty annoying..... Christian, my workaround to put the RCP/SWT plug-ins as implicit plugin dependencies into the TP doesn't help with newest repositiores. so you're right there are only 3 ways to deal with this: * remove them from the TP * remove them from Launch configs * uncheck 'include required software' and add all needed dependencies into the TP ekke
would it make sense to add a new checkbox to fine-tune how required software will be added ? * include required software * include optional dependencies then one could decide if optional dependencies should be resolved ekke
(In reply to comment #6) > (In reply to comment #4) > > unfortunately, for many of these multiversion, cross platform , target platform > > cases it seem that you have to disable that option. That's why its there :-/ > > Perhaps you can enter a PDE bug to suggest improvements to this workflow. > > from my POV: > > - checking 'include required software' should only include required, but not > optional dependencies > - there ould be 2nd option 'include also all optional dependencies' > > ekke +1 for that suggestion
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
