Can't add bundle pool based installation as AUT [message #1730208] |
Fri, 22 April 2016 10:49 |
Alexander Koptelov Messages: 10 Registered: December 2015 |
Junior Member |
|
|
In the latest nightly build it's impossible to add AUT that has non-standard bundle location.
For example, it is possible to have Oomph-based installation of Eclipse that doesn't have plugins folder, instead its plugins and features are located in a separate bundle pool
(choosing 'Use bundle pool' in the installer).
Here's the stack trace:
org.eclipse.core.runtime.CoreException: The directory "/home/alexander/eclipse/.../eclipse/plugins" is empty.
at org.eclipse.rcptt.internal.launching.ext.PDELocationUtils.getProductLocation(PDELocationUtils.java:69)
at org.eclipse.rcptt.launching.target.TargetPlatformManager.createTargetPlatform(TargetPlatformManager.java:66)
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformManager.createTargetPlatform(Q7TargetPlatformManager.java:125)
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformManager.newTargetPlatform(Q7TargetPlatformManager.java:100)
at org.eclipse.rcptt.internal.launching.ext.Q7TargetPlatformManager.getTarget(Q7TargetPlatformManager.java:75)
at org.eclipse.rcptt.internal.launching.ext.ui.AUTLocationBlock$3.run(AUTLocationBlock.java:215)
at org.eclipse.rcptt.internal.launching.ext.ui.AUTLocationBlock$4.run(AUTLocationBlock.java:236)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
The 2.0.2 version worked fine with such installation.
[Updated on: Fri, 22 April 2016 10:52] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03196 seconds