Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » problems with workspace while materializing from headless buckminster
problems with workspace while materializing from headless buckminster [message #648882] Fri, 14 January 2011 21:48 Go to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Hello Buckminsterers --

I'm now working on calling Buckminster headlessly from the command line to do a cross platform build.

I've installed Buckminster, installed a target platform with the delta pack, imported a target platform into buckminster, told it to always use that. I've listed my target definitions and seen it there with the proper workspace

I've checked out my main feature project into my workspace

THE PROBLEM:
When I tell buckminster to import it is not looking in my workspace for the feature that is already there.

The buckminster command I'm running is roughly:
buckminster import -P /usr/local/bla/workspace/features/_feature_my.feature/buckmi nster.properties -C -consoleLog -data /usr/local/bla/workspace/ /usr/local/bla/workspace/features/_feature_my.feature/_featu re_my.feature.cquery

As an experiment, I made a subdirectory:
/usr/local/bla/workspace/workspace
and a subdirectory in that
/usr/local/bla/workspace/workspace/features
checked out my feature into that subdirectory

Then I ran a similar import referencing that nested workspace directory
buckminster import -P /usr/local/bla/workspace/workspace/features/_feature_my.feat ure/buckminster.properties -data /usr/local/bla/workspace/ -C -consoleLog /usr/local/bla/workspace/workspace/features/_feature_my.feat ure/_feature_my.feature.cquery

This worked, and materialized all the components into the parent workspace directory where I wanted them.

SO ... any suggestions as to how I can force and confirm what workspace buckminster is using?

thanks

Tamar

Re: problems with workspace while materializing from headless buckminster [message #648886 is a reply to message #648882] Fri, 14 January 2011 22:53 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
hm. never mind, I tried it again in a clean workspace and it seemed to work, after about 9 failures. weird.
Re: problems with workspace while materializing from headless buckminster [message #648888 is a reply to message #648886] Fri, 14 January 2011 23:00 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Actually now what I find is if I first manually check out the feature at the root of the workspace, when it materializes it checks out another copy under features/ in the workspace. If I check it out into features/ in the workspace, it does not find the project. Is there a way to tell the workspace to find a project in the features directory that has been manually checked out by svn?
Re: problems with workspace while materializing from headless buckminster [message #649013 is a reply to message #648888] Mon, 17 January 2011 09:34 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
On 15.01.2011 00:00, Tamar Cohen wrote:
> Actually now what I find is if I first manually check out the feature at
> the root of the workspace, when it materializes it checks out another
> copy under features/ in the workspace. If I check it out into features/
> in the workspace, it does not find the project. Is there a way to tell
> the workspace to find a project in the features directory that has been
> manually checked out by svn?

Yes, with a reader type 'local'. The workspace location can be found in
the property buckminster.workspace.root

Best regards,
Johannes
Re: problems with workspace while materializing from headless buckminster [message #649359 is a reply to message #649013] Tue, 18 January 2011 21:39 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Thanks, Johannes -- it seems I am having a general problem with the workspace. I created it by just doing a mkdir, an svn checkout of the main feature, and then telling buckminster where the workspace was with -data during each command.

When I try to do a buckminster build, after materialization, giving it the properties file and the workspace (even after adding the buckminster.workspace.root property per your suggestion), I get a workspace is closed exception:

java.lang.IllegalStateException: Workspace is closed.
at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(Reso urcesPlugin.java:367)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.<init >(InternalWorkspaceJob.java:27)
at org.eclipse.core.resources.WorkspaceJob.<init>(WorkspaceJob.java:60)
at org.eclipse.buckminster.core.materializer.WorkspaceBindingIn stallJob. <init>(WorkspaceBindingInstallJob.java:60)

Is there a buckminster call that I should be using instead to create the workspace?

There is a lack of documentation on all the steps to do this headlessly, which I will try to remedy once I figure this out.

thanks for all the help

Tamar

[Updated on: Tue, 18 January 2011 21:40]

Report message to a moderator

Re: problems with workspace while materializing from headless buckminster [message #649371 is a reply to message #649359] Tue, 18 January 2011 23:39 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Hi Tamar

On 18.01.2011 22:39, Tamar Cohen wrote:
> Thanks, Johannes -- it seems I am having a general problem with the
> workspace. I created it by just doing a mkdir, an svn checkout of the
> main feature, and then telling buckminster where the workspace was with
> -data during each command.

I am not quite sure where your problems come from. Are you executing
both these commmands in a script file, or as individual commands from a
e.g. batch script? If the later is the case, could it be possible that
the second invocation gets executed before the first invocation has shut
down and that your workspace is therefore still locked?
That's just random guessing though...

Here is how I (and AFAIK quite a few other people) work with the local
resolver:
I do my builds in Hudson and Hudson is doing the checkout from the
repository. Now Buckminster is started with -data pointing to the folder
containing all the checked out projects and a script file that contains
one or more resolves/import and the actions I want executed.

The RMAP contains two separate readers for the projects that come from
the repository. The first reader is a local reader that expects all
projects to be in the workspace root. This is for the build
machine/hudson since the checkout is done by an external tool in that case.
The second reader is for developer machines and fetches everything
directly from the source repository.

Here's an example of how such a setup could look like:

<rm:searchPath name="yoursources">
<rm:provider componentTypes="osgi.bundle,eclipse.feature"
readerType="local">
<rm:uri format="file:///{0}/{1}/">
<bc:propertyRef key="workspace.root"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
<rm:provider
componentTypes="eclipse.feature,osgi.bundle,buckminster" readerType="cvs">
<rm:uri
format=":extssh:{0}@yourserver:22/var/share/cvs/,your/module{1} ">
<bc:propertyRef key="cvs.user"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
</rm:searchPath>


Best regards,
Johannes
Re: problems with workspace while materializing from headless buckminster [message #649444 is a reply to message #649371] Wed, 19 January 2011 09:20 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Hi Johannes --

I do not have Hudson and I am setting up to write a script that can be invoked manually or by a cron job. I am experimenting by manually calling each command; the previous command returns so I expect it has finished but I will check the processes to make sure.

I have reproduced the error now three times with clean, fresh workspaces.

I am also having trouble with the loglevel -- neither --loglevel nor -L seem to be valid parameters so that I can have a more verbose log level.

it seems that most of the documentation I have found (on the wiki and on various blogs / presentations) have to do with using Hudson to do builds and not with just calling Buckminster with command line!

any other insights will be greatly appreciated.

thanks

Tamar
Re: problems with workspace while materializing from headless buckminster [message #649464 is a reply to message #649444] Wed, 19 January 2011 10:29 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Hi Tamar,

--loglevel is correct. Is it possible that you pass --loglevel at the
wrong position?

Maybe you should try using a command script that contains all your
commands instead of passing them indivually. That's faster and that way
you can be sure that there no process stays open.

Am 19.01.2011 10:20, schrieb Tamar Cohen:
> it seems that most of the documentation I have found (on the wiki and on
> various blogs / presentations) have to do with using Hudson to do builds
> and not with just calling Buckminster with command line!

The Buckminster Book should contain all relevant information on how to
use Buckminster from commandline.
The Hudson Plugin invokes Buckminster also by command line, so
everything you see in blogs/tutorials concerning using Buckminster in
Hudson also applies to using Buckminster from command line. It works
exactly the same way.

Best regards,
Johannes
Re: problems with workspace while materializing from headless buckminster [message #649583 is a reply to message #649464] Wed, 19 January 2011 19:39 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Hi Johannes --

thank you for the tip -- it seems that using a script corrects my workspace and loglevel problem. Now I have a simple script set up and I am trying to tell Buckminster to build, but it does not seem to be building.

Questions:
Do you think it's possible that my parameters are not getting passed in in general if I am not using a script?

Is there a place to look for .log files that may tell me more information?

I run my script this way:
buckminster -data /usr/local/irg/path/workspace/ -L DEBUG -consoleLog -P /usr/local/path/buckminster.properties -S build_simple3.script

is passing properties that way correct? If not, how should I set the buckminster properties?

When I run the script, it says eclipse.buildId=unknown. Is this a problem?

Here is the output when it runs, if it is helpful:
!SESSION 2011-01-19 11:30:04.912 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -L DEBUG -P /usr/local/path/buckminster.properties -S build_simple3.script
Command-line arguments: -data /usr/local/path/workspace/ -L DEBUG -consoleLog -P /usr/local/path/buckminster.properties -S build_simple3.script

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-19 11:30:05.985
!MESSAGE importtargetdefinition '-A' '/usr/local/path/3.6.1_Installed.target'
importtargetdefinition '-A' '/usr/local/path/3.6.1_Installed.target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:08.879
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:08.881
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-19 11:30:08.989
!MESSAGE setpref 'baseline=3.6.1_Installed_Target'
setpref 'baseline=3.6.1_Installed_Target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:09.022
!MESSAGE Preference 'baseline' set to the value '3.6.1_Installed_Target'
Preference 'baseline' set to the value '3.6.1_Installed_Target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:09.022
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:09.023
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-19 11:30:09.231
!MESSAGE clean
clean

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:09.341
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:09.342
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-19 11:30:09.549
!MESSAGE build
build

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:09.553
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 11:30:09.553
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

Thanks so much for all your help; I really want this to work!

Tamar



Re: problems with workspace while materializing from headless buckminster [message #649587 is a reply to message #649583] Wed, 19 January 2011 19:58 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Oh and for the record here is what is in my buckminster install via listsite:

Features:
org.eclipse.buckminster.core.headless.feature (%featureName)
org.eclipse.buckminster.cvs.headless.feature (%featureName)
org.eclipse.buckminster.git.headless.feature (%featureName)
org.eclipse.buckminster.pde.headless.feature (%featureName)
org.eclipse.buckminster.product (Buckminster Product)
org.eclipse.buckminster.subversive.headless.feature (%featureName)
org.eclipse.equinox.p2.director.feature (%featureName)


Does the pde.headless.feature contain what is needed to compile?
Re: problems with workspace while materializing from headless buckminster [message #649624 is a reply to message #649583] Wed, 19 January 2011 22:58 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Hi Tamar,

please see comments inline.

On 19.01.2011 20:39, Tamar Cohen wrote:

> Questions:
> Do you think it's possible that my parameters are not getting passed in
> in general if I am not using a script?
>

No, it should work without a script, but command lines can be quite
tricky with quoting, shell magic and so on...
I just find it helpful to limit down the potential problem sources when
something isn't working, that's why I asked you to switch to a script
file for the time being.

> Is there a place to look for .log files that may tell me more information?
>

The regular eclipse mechanism is used, so the logfile appears in
WORKSPACE/.metadata/.log, but that should contain about the same
information that gets printed out with loglevel debug.

> I run my script this way:
> buckminster -data /usr/local/irg/path/workspace/ -L DEBUG -consoleLog -P
> /usr/local/path/buckminster.properties -S build_simple3.script
>
> is passing properties that way correct? If not, how should I set the
> buckminster properties?
>

Yes, that's fine

> When I run the script, it says eclipse.buildId=unknown. Is this a problem?
>

No, that's fine.

> Here is the output when it runs, if it is helpful:
> !SESSION 2011-01-19 11:30:04.912
> -----------------------------------------------
....

Your output seems to be just fine, I see no errors.
However, you don't seem to invoke a build action, so I'm not sure what
you expect to happen.

Just in case this is unclear:
The 'build' command simply triggers a full workspace build (same as when
you hit 'clean' in eclipse). So this does not create any artifacts, it
just executes all the project builders.
If you want to create an artifact of some sort you need a
'perform your.component.id#your.attribute' command

So let's say you want to build a p2 update site from an eclipse feature
called 'org.example.foobar'. The command to do this would be
perform org.example.foobar#site.p2

Which attributes (or build actions if you want to call it that way) are
available on a specific component depend on the type of component (plain
java, maven, osgi, eclipse feature,...).
It's best to try this out in your IDE before working with headless
buckminster. Right click on a project (for example an osgi bundle or
eclipse feature) -> buckminster -> invoke action


The artifacts will end up in ${buckminster.output.root} which defaults
to user.tmp if not specified in your properties file.

Best regards,
Johannes
Re: problems with workspace while materializing from headless buckminster [message #649629 is a reply to message #649624] Thu, 20 January 2011 00:30 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Hi Johannes --

thanks again for your response -- I do think I have a good understanding of invoking a buckminster action, as I have created create.product and create.product.zip which I have invoked from the UI and headless. These actions do operate, and they create p2 update site and copy files around and all that.

HOWEVER when they have done that if I have called it headlessly, there are no compiled java class files in the jars. This tells me the build (ie java compile) did not happen, and when I explore my workspace I see some bin/ folders but they are empty.

So what I am trying to do is explicitly call the build on the workspace such that it will do the eclipse build and generate the java class files. I have checked my full projects into svn so the eclipse builders should be defined.

What should the build action in a script file do? shouldn't it build my workspace? I'm having the feeling that I am missing some core feature or plugins from my headless buckminster install or something.

Thanks

Tamar

[Updated on: Thu, 20 January 2011 00:31]

Report message to a moderator

Re: problems with workspace while materializing from headless buckminster [message #649630 is a reply to message #649629] Thu, 20 January 2011 01:08 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
I just did an experiment where I called out a particular plugin and invoked the action java.binaries on it to see if that would compile. It did not, and here is the buckminster output from that attempt.

I'm also wondering if buckminster is not looking correctly at my target platform?

!SESSION 2011-01-19 16:59:18.326 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -L DEBUG --displaystacktrace -S build_simple4.script
Command-line arguments: -data /usr/local/path/workspace/ -L DEBUG -consoleLog --displaystacktrace -S build_simple4.script

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-19 16:59:19.431
!MESSAGE importtargetdefinition '-A' '/usr/local/path/3.6.1_Installed.target'
importtargetdefinition '-A' '/usr/local/path/3.6.1_Installed.target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:22.564
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:22.565
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-19 16:59:22.683
!MESSAGE setpref 'baseline=3.6.1_Installed_Target'
setpref 'baseline=3.6.1_Installed_Target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:22.718
!MESSAGE Preference 'baseline' set to the value '3.6.1_Installed_Target'
Preference 'baseline' set to the value '3.6.1_Installed_Target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:22.719
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:22.720
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-19 16:59:22.928
!MESSAGE perform '-P' '/usr/local/path/buckminster.properties' 'plugin.id#java.binaries'
perform '-P' '/usr/local/path/buckminster.properties' 'plugin.id#java.binaries'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:22.974
!MESSAGE Platform install location: /path/buckminster
Platform install location: /path/buckminster

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:22.985
!MESSAGE Target platform provided by class org.eclipse.buckminster.pde.internal.PDETargetPlatform
Target platform provided by class org.eclipse.buckminster.pde.internal.PDETargetPlatform

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:23.228
!MESSAGE Actions to perform (in order)
org.apache.log4j:osgi.bundle$1.2.15#eclipse.build
gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild
Actions to perform (in order)
org.apache.log4j:osgi.bundle$1.2.15#eclipse.build
gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:23.232
!MESSAGE init actor: eclipse.build[org.apache.log4j:osgi.bundle$1.2.15#eclipse.bu ild]
init actor: eclipse.build[org.apache.log4j:osgi.bundle$1.2.15#eclipse.bu ild]

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-19 16:59:23.233
!MESSAGE [start org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
buckminster.component=org.apache.log4j
workspace.root=/usr/local/path/workspace
buckminster.temp=/usr/local/path/buckminster_tmp/buckminster _test.tmp/org.apache.log4j_1.2.15-osgi.bundle/temp
buckminster.home=/usr/local/path/workspace/plugins/org.apach e.log4j/
localhost=bla.bla
generator.buildTimestamp.format=2011-01-20T00:59:23.218+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.2.15
target.nl=en_US
eclipse.home=/path/buckminster
INFO: [start org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
buckminster.component=org.apache.log4j
workspace.root=/usr/local/path/workspace
buckminster.temp=/usr/local/path/buckminster_tmp/buckminster _test.tmp/org.apache.log4j_1.2.15-osgi.bundle/temp
buckminster.home=/usr/local/path/workspace/plugins/org.apach e.log4j/
localhost=bla.bla
generator.buildTimestamp.format=2011-01-20T00:59:23.218+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.2.15
target.nl=en_US
eclipse.home=/path/buckminster

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-19 16:59:23.233
!MESSAGE [end org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
INFO: [end org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:23.234
!MESSAGE init actor: eclipse.build[plugin.id:osgi.bundle$1.0.0.qualifier#eclipse. build]
init actor: eclipse.build[plugin.id:osgi.bundle$1.0.0.qualifier#eclipse. build]

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-19 16:59:23.234
!MESSAGE [start plugin.id:osgi.bundle$1.0.0.qualifier#eclipse.build]
buckminster.component=plugin.id
workspace.root=/usr/local/path/workspace
buckminster.temp=/usr/local/path/buckminster_tmp/buckminster _test.tmp/plugin.id_1.0.0-osgi.bundle/temp
buckminster.home=/usr/local/path/workspace/plugins/plugin.id /
localhost=bla.bla
generator.buildTimestamp.format=2011-01-20T00:59:23.218+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.0.0.qualifier
target.nl=en_US
eclipse.home=/path/buckminster
INFO: [start plugin.id:osgi.bundle$1.0.0.qualifier#eclipse.build]
buckminster.component=plugin.id workspace.root=/usr/local/path/workspace
buckminster.temp=/usr/local/path/buckminster_tmp/buckminster _test.tmp/plugin.id_1.0.0-osgi.bundle/temp
buckminster.home=/usr/local/path/workspace/plugins/plugin.id /
localhost=bla.bla
generator.buildTimestamp.format=2011-01-20T00:59:23.218+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.0.0.qualifier
target.nl=en_US
eclipse.home=/path/buckminster

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-19 16:59:23.234
!MESSAGE [end plugin.id:osgi.bundle$1.0.0.qualifier#eclipse.build]
INFO: [end plugin.id:osgi.bundle$1.0.0.qualifier#eclipse.build]

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:23.235
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-19 16:59:23.236
!MESSAGE Waiting for jobs to end
Waiting for jobs to end
Re: problems with workspace while materializing from headless buckminster [message #649694 is a reply to message #649629] Thu, 20 January 2011 10:52 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Am 20.01.2011 01:30, schrieb Tamar Cohen:
> thanks again for your response -- I do think I have a good
> understanding of invoking a buckminster action, as I have created
> create.product and create.product.zip which I have invoked from the UI
> and headless. These actions do operate, and they create p2 update site
> and copy files around and all that.
>
> HOWEVER when they have done that, there are no compiled java class files
> in the jars. This tells me the build (ie java compile) did not happen,
> and when I explore my workspace I see some bin/ folders but they are empty.

That sounds odd indeed.
There is one thing I could think of. I've seen some really weird issues
when people installed buckminster with the p2 director by giving a
relative destination location instead of an absolute one.
Is it possible that you passed a relative location to the p2 director
when you first installed headless buckminster?

Best regards,
Johannes
Re: problems with workspace while materializing from headless buckminster [message #649839 is a reply to message #649694] Thu, 20 January 2011 17:39 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Hi Johannes --

nope, I used the full path. I installed headless buckminster following the directions on the wiki, that is starting with director, then doing:

director -r http://download.eclipse.org/tools/buckminster/headless-3.6/ -d <buckminster install folder, full path> -p Buckminster -i org.eclipse.buckminster.cmdline.product

I then used buckminster install to install from
http://download.eclipse.org/tools/buckminster/headless-3.6/
the following:
org.eclipse.buckminster.core.headless.feature
org.eclipse.buckminster.pde.headless.feature

and from cloudsmith the subversive feature

I have done this now at least 6 times, most recent being this morning, with the same behavior. Should I be getting buckminster a different way? Is there something wrong with this release of buckminster?

Tamar
Re: problems with workspace while materializing from headless buckminster [message #649857 is a reply to message #649630] Thu, 20 January 2011 18:10 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik LindbergFriend
Messages: 2501
Registered: July 2009
Senior Member
On 1/20/11 2:08 AM, Tamar Cohen wrote:
> I just did an experiment where I called out a particular plugin and
> invoked the action java.binaries on it to see if that would compile. It
> did not, and here is the buckminster output from that attempt.
>
afaik, java.binaries, and many other actions rely on the fact that the
workspace is built - the action actually just collects what was built.

A major difference between running in the IDE and headless is that the
IDE typically has "build automatically" turned on, whereas it is turned
off in the headless (by design).

The steps are:
- obtain the things to build (query, or already there)
- issue a build action
- then the action you want

Regards
- henrik
Re: problems with workspace while materializing from headless buckminster [message #649868 is a reply to message #649839] Thu, 20 January 2011 19:32 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Where is the actual code that does the eclipse workspace building? I would like to dig into my buckminster install and find that to make sure it is there.

thanks
Re: problems with workspace while materializing from headless buckminster [message #649916 is a reply to message #649868] Thu, 20 January 2011 23:36 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik LindbergFriend
Messages: 2501
Registered: July 2009
Senior Member
For java that would be JDT and then PDE.
- henrik

On 1/20/11 8:32 PM, Tamar Cohen wrote:
> Where is the actual code that does the eclipse workspace building? I
> would like to dig into my buckminster install and find that to make sure
> it is there.
>
> thanks
Re: problems with workspace while materializing from headless buckminster [message #649918 is a reply to message #649916] Fri, 21 January 2011 00:02 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Thanks Henrik -- that is what I though, and those plugins are installed.

It seems as though buckminster IS calling the eclipse.build action. My eclipse.home seems to be my current buckminster install. Is there some other way for me to check why java class files are not being generated?

I have tested this by doing the same steps from the non-headless buckminster which is installed in my target platform and that works perfectly.

thanks again for your help

Tamar

Here is my output with full paths included ...

!SESSION 2011-01-20 14:18:03.015 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -P buckminster.properties -L DEBUG -S verve_build_simple4.script
Command-line arguments: -P buckminster.properties -data /usr/local/irg/eclipse_build/verve_knrover_workspace -consoleLog -L DEBUG -S verve_build_simple4.script

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:04.090
!MESSAGE importtargetdefinition '-A' '/usr/local/irg/eclipse_build/3.6.1_Installed.target'
importtargetdefinition '-A' '/usr/local/irg/eclipse_build/3.6.1_Installed.target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.083
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.084
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:07.192
!MESSAGE setpref 'baseline=3.6.1_Installed_Target'
setpref 'baseline=3.6.1_Installed_Target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.224
!MESSAGE Preference 'baseline' set to the value '3.6.1_Installed_Target'
Preference 'baseline' set to the value '3.6.1_Installed_Target'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.224
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.225
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:07.433
!MESSAGE clean
clean

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.550
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.551
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:07.760
!MESSAGE perform '-P' '/usr/local/irg/eclipse_build/buckminster.properties' 'gov.nasa.arc.irg.util#java.binaries'
perform '-P' '/usr/local/irg/eclipse_build/buckminster.properties' 'gov.nasa.arc.irg.util#java.binaries'

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.809
!MESSAGE Platform install location: /hosts/sudoko/root/projects/www/buckminster_nope
Platform install location: /hosts/sudoko/root/projects/www/buckminster_nope

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.819
!MESSAGE Target platform provided by class org.eclipse.buckminster.pde.internal.PDETargetPlatform
Target platform provided by class org.eclipse.buckminster.pde.internal.PDETargetPlatform

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.065
!MESSAGE Actions to perform (in order)
org.apache.log4j:osgi.bundle$1.2.15#eclipse.build
gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild
Actions to perform (in order)
org.apache.log4j:osgi.bundle$1.2.15#eclipse.build
gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.069
!MESSAGE init actor: eclipse.build[org.apache.log4j:osgi.bundle$1.2.15#eclipse.bu ild]
init actor: eclipse.build[org.apache.log4j:osgi.bundle$1.2.15#eclipse.bu ild]

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.070
!MESSAGE [start org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
buckminster.component=org.apache.log4j
workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm p_verve/org.apache.log4j_1.2.15-osgi.bundle/temp
buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_ workspace/plugins/org.apache.log4j/
buckminster.output=/usr/local/irg/eclipse_build/verve_knrove r_rcp/org.apache.log4j_1.2.15-osgi.bundle
localhost=bla
generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.2.15
target.nl=en_US
eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e
INFO: [start org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
buckminster.component=org.apache.log4j
workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm p_verve/org.apache.log4j_1.2.15-osgi.bundle/temp
buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_ workspace/plugins/org.apache.log4j/
buckminster.output=/usr/local/irg/eclipse_build/verve_knrove r_rcp/org.apache.log4j_1.2.15-osgi.bundle
localhost=bla
generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.2.15
target.nl=en_US
eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.070
!MESSAGE [end org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
INFO: [end org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.071
!MESSAGE init actor: eclipse.build[gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualif ier#eclipse.build]
init actor: eclipse.build[gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualif ier#eclipse.build]

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.071
!MESSAGE [start gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild]
buckminster.component=gov.nasa.arc.irg.util
workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm p_verve/gov.nasa.arc.irg.util_1.0.0-osgi.bundle/temp
buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_ workspace/plugins/gov.nasa.arc.irg.util/
buckminster.output=/usr/local/irg/eclipse_build/verve_knrove r_rcp/gov.nasa.arc.irg.util_1.0.0-osgi.bundle
localhost=bla
generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.0.0.qualifier
target.nl=en_US
eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e
INFO: [start gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild]
buckminster.component=gov.nasa.arc.irg.util
workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm p_verve/gov.nasa.arc.irg.util_1.0.0-osgi.bundle/temp
buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_ workspace/plugins/gov.nasa.arc.irg.util/
buckminster.output=/usr/local/irg/eclipse_build/verve_knrove r_rcp/gov.nasa.arc.irg.util_1.0.0-osgi.bundle
localhost=bla
generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
buckminster.component.type=osgi.bundle
buckminster.version=1.0.0.qualifier
target.nl=en_US
eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e

!ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.072
!MESSAGE [end gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild]
INFO: [end gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild]

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.073
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.073
!MESSAGE Waiting for jobs to end
Waiting for jobs to end


Re: problems with workspace while materializing from headless buckminster [message #649919 is a reply to message #649918] Fri, 21 January 2011 00:49 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik LindbergFriend
Messages: 2501
Registered: July 2009
Senior Member
I assume you are checking in the .project files?
Have seen issues when people decide not to do that and instead rely on
that they are regenerated when creating projects on checkout (and then
relying on that the workspace defaults are what they want).

Anyway, that has been a source of mysterious problems in the past.

What happens if you start the IDE on the workspace that was
created/prepared for the headless buckminster? Does it build? See any
odd things?

- henrik

On 1/21/11 1:02 AM, Tamar Cohen wrote:
> Thanks Henrik -- that is what I though, and those plugins are installed.
> It seems as though buckminster IS calling the eclipse.build action. My
> eclipse.home seems to be my current buckminster install. Is there some
> other way for me to check why java class files are not being generated?
> I have tested this by doing the same steps from the non-headless
> buckminster which is installed in my target platform and that works
> perfectly.
>
> thanks again for your help
>
> Tamar
>
> Here is my output with full paths included ...
>
> !SESSION 2011-01-20 14:18:03.015
> -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_20
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> Framework arguments: -P buckminster.properties -L DEBUG -S
> verve_build_simple4.script
> Command-line arguments: -P buckminster.properties -data
> /usr/local/irg/eclipse_build/verve_knrover_workspace -consoleLog -L
> DEBUG -S verve_build_simple4.script
>
> !ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:04.090
> !MESSAGE importtargetdefinition '-A'
> '/usr/local/irg/eclipse_build/3.6.1_Installed.target'
> importtargetdefinition '-A'
> '/usr/local/irg/eclipse_build/3.6.1_Installed.target'
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.083
> !MESSAGE Doing full workspace refresh
> Doing full workspace refresh
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.084
> !MESSAGE Waiting for jobs to end
> Waiting for jobs to end
>
> !ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:07.192
> !MESSAGE setpref 'baseline=3.6.1_Installed_Target'
> setpref 'baseline=3.6.1_Installed_Target'
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.224
> !MESSAGE Preference 'baseline' set to the value '3.6.1_Installed_Target'
> Preference 'baseline' set to the value '3.6.1_Installed_Target'
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.224
> !MESSAGE Doing full workspace refresh
> Doing full workspace refresh
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.225
> !MESSAGE Waiting for jobs to end
> Waiting for jobs to end
>
> !ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:07.433
> !MESSAGE clean
> clean
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.550
> !MESSAGE Doing full workspace refresh
> Doing full workspace refresh
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.551
> !MESSAGE Waiting for jobs to end
> Waiting for jobs to end
>
> !ENTRY org.eclipse.buckminster.runtime 0 293 2011-01-20 14:18:07.760
> !MESSAGE perform '-P'
> '/usr/local/irg/eclipse_build/buckminster.properties'
> 'gov.nasa.arc.irg.util#java.binaries'
> perform '-P' '/usr/local/irg/eclipse_build/buckminster.properties'
> 'gov.nasa.arc.irg.util#java.binaries'
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.809
> !MESSAGE Platform install location:
> /hosts/sudoko/root/projects/www/buckminster_nope
> Platform install location: /hosts/sudoko/root/projects/www/buckminster_nope
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:07.819
> !MESSAGE Target platform provided by class
> org.eclipse.buckminster.pde.internal.PDETargetPlatform
> Target platform provided by class
> org.eclipse.buckminster.pde.internal.PDETargetPlatform
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.065
> !MESSAGE Actions to perform (in order)
> org.apache.log4j:osgi.bundle$1.2.15#eclipse.build
> gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild
> Actions to perform (in order)
> org.apache.log4j:osgi.bundle$1.2.15#eclipse.build
> gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.069
> !MESSAGE init actor:
> eclipse.build[org.apache.log4j:osgi.bundle$1.2.15#eclipse.bu ild]
> init actor: eclipse.build[org.apache.log4j:osgi.bundle$1.2.15#eclipse.bu
> ild]
>
> !ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.070
> !MESSAGE [start org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
> buckminster.component=org.apache.log4j
> workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
> buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm
> p_verve/org.apache.log4j_1.2.15-osgi.bundle/temp
> buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_
> workspace/plugins/org.apache.log4j/
> buckminster.output=/usr/local/irg/eclipse_build/verve_knrove
> r_rcp/org.apache.log4j_1.2.15-osgi.bundle
> localhost=bla
> generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
> buckminster.component.type=osgi.bundle
> buckminster.version=1.2.15
> target.nl=en_US
> eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e
> INFO: [start org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
> buckminster.component=org.apache.log4j
> workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
> buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm
> p_verve/org.apache.log4j_1.2.15-osgi.bundle/temp
> buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_
> workspace/plugins/org.apache.log4j/
> buckminster.output=/usr/local/irg/eclipse_build/verve_knrove
> r_rcp/org.apache.log4j_1.2.15-osgi.bundle
> localhost=bla
> generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
> buckminster.component.type=osgi.bundle
> buckminster.version=1.2.15
> target.nl=en_US
> eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e
>
> !ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.070
> !MESSAGE [end org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
> INFO: [end org.apache.log4j:osgi.bundle$1.2.15#eclipse.build]
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.071
> !MESSAGE init actor:
> eclipse.build[gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualif
> ier#eclipse.build]
> init actor: eclipse.build[gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualif
> ier#eclipse.build]
>
> !ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.071
> !MESSAGE [start
> gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild]
> buckminster.component=gov.nasa.arc.irg.util
> workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
> buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm
> p_verve/gov.nasa.arc.irg.util_1.0.0-osgi.bundle/temp
> buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_
> workspace/plugins/gov.nasa.arc.irg.util/
> buckminster.output=/usr/local/irg/eclipse_build/verve_knrove
> r_rcp/gov.nasa.arc.irg.util_1.0.0-osgi.bundle
> localhost=bla
> generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
> buckminster.component.type=osgi.bundle
> buckminster.version=1.0.0.qualifier
> target.nl=en_US
> eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e
> INFO: [start
> gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild]
> buckminster.component=gov.nasa.arc.irg.util
> workspace.root=/usr/local/irg/eclipse_build/verve_knrover_wo rkspace
> buckminster.temp=/usr/local/irg/eclipse_build/buckminster_tm
> p_verve/gov.nasa.arc.irg.util_1.0.0-osgi.bundle/temp
> buckminster.home=/usr/local/irg/eclipse_build/verve_knrover_
> workspace/plugins/gov.nasa.arc.irg.util/
> buckminster.output=/usr/local/irg/eclipse_build/verve_knrove
> r_rcp/gov.nasa.arc.irg.util_1.0.0-osgi.bundle
> localhost=bla
> generator.buildTimestamp.format=2011-01-20T22:18:08.055+0000
> buckminster.component.type=osgi.bundle
> buckminster.version=1.0.0.qualifier
> target.nl=en_US
> eclipse.home=/hosts/sudoko/root/projects/www/buckminster_nop e
>
> !ENTRY org.eclipse.buckminster.core 1 293 2011-01-20 14:18:08.072
> !MESSAGE [end
> gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu ild]
> INFO: [end gov.nasa.arc.irg.util:osgi.bundle$1.0.0.qualifier#eclipse.bu
> ild]
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.073
> !MESSAGE Doing full workspace refresh
> Doing full workspace refresh
>
> !ENTRY org.eclipse.buckminster.core 0 293 2011-01-20 14:18:08.073
> !MESSAGE Waiting for jobs to end
> Waiting for jobs to end
>
>
>
Re: problems with workspace while materializing from headless buckminster [message #650118 is a reply to message #649919] Fri, 21 January 2011 19:39 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Hi Henrik --

yes, I am checking in .project and .settings and all associated files into version control. I can open eclipse on that workspace -- however, it shows no projects! probably because the projects are under features/ and plugins/ as this is how Buckminster materialized them.

After I 'import projects into workspace' from the gui, and then exit eclipse and run buckminster / build from my script, it finally builds.

So it seems that despite the fact that I used buckminster to materialize the projects, since they were placed in child features/ and plugins/ folders they were not added to the workspace.

Where can I tell Buckminster to put them at the root of the workspace during materialization?

thanks

Tamar
Re: problems with workspace while materializing from headless buckminster [message #650139 is a reply to message #650118] Fri, 21 January 2011 21:33 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Hi Tamar,

On 21.01.2011 20:39, Tamar Cohen wrote:
> Hi Henrik --
>
> yes, I am checking in .project and .settings and all associated files
> into version control. I can open eclipse on that workspace -- however,
> it shows no projects! probably because the projects are under features/
> and plugins/ as this is how Buckminster materialized them.
>

No, something was not correct in that workspace. If the projects would
have been materialized correctly, they should have been visible when you
open that workspace with a regular eclipse.

> After I 'import projects into workspace' from the gui, and then exit
> eclipse and run buckminster / build from my script, it finally builds.
>
> So it seems that despite the fact that I used buckminster to materialize
> the projects, since they were placed in child features/ and plugins/
> folders they were not added to the workspace.
>
> Where can I tell Buckminster to put them at the root of the workspace
> during materialization?
>

You can do that with an mspec, but the features/ plugins/ layout was not
your problem. Eclipse decides according to the settings in .metadata
what projects are contained in the workspace. The physical location in
the filesystem doesn't matter.


The question remains though why your projects did not get imported
correctly. Is there maybe a prebind action defined in one of the bundles
that could have crashed during the import?
If you start with a completely new and empty workspace, does it still
not work?


Best regards,
Johannes
Re: problems with workspace while materializing from headless buckminster [message #650151 is a reply to message #650139] Fri, 21 January 2011 23:31 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
Hi Johannes --

so what I have now found is that if I do the materialize and build in the same script, the workspace knows about the projects. If I have already materialized in a separate call to buckminster, then the workspace does not know about the projects despite the fact that I have passed in that workspace.

Tamar
Re: problems with workspace while materializing from headless buckminster [message #650164 is a reply to message #650151] Sat, 22 January 2011 03:32 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik LindbergFriend
Messages: 2501
Registered: July 2009
Senior Member
Are you by any chance invoking something that causes the first step to
crash and thus not save the workspace on exit?

Does it work if you, on the command line, use buckminster to first
materialize and then build?

- henrik

On 1/22/11 12:31 AM, Tamar Cohen wrote:
> Hi Johannes --
>
> so what I have now found is that if I do the materialize and build in
> the same script, the workspace knows about the projects. If I have
> already materialized in a separate call to buckminster, then the
> workspace does not know about the projects despite the fact that I have
> passed in that workspace.
>
> Tamar
Re: problems with workspace while materializing from headless buckminster [message #650371 is a reply to message #650164] Mon, 24 January 2011 16:36 Go to previous messageGo to next message
Tamar Cohen is currently offline Tamar CohenFriend
Messages: 100
Registered: July 2009
Senior Member
AHA!

Thanks to both of you for your support -- I have realized that I had not properly specified the delta pack in my target platform definition, and one of my dependencies was for something from the delta pack.

I'm wondering if there's a way for Buckminster to populate the workspace with projects as they are materialized? It seems to me this issue would cause compilation errors but given that the source code existed in the workspace it would have been less confusing if the workspace knew about the projects...

thanks again for all the help! I will be presenting my talk on using Buckminster to people from many NASA centers later today. Smile

Tamar
Re: problems with workspace while materializing from headless buckminster [message #650434 is a reply to message #650371] Mon, 24 January 2011 20:25 Go to previous message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Hi Tamar,

it's great that it's finally working for you.

Am 24.01.2011 17:36, schrieb Tamar Cohen:
>
> I'm wondering if there's a way for Buckminster to populate the workspace
> with projects as they are materialized? It seems to me this issue would
> cause compilation errors but given that the source code existed in the
> workspace it would have been less confusing if the workspace knew about
> the projects...

That is what buckminster is doing. When it resolves and materializes
components, it binds them into the Eclipse workspace. If that isn't
working for you then something is going wrong. The only thing that comes
to mind is a buckminster.prebind action that fails, or, as Henrik
mentioned, that your eclipse crashes/doesn't properly shut down at some
point and therefore doesn't persist the metadata.

Best regards,
Johannes
Previous Topic:Approach for splitting Buckminster jobs in Hudson
Next Topic:New versions published to our repository
Goto Forum:
  


Current Time: Sun Dec 21 10:11:10 GMT 2014

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

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