Eclipse Community Forums: Buckminster » Error in headless build but not during import

Help

Home

Home » Archived » Buckminster » Error in headless build but not during import

Show: Today's Messages :: Show Polls :: Message Navigator

Error in headless build but not during import [message #519119]

Sat, 06 March 2010 18:06

Patrick Ruckstuhl

Messages: 65
Registered: July 2009

Member

The import step worked fine, but in the build step I get the following error

Error: file /home/build/tmp/ch.ethz.origo.aranea.messagedsl.build/workspace/plugins/ch.ethz.origo.aranea.messagedsl: The container 'Plug-in Dependencies' references non existing library '/home/build/tmp/eclipse/plugins/org.antlr.gen_3.0.1.v201002021559'

If I check the destination it looks like the correct location for the dependency.

Building from the UI also works fine.

Report message to a moderator

Re: Error in headless build but not during import [message #519195 is a reply to message #519119]

Sun, 07 March 2010 22:55

Patrick Ruckstuhl

Messages: 65
Registered: July 2009

Member

I did some further testing.

If I checkout the projects manually into the workspace from eclipse, it compiles.

If I make the import using buckminster and then launch the workspace in eclipse, I get the same error.

What could be the difference between a normal svn checkout into the workspace and what buckminster does? (Could it be that buckminster uses subclipse and eclipse subversive?)

What can I do to further track this problem down?

The build project can be found here

https://svn.origo.ethz.ch/aranea/trunk/dev/ch.ethz.origo.ara nea.messagedsl.build/

and currently expects buckminster headless to be installed and also have a target eclipse that consists of an eclipse xtext distribution 0.8 M5

I'm running on Linux64 bit.

Thanks for any ideas and help.

Report message to a moderator

Re: Error in headless build but not during import [message #519219 is a reply to message #519195]

Mon, 08 March 2010 06:55

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

Hi Patrick,
I think the problem is that you don't issue a build between the import and the perform so the workspace is inconsistent.
Try adding:

<buckminster command="build" workspace="${workspacePath}"/>

just after the import.

HTH,
- thomas

On 03/07/2010 11:55 PM, Patrick Ruckstuhl wrote:
> I did some further testing.
>
> If I checkout the projects manually into the workspace from eclipse, it
> compiles.
>
> If I make the import using buckminster and then launch the workspace in
> eclipse, I get the same error.
>
> What could be the difference between a normal svn checkout into the
> workspace and what buckminster does? (Could it be that buckminster uses
> subclipse and eclipse subversive?)
>
> What can I do to further track this problem down?
>
> The build project can be found here
>
> https://svn.origo.ethz.ch/aranea/trunk/dev/ch.ethz.origo.ara nea.messagedsl.build/
>
>
> and currently expects buckminster headless to be installed and also have
> a target eclipse that consists of an eclipse xtext distribution 0.8 M5
>
> I'm running on Linux64 bit.
>
> Thanks for any ideas and help.

Report message to a moderator

Re: Error in headless build but not during import [message #519226 is a reply to message #519119]

Mon, 08 March 2010 08:05

Patrick Ruckstuhl

Messages: 65
Registered: July 2009

Member

The situation is that after the checkout I first need to perform a generation action before the build or otherwise the build will never succeed.

So what I tried (and does not work)

-import
-generate additional source files
-build

Report message to a moderator

Re: Error in headless build but not during import [message #520175 is a reply to message #519119]

Thu, 11 March 2010 13:10

Patrick Ruckstuhl

Messages: 65
Registered: July 2009

Member

I did some more testing.

-import
-build (which will fail)
-generate additional source
-build again

results in the same error

The way I can manually fix the issue is by doing the following

-import with buckminster
-open workspace manually in eclipse
-remove "Plugin dependency" from classpath
-readd "Plugin dependency" to classpath
-everything is ok and I can also do a build from buckminster

But this is not a viable solution as it requires manual intervention, totally unusable in a headless build for testing.

Does anyone have any idea what I could further try? I really think buckminster looks very promising and I would love to use it as it would do (in theory) exactly what I need. But I'm really at a loss of what could be the problem :( Sad