Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Resolve plugin and package errors in headless build
Resolve plugin and package errors in headless build [message #757182] Thu, 17 November 2011 01:20 Go to next message
Thomas C. Franke is currently offline Thomas C. FrankeFriend
Messages: 13
Registered: November 2011
Junior Member
Hi,

still another two problem, maybe s.o. can help here.

I)
I wanna build by RCP project containing a feature 'RxTxComm_feature' with deps to plugins 'RxTxComm' and some fragments 'RxTxComm.win32', 'RxTxComm.win64'...
The win32 one seems to be found, for all other plugins there is a warning that the plugin cannot be resolved - No Idea why. The build should be independent of target os and arch. This follows when creating the installable product.
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\RxTxComm_feature\feature.xml, line 31: Plug-in reference 'RxTxComm.linux.i686' cannot be resolved


II)
For any reason the build crashes while a package cannot be resolved:
Error: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service.hivnat.ueye.ui\src\com\alere\service\hivnat\ueye\ui\UEyeCameraView.java, line 44: The import com.alere.ids cannot be resolved

Compiling the exactly same code using the eclipse IDE (Project->Build automatically) works fine and using buckminster a site.p2 action can be performed - in headless it does not work.

Full output:
[workspace] $ "C:\Program Files\Java\jdk1.6.0_27\bin\java.exe" "-Dbuckminster.output.root=C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\buckminster.output" "-Dbuckminster.temp.root=C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\buckminster.temp" -Xmx512m -jar C:\workspace\buckminster-headless\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar -application org.eclipse.buckminster.cmdline.headless -data "C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace" --loglevel debug -S "C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\commands.txt"
setpref 'targetPlatformPath=/C:/Program Files/Jenkins/jobs/rcptargetplatform/builds/2011-11-16_17-25-22/archive//targetPlatform'
Preference 'targetPlatformPath' set to the value '/C:/Program Files/Jenkins/jobs/rcptargetplatform/builds/2011-11-16_17-25-22/archive//targetPlatform'
Doing full workspace refresh
......
org.eclipse.help:osgi.bundle/[3.2.0,4.0.0): Found match org.eclipse.help:osgi.bundle$3.5.0.v20100524
org.eclipse.core.commands:osgi.bundle/[3.4.0,4.0.0): Found match org.eclipse.core.commands:osgi.bundle$3.6.0.I20100512-1500
Unable to determine readerType for project com.alere.service.hivnat.appmodel.interf. Assuming "local"
Unable to determine readerType for project RxTxComm. Assuming "local"
Unable to determine readerType for project com.alere.service.com. Assuming "local"
Unable to determine readerType for project com.alere.service. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel.ui. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel.calibration.ui. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel.calibration.ui_feature. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel.ui.control. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel.ui.control_feature. Assuming "local"
Unable to determine readerType for project log4j. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.ueye.ui. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.ueye.ui_feature. Assuming "local"
Unable to determine readerType for project log4j. Assuming "local"
Unable to determine readerType for project log4j_feature. Assuming "local"
Unable to determine readerType for project log4j_feature. Assuming "local"
Unable to determine readerType for project jfreechart. Assuming "local"
Unable to determine readerType for project jfreechart_feature. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.bootloadermodel.interf. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.connections.serial. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.connections.serial.bootloader. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.connections.serial.application. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.bootloadermodel. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel.livedata.ui. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.appmodel.statusdata.ui. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat.bootloadermodel.ui. Assuming "local"
Unable to determine readerType for project com.alere.service.hivnat_feature_base. Assuming "local"
Unable to determine readerType for project RxTxComm.win32. Assuming "local"
Unable to determine readerType for project RxTxComm_feature. Assuming "local"
Unable to determine readerType for project log4j_feature. Assuming "local"
Unable to determine readerType for project com.alere.service_products. Assuming "local"
Unable to determine readerType for project com.alere.service_products_feature. Assuming "local"
Unable to determine readerType for project com.alere.service_feature_base. Assuming "local"
Unable to determine readerType for project com.alere.service.site. Assuming "local"
INFO:  Import complete.
Doing full workspace refresh
Waiting for jobs to end
build '-c' '-D' 'osgi.arch=*' '-D' 'osgi.os=*'
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\RxTxComm_feature\feature.xml, line 31: Plug-in reference 'RxTxComm.linux.i686' cannot be resolved
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\RxTxComm_feature\feature.xml, line 51: Plug-in reference 'RxTxComm.win64' cannot be resolved
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\RxTxComm_feature\feature.xml, line 61: Plug-in reference 'RxTxComm.linux.x86_64' cannot be resolved
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service\src\com\alere\service\ui\ConnectionView.java, line 49: The value of the field ConnectionView.m_bindingContext is not used
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service\src\com\alere\service\ui\ConnectionView.java, line 438: The value of the local variable toolbarManager is not used
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service\src\com\alere\service\ui\ConnectionView.java, line 446: The value of the local variable menuManager is not used
Error: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service.hivnat.ueye.ui\src\com\alere\service\hivnat\ueye\ui\UEyeCameraView.java, line 439: IUEyeCamera cannot be resolved to a type
Error: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service.hivnat.ueye.ui\src\com\alere\service\hivnat\ueye\ui\UEyeCameraView.java, line 440: IUEyeCameraInfo cannot be resolved to a type
Error: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service.hivnat.ueye.ui\src\com\alere\service\hivnat\ueye\ui\UEyeCameraView.java, line 44: The import com.alere.ids cannot be resolved
....
Re: Resolve plugin and package errors in headless build [message #757296 is a reply to message #757182] Thu, 17 November 2011 14:55 Go to previous messageGo to next message
Thomas C. Franke is currently offline Thomas C. FrankeFriend
Messages: 13
Registered: November 2011
Junior Member
To clarify the problem in point I) above:

