Home » Archived » Buckminster » Buckminster: targetPlatform materialize fails silently
| Buckminster: targetPlatform materialize fails silently [message #380395] |
Tue, 14 October 2008 18:12  |
 Rich Scott
Messages: 63
Registered: July 2009 |
Member |
|
|
Back in July I successful in getting things setup to materialize a
targetPlatform for our RCP development using Buckminster. I have a feature
defined that is dependent upon all of the eclipse features/plugins that
are required for our eclipse product. I setup a new project that contained
a CQUERYand RMAP to do the materialize. In July I was able to generate the
targetPlatform as desired. At that point I was running Ganymede with
current updates. I ran the process through the Resolve Wizard on the
CQUERY.
I want to bring the targetPlatform up to date with 3.4.1 updates, but can
not get it to work. When run as before (ie pressing "Resolve to Wizard"
from cspec) it finishes the resolve processing, I had it save the bom for
reference, and then the wizard asks for the materialize info. I indicated
destination type=targetPlatform and provided the directory where the
platform should be built. Pressing finish, the dialog immediately closes
and no messages. I've checked the Error Log and scanned through the entire
eclipse directory structure for .log files and have found no messages. I
have tried this with the targetPlatform initialized to the 3.4.1 RCP-SDK
with the 3.4.1 delta pack added, and also with an empty directory. Same
results both ways.
To simplify testing and give more info for debugging, I tried to do the
same processing from a provided mspec. I get the same results.
The MSPEC, CQUERY, and RMAP follow. I have the BOM, but its 3310 lines so
I have not included it here.
Any thoughts about what I am doing wrong, or what has changed?
Thanks
Rich Scott
MSPEC:
--------------------
<?xml version="1.0" encoding="UTF-8"?>
<md:mspec xmlns:md="http://www.eclipse.org/buckminster/MetaData-1.0"
materializer="targetPlatform"
name="ceTarget"
conflictResolution="UPDATE"
installLocation="d:/rls/eclipse/3.4.1/ceTarget/eclipse"
url="targetPlatform.cquery">
</md:mspec>
CQUERY:
----------------------
<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery
xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
resourceMap="targetPlatform.rmap">
<cq:rootRequest name="org.c.r.chr.eclipseplugins.feature"
componentType="eclipse.feature"/>
<cq:advisorNode namePattern="Source"
componentType="osgi.bundle" sourceLevel="DESIRE"/>
</cq:componentQuery>
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="eclipse">
<provider readerType="eclipse.import"
componentTypes="eclipse.feature,osgi.bundle,buckminster"
source="false">
<uri format="http://download.eclipse.org/releases/ganymede">
<bc:propertyRef key="buckminster.component" />
</uri>
</provider>
</searchPath>
<locator searchPathRef="eclipse" pattern="org.eclipse*" />
<locator searchPathRef="eclipse" pattern="org.sat4j" />
</rmap>
|
|
| | | |
| Re: Any Ideas? Re: Buckminster: targetPlatform materialize fails silently [message #380417 is a reply to message #380415] |
Tue, 28 October 2008 07:28  |
|
Hi Rich,
One thing that is always very helpful is if you could create a sample based on publicly
available components and attach that to a bugzilla. That would give us a chance to
reproduce the problem and also verify its solution.
Regards,
Thomas Hallgren
Rich Scott wrote:
> Thomas,
>
> Thanks for pointer. Unfortunately, I still get no log info during the
> materialize processing with debug. I also set -consoleLog to try and be
> sure I was not missing the log file.
>
> I'm currently getting setup to run the materialize outside of the IDE,
> using headless buckminster, to see if I can get any more information
> there. I will post the results of that work tomorrow.
>
> Rich Scott
>
> Thomas Hallgren wrote:
>
>> Hi Rich,
>> It's not easy to figure out what's going on here. Don't you get
>> anything in
> the log? Not
>> even if you run in DEBUG mode?
>
>> Regards,
>> Thomas Hallgren
>
>> Rich Scott wrote:
>>> Still have not been able to solve this problem. Does anyone have an
>>> idea about what the issue may be, or how to approach tracking it down?
>>>
>>> Thanks
>>> Rich
>>>
>
>
|
|
|
| Re: Any Ideas? Re: Buckminster: targetPlatform materialize fails silently [message #380420 is a reply to message #380417] |
Wed, 29 October 2008 11:24 |
Rich Scott
Messages: 63
Registered: July 2009 |
Member |
|
|
Thomas,
In trying to create the sample for a bugzilla, I ended up fixing the
problem. Unfortunately I don't know specifically what caused it. The fix
was to recreate my workspace and reimport my preferences and projects.
Here is what I did:
* Created a new empty workspace and created copies of the two
projects required. The first is a feature that is dependent on all of the
eclipse plugins that my application needs, the second contains the
buckminster files to materialize the target platform.
* Sanitized the names in the copied projects so that they could be
submitted as a test case for a bugzilla report.
* Tested the materialize and it worked.
* So I tested copies of the original projects in the new workspace and
they worked.
* Copied the test projects back to my original workspace and the
materialize silently failed.
* Used buckminster preferences to "clear URL Cache" and "Refresh meta
data", the buckminster import still fails
* Recreated development workspace, reset preferences, and imported all
projects. Then reran the original buckminster import and it worked as
expected.
So it looks like some saved state in my workspace was causing the problem.
Everything now seems to be working as I had hoped.
If there is any more info you would like, let me know.
Thanks for your pointers.
Rich
Thomas Hallgren wrote:
> Hi Rich,
> One thing that is always very helpful is if you could create a sample based
on publicly
> available components and attach that to a bugzilla. That would give us a
chance to
> reproduce the problem and also verify its solution.
> Regards,
> Thomas Hallgren
> Rich Scott wrote:
>> Thomas,
>>
>> Thanks for pointer. Unfortunately, I still get no log info during the
>> materialize processing with debug. I also set -consoleLog to try and be
>> sure I was not missing the log file.
>>
>> I'm currently getting setup to run the materialize outside of the IDE,
>> using headless buckminster, to see if I can get any more information
>> there. I will post the results of that work tomorrow.
>>
>> Rich Scott
>>
>> Thomas Hallgren wrote:
>>
>>> Hi Rich,
>>> It's not easy to figure out what's going on here. Don't you get
>>> anything in
>> the log? Not
>>> even if you run in DEBUG mode?
>>
>>> Regards,
>>> Thomas Hallgren
>>
>>> Rich Scott wrote:
>>>> Still have not been able to solve this problem. Does anyone have an
>>>> idea about what the issue may be, or how to approach tracking it down?
>>>>
>>>> Thanks
>>>> Rich
>>>>
>>
>>
|
|
|
| Re: Any Ideas? Re: Buckminster: targetPlatform materialize fails silently [message #381435 is a reply to message #380420] |
Fri, 05 December 2008 19:42 |
Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
Hi Thomas,
I am having the same problem as Rich, but mine won't go away after I
tried a second workspace. I event tried it on an alternate Eclipse
install.
Opened bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=257759
thanks,
John
Rich Scott wrote:
> Thomas,
>
> In trying to create the sample for a bugzilla, I ended up fixing the
> problem. Unfortunately I don't know specifically what caused it. The fix
> was to recreate my workspace and reimport my preferences and projects.
> Here is what I did:
>
>
> * Created a new empty workspace and created copies of the two
> projects required. The first is a feature that is dependent on all of
> the eclipse plugins that my application needs, the second contains the
> buckminster files to materialize the target platform.
> * Sanitized the names in the copied projects so that they could be
> submitted as a test case for a bugzilla report.
> * Tested the materialize and it worked.
> * So I tested copies of the original projects in the new workspace
> and they worked.
> * Copied the test projects back to my original workspace and the
> materialize silently failed.
> * Used buckminster preferences to "clear URL Cache" and "Refresh meta
> data", the buckminster import still fails
> * Recreated development workspace, reset preferences, and imported
> all projects. Then reran the original buckminster import and it worked
> as expected.
>
> So it looks like some saved state in my workspace was causing the problem.
>
> Everything now seems to be working as I had hoped.
>
> If there is any more info you would like, let me know.
>
> Thanks for your pointers.
>
> Rich
>
>
>
> Thomas Hallgren wrote:
>
>> Hi Rich,
>> One thing that is always very helpful is if you could create a sample
>> based
> on publicly
>> available components and attach that to a bugzilla. That would give us a
> chance to
>> reproduce the problem and also verify its solution.
>
>> Regards,
>> Thomas Hallgren
>
>
>> Rich Scott wrote:
>>> Thomas,
>>>
>>> Thanks for pointer. Unfortunately, I still get no log info during the
>>> materialize processing with debug. I also set -consoleLog to try and
>>> be sure I was not missing the log file.
>>>
>>> I'm currently getting setup to run the materialize outside of the
>>> IDE, using headless buckminster, to see if I can get any more
>>> information there. I will post the results of that work tomorrow.
>>>
>>> Rich Scott
>>>
>>> Thomas Hallgren wrote:
>>>
>>>> Hi Rich,
>>>> It's not easy to figure out what's going on here. Don't you get
>>>> anything in
>>> the log? Not
>>>> even if you run in DEBUG mode?
>>>
>>>> Regards,
>>>> Thomas Hallgren
>>>
>>>> Rich Scott wrote:
>>>>> Still have not been able to solve this problem. Does anyone have an
>>>>> idea about what the issue may be, or how to approach tracking it down?
>>>>>
>>>>> Thanks
>>>>> Rich
>>>>>
>>>
>>>
>
>
|
|
| |
Goto Forum:
Current Time: Fri Apr 19 15:50:09 GMT 2024
Powered by FUDForum. Page generated in 0.01626 seconds |
] 
Search
Help
Register
Login
Home
