Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » headless build fails resolving plugins
headless build fails resolving plugins [message #533803] Mon, 17 May 2010 03:44 Go to next message
Bernhard Merkle is currently offline Bernhard Merkle
Messages: 88
Registered: July 2009
Member
Hi,

I run buckminster headless to build a project which requires Xpand

importtargetdefinition and import runs fine, however the following "build" fails resolving the Xpand plugins...

buckminster.bat -consoleLog -L DEBUG -data file:///W:/Buckminster_SopasGenerator build
Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF, line 24: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF, line 25: Bundle 'org.eclipse.xtend' cannot be resolved
Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF, line 22: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF, line 23: Bundle 'org.eclipse.xpand' cannot be resolved

Do you have any idea why buckminster headless can not resolve them ?

As an indication, the same error msgs is also displayed in the Eclipse IDE (non headless) but after a "clean" or "build project" the plugins are found and the msg disapears.

I looked into the plugin registry and the relevant plugins are inactive after the startup of the IDE and just go activated after "build" in the IDE>

however how can I achieve this in buckminster headless ?

am I on the wrong path ? is there any sample ?

thanks,
Bernhard.
Re: headless build fails resolving plugins [message #533925 is a reply to message #533803] Mon, 17 May 2010 09:37 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3208
Registered: July 2009
Senior Member
Hi Bernhard,
Do you get the same errors if you use the --thorough option?

- thomas

On 05/17/2010 09:44 AM, Bernhard Merkle wrote:
> Hi,
>
> I run buckminster headless to build a project which requires Xpand
>
> importtargetdefinition and import runs fine, however the following
> "build" fails resolving the Xpand plugins...
>
> buckminster.bat -consoleLog -L DEBUG -data
> file:///W:/Buckminster_SopasGenerator build
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 24: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 25: Bundle 'org.eclipse.xtend' cannot be resolved
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 22: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 23: Bundle 'org.eclipse.xpand' cannot be resolved
>
> Do you have any idea why buckminster headless can not resolve them ?
>
> As an indication, the same error msgs is also displayed in the Eclipse
> IDE (non headless) but after a "clean" or "build project" the plugins
> are found and the msg disapears.
>
> I looked into the plugin registry and the relevant plugins are inactive
> after the startup of the IDE and just go activated after "build" in the
> IDE>
>
> however how can I achieve this in buckminster headless ?
>
> am I on the wrong path ? is there any sample ?
>
> thanks,
> Bernhard.
>
Re: headless build fails resolving plugins [message #534028 is a reply to message #533925] Mon, 17 May 2010 14:40 Go to previous messageGo to next message
Bernhard Merkle is currently offline Bernhard Merkle
Messages: 88
Registered: July 2009
Member
Hi Thomas

if i use build --thorough the error remains the same unfortunately.

is there any example of buckminster using also xpand (e.g. b3 ?).
Maybe I could use that as a example/template project ?

What I am puzzeled is that the error is also in eclipse IDE first.
Then when I do a rebuild the bundles are started. How does bucky handle
that ?

thanks again for your help
Berni.

C:\ide\ibm\buckminster-headless-3.5>buckminster.bat -consoleLog -L DEBUG
-data file:///W:/Buckminster_SopasGenerator build --thorough
!SESSION 2010-05-17 20:36:04.156
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments: -L DEBUG build --thorough
Command-line arguments: -consoleLog -L DEBUG -data
file:///W:/Buckminster_SopasGenerator build --thorough

!ENTRY org.eclipse.buckminster.runtime 0 293 2010-05-17 20:36:05.671
!MESSAGE build '--thorough'
build '--thorough'
......

Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
line 26: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
line 27: Bundle 'org.eclipse.xpand' cannot be resolved
Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
line 28: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
line 29: Bundle 'org.eclipse.xtend' cannot be resolved


On 17.05.2010 15:37, Thomas Hallgren wrote:
> Hi Bernhard,
> Do you get the same errors if you use the --thorough option?
>
> - thomas
>
> On 05/17/2010 09:44 AM, Bernhard Merkle wrote:
>> Hi,
>>
>> I run buckminster headless to build a project which requires Xpand
>>
>> importtargetdefinition and import runs fine, however the following
>> "build" fails resolving the Xpand plugins...
>>
>> buckminster.bat -consoleLog -L DEBUG -data
>> file:///W:/Buckminster_SopasGenerator build
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 24: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 25: Bundle 'org.eclipse.xtend' cannot be resolved
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 22: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 23: Bundle 'org.eclipse.xpand' cannot be resolved
>>
>> Do you have any idea why buckminster headless can not resolve them ?
>>
>> As an indication, the same error msgs is also displayed in the Eclipse
>> IDE (non headless) but after a "clean" or "build project" the plugins
>> are found and the msg disapears.
>>
>> I looked into the plugin registry and the relevant plugins are inactive
>> after the startup of the IDE and just go activated after "build" in the
>> IDE>
>>
>> however how can I achieve this in buckminster headless ?
>>
>> am I on the wrong path ? is there any sample ?
>>
>> thanks,
>> Bernhard.
>>
>
Re: headless build fails resolving plugins [message #534030 is a reply to message #534028] Mon, 17 May 2010 14:54 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3208
Registered: July 2009
Senior Member
Hi Bernhard,

The error seems to stem from the PDE Manifest builder. You can turn them into warnings by using a preference setting for
that compiler on an empty workspace that you zip up and then use as a template workspace. Perhaps that can be used as a
workaround.

I don't know why some plug-ins doesn't get activated before you build in the IDE but I promise I'll bring that up with
the PDE team if you can provide a reproducible use-case in a bugzilla.

- thomas

On 05/17/2010 08:40 PM, Bernhard Merkle wrote:
> Hi Thomas
>
> if i use build --thorough the error remains the same unfortunately.
>
> is there any example of buckminster using also xpand (e.g. b3 ?).
> Maybe I could use that as a example/template project ?
>
> What I am puzzeled is that the error is also in eclipse IDE first.
> Then when I do a rebuild the bundles are started. How does bucky handle
> that ?
>
> thanks again for your help
> Berni.
>
> C:\ide\ibm\buckminster-headless-3.5>buckminster.bat -consoleLog -L DEBUG
> -data file:///W:/Buckminster_SopasGenerator build --thorough
> !SESSION 2010-05-17 20:36:04.156
> -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_20
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
> Framework arguments: -L DEBUG build --thorough
> Command-line arguments: -consoleLog -L DEBUG -data
> file:///W:/Buckminster_SopasGenerator build --thorough
>
> !ENTRY org.eclipse.buckminster.runtime 0 293 2010-05-17 20:36:05.671
> !MESSAGE build '--thorough'
> build '--thorough'
> ......
>
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 26: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 27: Bundle 'org.eclipse.xpand' cannot be resolved
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 28: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
> line 29: Bundle 'org.eclipse.xtend' cannot be resolved
>
>
> On 17.05.2010 15:37, Thomas Hallgren wrote:
>> Hi Bernhard,
>> Do you get the same errors if you use the --thorough option?
>>
>> - thomas
>>
>> On 05/17/2010 09:44 AM, Bernhard Merkle wrote:
>>> Hi,
>>>
>>> I run buckminster headless to build a project which requires Xpand
>>>
>>> importtargetdefinition and import runs fine, however the following
>>> "build" fails resolving the Xpand plugins...
>>>
>>> buckminster.bat -consoleLog -L DEBUG -data
>>> file:///W:/Buckminster_SopasGenerator build
>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>> line 24: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>> line 25: Bundle 'org.eclipse.xtend' cannot be resolved
>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>> line 22: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>> line 23: Bundle 'org.eclipse.xpand' cannot be resolved
>>>
>>> Do you have any idea why buckminster headless can not resolve them ?
>>>
>>> As an indication, the same error msgs is also displayed in the Eclipse
>>> IDE (non headless) but after a "clean" or "build project" the plugins
>>> are found and the msg disapears.
>>>
>>> I looked into the plugin registry and the relevant plugins are inactive
>>> after the startup of the IDE and just go activated after "build" in the
>>> IDE>
>>>
>>> however how can I achieve this in buckminster headless ?
>>>
>>> am I on the wrong path ? is there any sample ?
>>>
>>> thanks,
>>> Bernhard.
>>>
>>
>
Re: headless build fails resolving plugins [message #534050 is a reply to message #534030] Mon, 17 May 2010 15:44 Go to previous message
Bernhard Merkle is currently offline Bernhard Merkle
Messages: 88
Registered: July 2009
Member
okay. I use now the warning-instead-of-error workaround. Thanks !
Actually it can be activated project specific so i do not need to create
the template workspace (I prefer to have it only in that project).

thanks again for your help. I will try to create a reproducable use-case
and file a bugzilla (probably next week).

thanks,
Berni.


On 17.05.2010 20:54, Thomas Hallgren wrote:
> Hi Bernhard,
>
> The error seems to stem from the PDE Manifest builder. You can turn them
> into warnings by using a preference setting for that compiler on an
> empty workspace that you zip up and then use as a template workspace.
> Perhaps that can be used as a workaround.
>
> I don't know why some plug-ins doesn't get activated before you build in
> the IDE but I promise I'll bring that up with the PDE team if you can
> provide a reproducible use-case in a bugzilla.
>
> - thomas
>
> On 05/17/2010 08:40 PM, Bernhard Merkle wrote:
>> Hi Thomas
>>
>> if i use build --thorough the error remains the same unfortunately.
>>
>> is there any example of buckminster using also xpand (e.g. b3 ?).
>> Maybe I could use that as a example/template project ?
>>
>> What I am puzzeled is that the error is also in eclipse IDE first.
>> Then when I do a rebuild the bundles are started. How does bucky handle
>> that ?
>>
>> thanks again for your help
>> Berni.
>>
>> C:\ide\ibm\buckminster-headless-3.5>buckminster.bat -consoleLog -L DEBUG
>> -data file:///W:/Buckminster_SopasGenerator build --thorough
>> !SESSION 2010-05-17 20:36:04.156
>> -----------------------------------------------
>> eclipse.buildId=unknown
>> java.version=1.6.0_20
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
>> Framework arguments: -L DEBUG build --thorough
>> Command-line arguments: -consoleLog -L DEBUG -data
>> file:///W:/Buckminster_SopasGenerator build --thorough
>>
>> !ENTRY org.eclipse.buckminster.runtime 0 293 2010-05-17 20:36:05.671
>> !MESSAGE build '--thorough'
>> build '--thorough'
>> ......
>>
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 26: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 27: Bundle 'org.eclipse.xpand' cannot be resolved
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 28: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>> line 29: Bundle 'org.eclipse.xtend' cannot be resolved
>>
>>
>> On 17.05.2010 15:37, Thomas Hallgren wrote:
>>> Hi Bernhard,
>>> Do you get the same errors if you use the --thorough option?
>>>
>>> - thomas
>>>
>>> On 05/17/2010 09:44 AM, Bernhard Merkle wrote:
>>>> Hi,
>>>>
>>>> I run buckminster headless to build a project which requires Xpand
>>>>
>>>> importtargetdefinition and import runs fine, however the following
>>>> "build" fails resolving the Xpand plugins...
>>>>
>>>> buckminster.bat -consoleLog -L DEBUG -data
>>>> file:///W:/Buckminster_SopasGenerator build
>>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>>> line 24: Bundle 'org.eclipse.emf.mwe.utils' cannot be resolved
>>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>>> line 25: Bundle 'org.eclipse.xtend' cannot be resolved
>>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>>> line 22: Bundle 'org.eclipse.emf.mwe.core' cannot be resolved
>>>> Error: file W:\Buckminster_SopasGenerator\CodeGen\META-INF\MANIFEST.MF,
>>>> line 23: Bundle 'org.eclipse.xpand' cannot be resolved
>>>>
>>>> Do you have any idea why buckminster headless can not resolve them ?
>>>>
>>>> As an indication, the same error msgs is also displayed in the Eclipse
>>>> IDE (non headless) but after a "clean" or "build project" the plugins
>>>> are found and the msg disapears.
>>>>
>>>> I looked into the plugin registry and the relevant plugins are inactive
>>>> after the startup of the IDE and just go activated after "build" in the
>>>> IDE>
>>>>
>>>> however how can I achieve this in buckminster headless ?
>>>>
>>>> am I on the wrong path ? is there any sample ?
>>>>
>>>> thanks,
>>>> Bernhard.
>>>>
>>>
>>
>
Previous Topic:Buckminster+Hudson: Broken Encoding
Next Topic:Target definition
Goto Forum:
  


Current Time: Wed Apr 16 18:54:28 EDT 2014

Powered by FUDForum. Page generated in 0.01982 seconds