I have 4 plugin fragments 'RxTxComm.win32', 'RxTxComm.win64', 'RxTxComm.linux.i686' and 'RxTxComm.linux.x86_64' (know not nice names...) with a host plugin 'RxTxComm'.
In each plugin fragment a platform filter is specified like '(&(osgi.os=linux)(osgi.arch=x86))'...
The host plugin has no platform filter.
To include the plugins into a product, a feature called 'RxTxComm_feature' is created referencing the plugin and its fragments. The supported environment for the feature is set to 'os="linux,win32" arch="x86,x86_64"'.
Using the eclipse IDE it works fine and products for various platforms can be exported and run fine.

The warning
Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\RxTxComm_feature\feature.xml, line 31: Plug-in reference 'RxTxComm.linux.i686' cannot be resolved

comes out of the "build"-action of buckminster when called from jenkins. I assumed the "build"-action is platform independent, the "site.p2"-actoin should be called with 'target.os=* target.arch=*...' to create a update site for all platforms, and the 'create.product'-action (see the ralf ebert howto) is called with a specified combination and may be called several times.
I also tried to call the "build"-action with -D target.os=*... but it did not solve the problem. The Warning results in an error in "site.p2" action.
No component named RxTxComm.win64:osgi.bundle(&(osgi.os=linux)(osgi.arch=x86)) is known to Buckminster
Re: Resolve plugin and package errors in headless build [message #757357 is a reply to message #757296] Thu, 17 November 2011 21:49 Go to previous message
Thomas C. Franke is currently offline Thomas C. FrankeFriend
Messages: 13
Registered: November 2011
Junior Member
Solved problem 1) see https://bugs.eclipse.org/bugs/show_bug.cgi?id=364085
Solution was quiet too simple...
Re: Resolve plugin and package errors in headless build [message #758014 is a reply to message #757182] Thu, 17 November 2011 06:43 Go to previous message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 2011-11-17 02:20, Thomas C. Franke wrote:
> Hi,
>
> still another two problem, maybe s.o. can help here.
>
> I)
> I wanna build by RCP project containing a feature 'RxTxComm_feature' with deps to plugins 'RxTxComm' and some fragments
> 'RxTxComm.win32', 'RxTxComm.win64'...
> The win32 one seems to be found, for all other plugins there is a warning that the plugin cannot be resolved - No Idea
> why. The build should be independent of target os and arch. This follows when creating the installable product.
>
> Warning: file C:\Program Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\RxTxComm_feature\feature.xml, line
> 31: Plug-in reference 'RxTxComm.linux.i686' cannot be resolved
>
This is just the PDE compiler complaining that given the current environment, the filters of those fragments aren't
valid. This is nothing to worry about.

>
> II)
> For any reason the build crashes while a package cannot be resolved:
>
> Error: file C:\Program
> Files\Jenkins\jobs\AlereServiceSoftware\workspace\serviceRCP\com.alere.service.hivnat.ueye.ui\src\com\alere\service\hivnat\ueye\ui\UEyeCameraView.java,
> line 44: The import com.alere.ids cannot be resolved
>
> Compiling the exactly same code using the eclipse IDE (Project->Build automatically) works fine and using buckminster a
> site.p2 action can be performed - in headless it does not work.
>
Then there must be some difference in either the workspace or the target platform. The builder is the same in both
cases. I suggest you use Buckminster headless to create the workspace and then start your IDE on that workspace to get a
better view of the problem.

HTH,
- thomas
Previous Topic:No component named ... is known to Buckminster
Next Topic:How to read a JAR from an SVN-Repository ?
Goto Forum:
  


Current Time: Wed Apr 24 20:30:48 GMT 2024

Powered by FUDForum. Page generated in 0.02971 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top