|Launch Configuration Changes Unexpectedly Why? [message #53931]
||Mon, 06 April 2009 23:48
| Geoffry Roberts
Registered: July 2009
Today I checked in a project. The app, a headless OSGi thing, was working |
well enough for me so I saved the launch configuration as a shared file to
a location in the project itself and did the commit. We use SVN around
here not that it matters.
My colleague checked the whole mess out, tried to run using the launch,
and no go. The errors looked like a launch configuration problem so we
opened up said launch configuration (Run/Run Configurations.../OSGi
Framework/ourLauncher) and under the "Bundles" tab, under the "Workspace"
node, we noticed a number of bundles showing with green check marks
indicting they were to be started when the thing ran. The bundles in
question correspond to several projects that my colleague had open in his
Package Explorer. We deselected these, and ran, and life got good again.
My question is: why did these irrelevant projects intrude into my
colleague's copy of the launch configuration. He had other projects open
that did not so intrude.
Why are these extra projects being picked up?
Is this the way things should be?
I would like to use the launch configuration file as the basis for an
automated build/deploy of an OSGi container but this little issue has me
Powered by FUDForum
. Page generated in 0.01906 seconds