| Unresolved import in Buckminster, but not PDE [message #387382] |
Wed, 01 July 2009 17:03  |
Eclipse User |
|
|
|
Hello -
I'm having a strange issue with Buckminster, which is remarkably difficult
to describe. The project I work on is an SDK, with a fairly large number
of plug-ins. This SDK is shipped as a zip of built plug-ins. Some of these
plug-ins are jars but some are shipped unpacked, because they contain
resources we need to load. We have a sample application which builds and
ships separately from the SDK.
Previously, we had set up the rmap of the sample app to redirect to the
rmap of the SDK - the build then checked out and compiled the needed
source for both the SDK and the sample app. This worked fine. We decided
it was necessary to instead download an official, already-released version
of the SDK, and set it up as part of the target platform Buckminster would
use to build the sample application. This is where things start to get
screwy; we wound up getting the following exception (anonymized):
[java] INFO: [start
com.company.sampleapp:osgi.bundle$1.9.0.qualifier#OSGi#eclip se.build]
[java] org.eclipse.core.runtime.CoreException: The import
com.company.sdk.map.rcp cannot be resolved
[java] at
org.eclipse.buckminster.core.internal.actor.AbstractBuildInt egrationActor.internalPerform(AbstractBuildIntegrat
ionActor.java:53)
[java] at
org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:136)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
[java] at
org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:198)
[java] at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:99)
[java] at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 95)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 29)
[java] at
org.eclipse.buckminster.cmdline.Headless.start(Headless.java :304)
[java] at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
[java] at
org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
[java] at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
[java] at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
[java] The import com.company.sdk.map.rcp cannot be resolved
The package in question, com.company.sdk.map.rcp, is in a plug-in
com.company.sdk.map.rcp. The SDK is built by Buckminster, and is created
by exporting a feature. The feature entry for com.company.sdk.map.rcp does
not have 'unpack="false"' in it, and when exported, it appears as properly
unpacked.
The classpath for com.company.sdk.map.rcp is set as ".", and the src/
folder is added to it. This runtime information is set up correctly both
on the "classpath" and "build" tabs of the Manifest Editor.
I can set up a workspace with the sample application and point it to the
built SDK target platform, and it builds (and runs) fine. It is only when
I try to build the sample app through Buckminster that I get the above
exception.
We have other plug-ins that ship as folders, but only this one seems to be
giving us trouble. I can't discern any difference between the way the
working plug-ins and this broken one are set up.
Any help would be greatly appreciated (or a pointer to another mailing
list if this isn't a Buckminster issue). Thank you.
-- Art
|
|
|
| Re: Unresolved import in Buckminster, but not PDE [message #387384 is a reply to message #387382] |
Thu, 02 July 2009 07:08  |
| Eclipse User |
|
|
|
Hi Art,
The first thing that I'd try is to let a proper build precede the perform. The perform will call the
Eclipse builder for each project that it builds but calling a build will build the workspace as a
whole. I.e. try:
buckminster build
buckminster perform xxx
or, in case that doesn't help either, try:
buckminster build -thorough
buckminster perform xxx
The -thorough ensures that at least two full builds are executed on the workspace. In some strange
situations, that is necessary (just like it is in the IDE where you need to do a clean build more
then once to get rid of all errors).
HTH,
Thomas Hallgren
Art Doler wrote:
> Hello -
> I'm having a strange issue with Buckminster, which is remarkably
> difficult to describe. The project I work on is an SDK, with a fairly
> large number of plug-ins. This SDK is shipped as a zip of built
> plug-ins. Some of these plug-ins are jars but some are shipped unpacked,
> because they contain resources we need to load. We have a sample
> application which builds and ships separately from the SDK.
>
> Previously, we had set up the rmap of the sample app to redirect to the
> rmap of the SDK - the build then checked out and compiled the needed
> source for both the SDK and the sample app. This worked fine. We decided
> it was necessary to instead download an official, already-released
> version of the SDK, and set it up as part of the target platform
> Buckminster would use to build the sample application. This is where
> things start to get screwy; we wound up getting the following exception
> (anonymized):
> [java] INFO: [start
> com.company.sampleapp:osgi.bundle$1.9.0.qualifier#OSGi#eclip se.build]
> [java] org.eclipse.core.runtime.CoreException: The import
> com.company.sdk.map.rcp cannot be resolved
> [java] at
> org.eclipse.buckminster.core.internal.actor.AbstractBuildInt egrationActor.internalPerform(AbstractBuildIntegrat
>
> ionActor.java:53)
> [java] at
> org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:136)
>
> [java] at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
>
> [java] at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
>
> [java] at
> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:198)
> [java] at
> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:99)
>
> [java] at
> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
>
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 95)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 29)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :304)
> [java] at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:386)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:597)
> [java] at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
> [java] The import com.company.sdk.map.rcp cannot be resolved
>
> The package in question, com.company.sdk.map.rcp, is in a plug-in
> com.company.sdk.map.rcp. The SDK is built by Buckminster, and is created
> by exporting a feature. The feature entry for com.company.sdk.map.rcp
> does not have 'unpack="false"' in it, and when exported, it appears as
> properly unpacked.
> The classpath for com.company.sdk.map.rcp is set as ".", and the src/
> folder is added to it. This runtime information is set up correctly both
> on the "classpath" and "build" tabs of the Manifest Editor.
> I can set up a workspace with the sample application and point it to the
> built SDK target platform, and it builds (and runs) fine. It is only
> when I try to build the sample app through Buckminster that I get the
> above exception.
> We have other plug-ins that ship as folders, but only this one seems to
> be giving us trouble. I can't discern any difference between the way the
> working plug-ins and this broken one are set up.
>
> Any help would be greatly appreciated (or a pointer to another mailing
> list if this isn't a Buckminster issue). Thank you.
> -- Art
>
|
|
|
|
| Re: Unresolved import in Buckminster, but not PDE [message #387388 is a reply to message #387387] |
Thu, 02 July 2009 14:24 |
| Eclipse User |
|
|
|
Art Doler wrote:
> This error shows up in the actual build step - so it's the same problem
> I was already having, with a little more context supplied.
> Just to add some more info to the dump: I'm using Eclipse 3.4.2 as my
> TP, and a 3.4 Buckminster.
>
Could you try using Buckminster for 3.5? There's nothing stopping you from building 3.4 artifacts
with it. To my knowledge, the --thorough option doesn't work with 3.4.
Regards,
Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.04240 seconds
Home