| Hudson-Buckminster No suitable provider [message #499609] |
Mon, 23 November 2009 14:33  |
 TW 
Messages: 62
Registered: November 2009 |
Member |
|
|
Hi,
I´m trying to set up a buckminster headless Build of my Eclipse RCP. I´ve installed a hudson server and created a RCP Project while following the tutorial on http://www.ralfebert.de/blog/eclipsercp/rcp_builds/
Everything worked fine until I want to build my hudson-job.
When I´m try to build I get the following error:
Gestartet durch Benutzer anonymous
Commandline:
java -Dbuckminster.output.root=/C:/hudson/jobs/rcp_target/workspace//buckminster.output -Dbuckminster.temp.root=/C:/hudson/jobs/rcp_target/workspace//buckminster.temp -DtargetPlatformPath=C:/buckminsterTargetPlatform -jar plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar -application org.eclipse.buckminster.cmdline.headless -data /C:/hudson/jobs/rcp_target/workspace/ --loglevel info -S C:\hudson\jobs\rcp_target\builds\2009-11-23_15-13-24/commands.txt INFO: import 'file:///D:/workspaces/buckminster/com.example.target/target.mspec'
ERROR [0001] : No suitable provider for component com.example.target:eclipse.feature was found in resourceMap file:/D:/workspaces/buckminster/com.example.target/target-resources.rmap
ERROR [0001] : No suitable provider for component com.example.target:eclipse.feature was found in searchPath default
ERROR [0001] : Resolution attempt ended with exception: Provider local(file:///C:/hudson/jobs/rcp_target/workspace/com.example.target/): Missing CSpec source required by component type eclipse.feature
ERROR Provider local(file:///C:/hudson/jobs/rcp_target/workspace/com.example.target/): Missing CSpec source required by component type eclipse.feature
INFO: TAG-ID 0001 = Query for com.example.target:eclipse.feature
Archiviere Artefakte
Finished: FAILURE
I´ve checked my files and compared them to the ones in the tutorial. I think that everything is fine
I´ve even downloaded the original code from the tutorial which is available on [ CODEhttp://github.com/ralfebert/com.example.mail.buckminster][/CODE].
Doe´s anybody has a solution for my problem?
Thanks
[Updated on: Tue, 24 November 2009 06:58] Report message to a moderator |
|
|
| Re: Hudson-Buckminster No suitable provider [message #499682 is a reply to message #499609] |
Mon, 23 November 2009 17:04  |
Johannes Utzig
Messages: 329
Registered: July 2009 |
Senior Member |
|
|
Hi,
I would say that it's very likely that your rmap simply points to a
wrong directory. You probably use a local resolver and look for
${buckminster.component} in workspace root?
It is important to know that buckminster component is the ID, the name
of the component. So if your feature ID is com.example.target, make sure
that the directory where to find that feature xml really is
'${workspace.root}/com.example.target'.
Many people seem to have suffixes like -feature, or .feature at their
feature projects. This will work as well with buckminster, but you need
to state that properly in the rmap. For example you can have 2 different
providers within a searchpath. One applies only for osgi.bundle and
points to something like file:{0}/{1} where {0} is workspace.root and
{1} is buckminster.component. The other only applies for eclipse.feature
component types and points to file:{0}/{1}-suffix
That way buckminster will look for the correct directory name depending
on the type of component.
As a side note, you have more / than necessary in your path:
file:///C:/hudson/jobs/rcp_target/workspace/com.example.targ et/
It should still work, but you might want to fix it anyway.
If that does not help you, it would be best if you'd post your rmap here
and explain how the physical structure of your workspace looks like.
Best regards,
Johannes
TW schrieb:
> Hi,
>
> I´m trying to set up a buckminster headless Build of my Eclipse RCP.
> I´ve installed a hudson server and created a RCP Project while following
> the tutorial on http://www.ralfebert.de/blog/eclipsercp/rcp_builds/
>
> Everything worked fine until I want to build my hudson-job.
>
> When I´m try to build I get the following error:
> Gestartet durch Benutzer anonymous
> Commandline: java
> -Dbuckminster.output.root=/C:/hudson/jobs/rcp_target/workspa ce//buckminster.output
> -Dbuckminster.temp.root=/C:/hudson/jobs/rcp_target/workspace //buckminster.temp
> -DtargetPlatformPath=C:/buckminsterTargetPlatform -jar
> plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715. jar
> -application org.eclipse.buckminster.cmdline.headless -data
> /C:/hudson/jobs/rcp_target/workspace/ --loglevel info -S
> C:\hudson\jobs\rcp_target\builds\2009-11-23_15-13-24/command s.txt INFO:
> import ' file:///D:/workspaces/buckminster/com.example.target/target. mspec'
> ERROR [0001] : No suitable provider for component
> com.example.target:eclipse.feature was found in resourceMap
> file:/D:/workspaces/buckminster/com.example.target/target-re sources.rmap
> ERROR [0001] : No suitable provider for component
> com.example.target:eclipse.feature was found in searchPath default
> ERROR [0001] : Resolution attempt ended with exception: Provider
> local( file:///C:/hudson/jobs/rcp_target/workspace/com.example.targ et/):
> Missing CSpec source required by component type eclipse.feature
> ERROR Provider
> local( file:///C:/hudson/jobs/rcp_target/workspace/com.example.targ et/):
> Missing CSpec source required by component type eclipse.feature
> INFO: TAG-ID 0001 = Query for com.example.target:eclipse.feature
>
> Archiviere Artefakte
> Finished: FAILURE
>
> I´ve checked my files and compared them to the ones in the tutorial. I
> think that everythink is fine I´ve even downloaded the original code
> from the tutorial which is available on
> [ CODEhttp://github.com/ralfebert/com.example.mail.buckminster][/CODE].
>
> Doe´s anybody has a solution for my problem?
> Thanks
|
|
|
| Re: Hudson-Buckminster No suitable provider [message #499793 is a reply to message #499682] |
Tue, 24 November 2009 08:04 |
TW
Messages: 62
Registered: November 2009 |
Member |
|
|
Hi,
I think that I´ve done everythink right in my rmap. Maybe I messed up my hudson configuration, but I can´t find anything wrong.
First of all my workspace of my Eclipse project is:
D:\workspaces\buckminster
+ org.example.mail
+ org.example.mail.feature
+ org.example.mail.site
- org.example.target
- target-resources.rmap
- target.mspec
- target.cquery
- feature.xml
- build.properties
This is by the structure that ralf ebert used in his tutorial.
My rmap file (target-resources.rmap):
<?xml version="1.0" encoding="UTF-8"?>
<rmap
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
<searchPath name="resources">
<provider readerType="local" componentTypes="osgi.bundle,eclipse.feature" mutable="true" source="true">
<uri format="file:///{0}/{1}/">
<bc:propertyRef key="workspace.root" />
<bc:propertyRef key="buckminster.component" />
</uri>
</provider>
<provider readerType="eclipse.import" componentTypes="osgi.bundle,eclipse.feature" mutable="false" source="true">
<uri format="http://download.eclipse.org/releases/galileo"/>
</provider>
</searchPath>
<locator searchPathRef="resources"/>
</rmap>
The second provider was used to create the target platform with up to date features and plugins.
Now some additional informations about the resources which are used during the headless build.
- Headless Buckminster : (C:\Buckminsterheadless)
Was installed like described in ralf eberts tutorial and has the important plugin org.eclipse.equinox.p2.director.app....jar
- RCP Target Platform (C:\rcp_target)
Created with "Resolve to Wizard" from target.cquery. Includes "Features", "Plugins" Folder and artifacts.xml File.
- Hudson (C:\hudson)
Installed by setting the home directory to C:\hudson and calling java -jar hudson.war
Buckminster Plugin successfully installed.
Now I´ll post the configuration of hudson and the config of my hudson job(I´m not quite sure if I´ve entered the right information here)
->Hudson Configuration:
-"Buckminster Installations":
Eclipse Buckminster 3.5; 3.5; C:\Buckminsterheadless
->"Free-Style" Job Configuration:
-"Build"
Eclipse Buckminster 3.5; None: Info(Default); import file:///D:/workspaces/buckminster/com.example.target/target. mspec
- "Advanced Options"
-DtargetPlatformPath=file:///C:/buckminsterTargetPlatform
- "Post-Build Actions"
[x] archive and publish an Eclipse Target Platform
Path: C:\buckminsterTargetPlatform
Name: MailApp Target Platform
This is all information that I have.
I´m confused about the error log of my previous message. There hudson wants to look for a cspeq in file:///C:/hudson/jobs ??
Maybe someone can help my by analyzing my data
Thanks for your support
(By the way: Using just two "//" did bring up another error when importing file://D:/ ...)
[Updated on: Tue, 24 November 2009 08:05] Report message to a moderator |
|
|
| Re: Hudson-Buckminster No suitable provider [message #499795 is a reply to message #499793] |
Tue, 24 November 2009 08:21 |
Johannes Utzig
Messages: 329
Registered: July 2009 |
Senior Member |
|
|
Hi,
I think there is a slight missunderstanding going on here. Your own
workspace does not count, when I say workspace, I talk about the
Workspace Hudson will create for your job. The Buckminster PlugIn will
set the eclipse data directory (eclipse workspace) for the build to the
hudson workspace, so those two are identical
> This is all information that I have.
> I´m confused about the error log of my previous message. There hudson
> wants to look for a cspeq in file:///C:/hudson/jobs ??
Exactly, all Hudson Workspaces are in HUDSON_HOME/jobs/JOB_NAME. This is
were your plugins/featues need to be during the build. You have two ways
of doing this, either by letting Buckminster checkout your projects, or
by letting Hudson checkout your projects. Since you're using a local
resolver, I guess you let Hudson do the checkout. Did you confirm that
your hudson job workspace has the right contents? i.e. you open the job,
click on 'Workspace' and see all your plugins and features there?
> Eclipse Buckminster 3.5; None: Info(Default); import
> file:///D:/workspaces/buckminster/com.example.target/target. mspec
This is probably not how you want to do it. Like stated earlier, Hudson
creates its own workspace for every job, so you should use it:
import file:/${WORKSPACE}/com.example.target/target.mspec
Best regards,
Johannes
|
|
|
|
|
| Re: Hudson-Buckminster No suitable provider [message #499835 is a reply to message #499812] |
Tue, 24 November 2009 10:33 |
TW
Messages: 62
Registered: November 2009 |
Member |
|
|
Hi,
ok now I understand the whole thing a lot better. I thought I could turn off CVS/SVN for testing purposes and hudson copies my eclipse workspace into its workspace directory. Now I know that I´m wrong.
I added a StarTeam Plugin to Hudson and configured it. The target platform build now automatically gets the files from the repository and the build succeeds.
The other job which creates the product for the different operation system has also a connection to StarTeam and now copies the workspace code x times to the different locations.
But the build fails because the cspec file in each directory cannot be located.
-> When building the target platform, there was only one workspace folder so it was no problem to import the file with the complete path
Now, when building the product for the os, there are many different workspace folders. At this point I need the ${WORKSPACE} Tag to find the right workspace for each os.
As you explained before this could be a problem with separators "/" because the location would be correct if the system would add them correct.
File not found: file:/C:hudsonjobsproductworkspacearch/x86_64/os/win32/ws/win32/com.example.mail.site/site.cquery
The File is located in C:/hudson/jobs/productworkspace/arch//x86_64/os/win32/ws/win 32/com.example.mail.site/site.cquery
Maybe this is a bug, or we have to change the command when using windows.
If you have a look at that and find a solution I would be glad if you could post this in this thread.
I think if this is fixed my build should work.
Thanks
[Updated on: Tue, 24 November 2009 10:33] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Hudson-Buckminster No suitable provider [message #500124 is a reply to message #499949] |
Wed, 25 November 2009 06:03 |
|
On 2009-11-24 16:06, Johannes Utzig wrote:
> TW schrieb:
>> Hi I just visited the issue tracer to add the bug. Unfortunately there
>> is no option for me to generate a new issue I can only view existing
>> issues.
>> Could you possible add the bug to the issue tracer or tell me where I
>> can generate a new issue?
>>
>> Regards, TW
>
> Well, the plugin writes a correct path to the commands.txt file:
> import C:\hudson\jobs\rcp_target\workspace\com.example.target\targe t.mspec
>
It's a correct path according to a Windows cmd.exe. It's *not* a correct path in terms of the Buckminster shell that
interprets the script file. This shell is like a Linux/Unix shell and will use '\' as the escape character. The correct
path should read:
import C:\\hudson\\jobs\\rcp_target\\workspace\\com.example.target\ \target.mspec
This information is missing in the documentation. I'll add a bugzilla for that.
Regards,
Thomas Hallgren
|
|
|
| Re: Hudson-Buckminster No suitable provider [message #500126 is a reply to message #500124] |
Wed, 25 November 2009 06:26 |
|
On 2009-11-25 07:03, Thomas Hallgren wrote:
> It's a correct path according to a Windows cmd.exe. It's *not* a correct
> path in terms of the Buckminster shell that interprets the script file.
> This shell is like a Linux/Unix shell and will use '\' as the escape
> character. The correct path should read:
>
> import
> C:\\hudson\\jobs\\rcp_target\\workspace\\com.example.target\ \target.mspec
>
> This information is missing in the documentation. I'll add a bugzilla
> for that.
>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=296081
- thomas
|
|
|
| Re: Hudson-Buckminster No suitable provider [message #500128 is a reply to message #500126] |
Wed, 25 November 2009 06:51 |
TW
Messages: 62
Registered: November 2009 |
Member |
|
|
Hi Thomas,
does that mean that I have to wait for a bug fix to use ${workspace}?
If I understand your bugzilla report correctly I can create a workaround by writing a script and then execute that script.
The script itself can have the ${workspace} variable and is interpreted correctly on windows.
[Updated on: Wed, 25 November 2009 06:53] Report message to a moderator |
|
|
| Re: Hudson-Buckminster No suitable provider [message #500135 is a reply to message #500128] |
Wed, 25 November 2009 07:24 |
|
Hi Toby,
On 2009-11-25 07:51, TW wrote:
> Hi Thomas,
>
> does that mean that I have to wait for a bug fix or is there any
> workaround so that I can build my products and tragetplatform using the
> ${workspace} variable on windows?
>
Assuming that Johannes pass a -data ${WORKSPACE} to the buckminster invocation, it should be possible for you to write:
import ${osgi.instance.area}/com.example.target/target.mspec
Then again, since it seems property expansion is made of the actual command, I'm not sure that will work either.
Johannes needs to answer that.
Regards,
Thomas Hallgren
|
|
|
|
| Re: Hudson-Buckminster No suitable provider [message #500148 is a reply to message #500135] |
Wed, 25 November 2009 08:27 |
TW
Messages: 62
Registered: November 2009 |
Member |
|
|
Your hint seems to work for the import command.
-> import ${osgi.instance.area}/com.example.target/target.mspec
and the log says:
*** Get list of all files for C:\hudson\jobs\rcp_target\workspace
*** Looking for versioned files in buckminster
*** Looking for versioned files in com.example.mail
*** Looking for versioned files in src
*** Looking for versioned files in com
*** Looking for versioned files in example
*** Looking for versioned files in mail
*** Looking for versioned files in icons
*** Looking for versioned files in META-INF
*** Looking for versioned files in com.example.mail.feature
*** Looking for versioned files in build
*** Looking for versioned files in com.example.target
*** Looking for versioned files in com.example.mail.site
*** done
*** Performing checkout
*** done
Commandline:
java -Dbuckminster.output.root=/C:/hudson/jobs/rcp_target/workspace//buckminster.output -Dbuckminster.temp.root=/C:/hudson/jobs/rcp_target/workspace//buckminster.temp -DtargetPlatformPath=file:/${workspace.root}/target -jar plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar -application org.eclipse.buckminster.cmdline.headless -data /C:/hudson/jobs/rcp_target/workspace/ --loglevel info -S C:\hudson\jobs\rcp_target\builds\2009-11-25_09-17-00/commands.txt INFO: import 'file:/C:/hudson/jobs/rcp_target/workspace//com.example.target/target.mspec'
...
I also have to set my target platform. This is done in Advanced Options -> JVM Arguments.
Here the call: -DtargetPlatformPath=${osgi.instance.area}/target does not work because the log says:
...
java.io.FileNotFoundException: C:\buckminsterheadless\file:\C:\hudson\jobs\rcp_target\workspace\target\artifacts.xml (Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.save(SimpleArtifactRepository.java:896)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.save(SimpleArtifactRepository.java:877)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.<init>(SimpleArtifactRepository.java:298)
at org.eclipse.equinox.internal.provisional.spi.p2.artifact.repository.SimpleArtifactRepositoryFactory.create(SimpleArtifactRepositoryFactory.java:123)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.factoryCreate(ArtifactRepositoryManager.java:55)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.doCreateRepository(AbstractRepositoryManager.java:272)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.createRepository(ArtifactRepositoryManager.java:48)
at org.eclipse.buckminster.core.materializer.P2Materializer.materialize(P2Materializer.java:196)
at org.eclipse.buckminster.core.materializer.MaterializerJob.run(MaterializerJob.java:70)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
ERROR [0002] : An error occurred while collecting items to be installed
ERROR [0002] : session context was:(profile=file:\C:\hudson\jobs\rcp_target\workspace\target, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=).
ERROR [0002] : Multiple problems occurred while downloading.
ERROR [0002] : Unable to write to repository: file:/C:/buckminsterheadless/file:/C:/hudson/jobs/rcp_target/workspace/target.
ERROR [0002] : Unable to write to repository: file:/C:/buckminsterheadless/file:/C:/hudson/jobs/rcp_target/workspace/target.
...
So in this case ${osgi.instance.area} does not work because somthing goes wrong and buckminster wants to write in the directory, where my buckminsterheadless build is. (C:\buckminsterheadless).
&{workspace} doesn't work because then my target platform is written to C:\buckminsterheadless\$workspace and it is supposed to be in C:\hudson\jobs\rcp_target\workspace\target
The only thing that works is if I use:
-DtargetPlatformPath=${workspace.root}/target
[Updated on: Wed, 25 November 2009 08:33] Report message to a moderator |
|
|
| Re: Hudson-Buckminster No suitable provider [message #500170 is a reply to message #499609] |
Wed, 25 November 2009 09:04 |
TW
Messages: 62
Registered: November 2009 |
Member |
|
|
After the creation of the target Platform was successful I get similar problems when trying to build the product for the different operation systems.
I post you some information about the problem, so that this problem could also be fixed in the new release of the buckminster plugin.
I set up the Build like in the tutorial I was referring to all the time.
Build:
=> Run Buckminster
- Import works perfectly with ${osgi.instance.area}
- I have to set my Target Platform to the platform which is created by my other job
So I select "MailApp Target Platform".
If I try to build the job, the log says:
Gestartet durch vorgelagertes Projekt "mailApp", Build 2
*** Get list of all files for C:\hudson\jobs\mailApp\workspace\arch\x86\os\win32\ws\win32
*** Looking for versioned files in buckminster
*** Looking for versioned files in com.example.mail
*** Looking for versioned files in src
*** Looking for versioned files in com
*** Looking for versioned files in example
*** Looking for versioned files in mail
*** Looking for versioned files in icons
*** Looking for versioned files in META-INF
*** Looking for versioned files in com.example.mail.feature
*** Looking for versioned files in build
*** Looking for versioned files in com.example.target
*** Looking for versioned files in com.example.mail.site
*** done
*** Performing checkout
*** done
Commandline:
java -Dbuckminster.output.root=/C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32//buckminster.output -Dbuckminster.temp.root=/C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32//buckminster.temp -Dtarget.os=win32 -Dtarget.ws=win32 -Dtarget.arch=x86 -jar plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar -application org.eclipse.buckminster.cmdline.headless -data /C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32/ --loglevel info -S C:\hudson\jobs\mailApp\configurations\axis-arch\x86\axis-os\win32\axis-ws\win32\builds\2009-11-25_09-47-25/commands.txt INFO: setpref 'targetPlatformPath=C:hudsonjobs
cp_targetbuilds2009-11-25_09-33-58archive/targetPlatform'
targetPlatformPath set to the value 'C:hudsonjobs
cp_targetbuilds2009-11-25_09-33-58archive/targetPlatform'
INFO: import 'file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32//com.example.mail.site/site.cquery'
ERROR [0000] : No suitable provider for component org.eclipse.rcp:eclipse.feature was found in resourceMap file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32//com.example.mail.site/resources.rmap
ERROR [0000] : No suitable provider for component org.eclipse.rcp:eclipse.feature was found in searchPath resources
ERROR [0000] : Resolution attempt ended with exception: Provider local(file:///C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32/org.eclipse.rcp/): Missing CSpec source required by component type eclipse.feature
ERROR Provider local(file:///C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32/org.eclipse.rcp/): Missing CSpec source required by component type eclipse.feature
ERROR [0000] : No suitable provider for component org.eclipse.ui:osgi.bundle was found in resourceMap file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32//com.example.mail.site/resources.rmap
ERROR [0000] : No suitable provider for component org.eclipse.ui:osgi.bundle was found in searchPath resources
ERROR [0000] : Resolution attempt ended with exception: Provider local(file:///C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32/org.eclipse.ui/): Missing CSpec source required by component type osgi.bundle
ERROR Provider local(file:///C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32/org.eclipse.ui/): Missing CSpec source required by component type osgi.bundle
ERROR [0000] : No suitable provider for component org.eclipse.core.runtime:osgi.bundle was found in resourceMap file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32//com.example.mail.site/resources.rmap
ERROR [0000] : No suitable provider for component org.eclipse.core.runtime:osgi.bundle was found in searchPath resources
ERROR [0000] : Resolution attempt ended with exception: Provider local(file:///C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32/org.eclipse.core.runtime/): Missing CSpec source required by component type osgi.bundle
ERROR Provider local(file:///C:/hudson/jobs/mailApp/workspace/arch/x86/os/win32/ws/win32/org.eclipse.core.runtime/): Missing CSpec source required by component type osgi.bundle
Archiviere Artefakte
Finished: FAILURE
In my opinion the resources are missing, because the target platform cannot be resolved. This may be because buckminster cannot find the target platform.
If I look at commands.txt, I can see that the path is set wrong.
setpref targetPlatformPath="C:\hudson\jobs\rcp_target\builds\2009-11-25_09-33-58\archive/targetPlatform"
import ${osgi.instance.area}/com.example.mail.site/site.cquery
perform com.example.mail.feature#create.product.zip
Maybe there is a workaround. I could call setpref in the commands text field but then I need to get the "C:\hudson\jobs\rcp_target\builds\2009-11-25_09-33-58" path with any kind of variable.
Hope that my concerns are not annoying you that much.
I wonder why I haven't found other developers which have experienced similar problems when using buckminster windows and hudson?
Thanks for all of your support.
@Johannes
I have to write a how to build headless eclipse rcp with hudson and buckminster during my internship. I haven't begun to write how to set up buckminster in eclipse so I will do this exercise first.
-TW
[Updated on: Wed, 25 November 2009 09:08] Report message to a moderator |
|
|
|
|
|
| Re: Hudson-Buckminster No suitable provider [message #500447 is a reply to message #500360] |
Thu, 26 November 2009 08:52 |
TW
Messages: 62
Registered: November 2009 |
Member |
|
|
Hi,
I have some good news but also bad news.
Good news:
Your fix seems to work. I can now export the target platform with the variable &{workspace} and set it as targetplatform successful.
The bad news:
My product build fails. I think this has nothing to do with the old bug or your plugin.
I will describe the error, maybe you did already see something like this. Otherwise I may open a new thread.
When I tried to export my product there was the following message in the error log:
The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project
Archiviere Artefakte
Finished: FAILURE
I searched the web and found, that this could has something to do with missing informations in the ".classpath" file in my com.example.mail plugin.
I did not even add the ".classpath" file to my starteam cvs, because I didn´t want to add all metadata files.
For testing purposes I added the .claspath file to my starteam and built the target platform and produt again.
The target platorm build succeeded like it did before. But the interesting thing happened with the product build.
Here the win32 and win64 build succeeded but the both linux and mac builds failed with the following message:
[ant] C:\Buckminsterheadless\plugins\org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
[ant] file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/macosx/ws/cocoa/buckminster.output/com.example.mail.feature_1.0.0-eclipse.feature/site.p2/
[ant] C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\buckminster.output\com.example.mail.feature_1.0.0-eclipse.feature\Mail
[ant] Cannot complete the install because one or more required items could not be found.
[ant] Software being installed: mail 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB (com.example.mail.product 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB)
[ant] Missing requirement for filter (&(osgi.os=macosx)(osgi.ws=cocoa)(osgi.arch=x86)): Eclipse RCP 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6 (org.eclipse.rcp.feature.group 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6) requires 'org.eclipse.equinox.launcher.cocoa.macosx [1.0.1.R35x_v20090707]' but it could not be found
[ant] Cannot satisfy dependency:
[ant] From: Mail Feature 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB (com.example.mail.feature.feature.group 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB)
[ant] To: org.eclipse.rcp.feature.group [3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6]
[ant] Cannot satisfy dependency:
[ant] From: mail 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB (com.example.mail.product 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB)
[ant] To: com.example.mail.feature.feature.group [1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB]
[ant] Application failed, log file location: C:\Buckminsterheadless\configuration\1259225343890.log
ERROR: org.eclipse.core.runtime.CoreException: C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\com.example.mail.feature\build\product.ant:22: Java returned: 13
org.eclipse.core.runtime.CoreException: C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\com.example.mail.feature\build\product.ant:22: Java returned: 13
at org.eclipse.buckminster.ant.AntRunner.handleInvocationTargetException(AntRunner.java:189)
at org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:352)
at org.eclipse.buckminster.ant.actor.AntActor.internalPerform(AntActor.java:281)
at org.eclipse.buckminster.core.actor.AbstractActor.perform(AbstractActor.java:201)
at org.eclipse.buckminster.core.internal.actor.PerformManager$DirectActionInvocation.execute(PerformManager.java:151)
at org.eclipse.buckminster.core.internal.actor.PerformManager.internalPerform(PerformManager.java:507)
at org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:335)
at org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:350)
at org.eclipse.buckminster.core.commands.Perform.internalRun(Perform.java:118)
at org.eclipse.buckminster.core.commands.WorkspaceCommand.run(WorkspaceCommand.java:191)
at org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(AbstractCommand.java:155)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:341)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:135)
at org.eclipse.buckminster.cmdline.Headless.start(Headless.java:189)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\com.example.mail.feature\build\product.ant:22: Java returned: 13
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:622)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:455)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:344)
... 25 more
C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\com.example.mail.feature\build\product.ant:22: Java returned: 13
Caused by:
Archiviere Artefakte
Finished: FAILURE
In this message a log is mentioned:
..
[ant] Application failed, log file location: C:\Buckminsterheadless\configuration\1259225343890.log
..
The information in the log says:
!SESSION 2009-11-26 09:49:03.609 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments: -application org.eclipse.equinox.p2.director -artifactRepository file:file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/macosx/ws/cocoa/buckminster.output/com.example.mail.feature_1.0.0-eclipse.feature/site.p2/ -metadataRepository file:file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/macosx/ws/cocoa/buckminster.output/com.example.mail.feature_1.0.0-eclipse.feature/site.p2/ -destination C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\buckminster.output\com.example.mail.feature_1.0.0-eclipse.feature\Mail -bundlepool C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\buckminster.output\com.example.mail.feature_1.0.0-eclipse.feature\Mail -profile MailProfile -profileProperties org.eclipse.update.install.features=true -installIU com.example.mail.product -p2.os macosx -p2.ws cocoa -p2.arch x86
Command-line arguments: -application org.eclipse.equinox.p2.director -artifactRepository file:file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/macosx/ws/cocoa/buckminster.output/com.example.mail.feature_1.0.0-eclipse.feature/site.p2/ -metadataRepository file:file:/C:/hudson/jobs/mailApp/workspace/arch/x86/os/macosx/ws/cocoa/buckminster.output/com.example.mail.feature_1.0.0-eclipse.feature/site.p2/ -destination C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\buckminster.output\com.example.mail.feature_1.0.0-eclipse.feature\Mail -bundlepool C:\hudson\jobs\mailApp\workspace\arch\x86\os\macosx\ws\cocoa\buckminster.output\com.example.mail.feature_1.0.0-eclipse.feature\Mail -profile MailProfile -profileProperties org.eclipse.update.install.features=true -installIU com.example.mail.product -p2.os macosx -p2.ws cocoa -p2.arch x86 -consoleLog
!ENTRY org.eclipse.equinox.p2.director 4 1 2009-11-26 09:49:05.281
!MESSAGE Cannot complete the install because one or more required items could not be found.
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2009-11-26 09:49:05.281
!MESSAGE Software being installed: mail 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB (com.example.mail.product 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB)
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2009-11-26 09:49:05.281
!MESSAGE Missing requirement for filter (&(osgi.os=macosx)(osgi.ws=cocoa)(osgi.arch=x86)): Eclipse RCP 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6 (org.eclipse.rcp.feature.group 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6) requires 'org.eclipse.equinox.launcher.cocoa.macosx [1.0.1.R35x_v20090707]' but it could not be found
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2009-11-26 09:49:05.281
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2009-11-26 09:49:05.281
!MESSAGE From: Mail Feature 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB (com.example.mail.feature.feature.group 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB)
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2009-11-26 09:49:05.281
!MESSAGE To: org.eclipse.rcp.feature.group [3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2009-11-26 09:49:05.281
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2009-11-26 09:49:05.281
!MESSAGE From: mail 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB (com.example.mail.product 1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB)
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2009-11-26 09:49:05.281
!MESSAGE To: com.example.mail.feature.feature.group [1.0.0.200911260948-340cLSJ--7S46yAw311_19220_TB]
Does anybody know how to fix this error? I think it´s some kind of jre error because the product build works for the system that I´m running but nor for not for mac and linux.
How can I fix this error?
[Updated on: Thu, 26 November 2009 08:54] Report message to a moderator |
|
|
| Re: Hudson-Buckminster No suitable provider [message #500455 is a reply to message #500447] |
Thu, 26 November 2009 09:08 |
Johannes Utzig
Messages: 329
Registered: July 2009 |
Senior Member |
|
|
Hi,
see comments below
TW schrieb:
> Hi,
>
> I have some good news but also bad news.
>
> Good news:
> Your fix seems to work. I can now export the target platform with the
> variable &{workspace} and set it as targetplatform successful.
Good, I'm glad the fix works for you.
> The bad news:
> My product build fails. I think this has nothing to do with the old bug
> or your plugin.
>
> I will describe the error, maybe you did already see something like
> this. Otherwise I may open a new thread.
>
> When I tried to export my product there was the following message in the
> error log:
> The project was not built since its build path is incomplete. Cannot
> find the class file for java.lang.Object. Fix the build path then try
> building this project
> Archiviere Artefakte
> Finished: FAILURE
>
> I searched the web and found, that this could has something to do with
> missing informations in the ".classpath" file in my com.example.mail
> plugin.
>
> I did not even add the ".classpath" file to my starteam cvs, because I
> didn´t want to add all metadata files.
>
You do need the meta data present, and in fact, in general you should
commit meta data like that to the repository (unless you use maven) so
others are able to run/build your projects without too too much
background knowledge.
> !MESSAGE Missing requirement for filter
> (&(osgi.os=macosx)(osgi.ws=cocoa)(osgi.arch=x86)): Eclipse RCP
> 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6
> (org.eclipse.rcp.feature.group
> 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6) requires
> 'org.eclipse.equinox.launcher.cocoa.macosx [1.0.1.R35x_v20090707]' but
> it could not be found
Is org.eclipse.equinox.launcher.cocoa.macosx [1.0.1.R35x_v20090707] part
of your target platform?
Best regards,
Johannes
|
|
|
|
] 
Search
Help
Register
Login
Home
