-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically load a subset of world plugins #281
Conversation
9acc99e
to
00c5419
Compare
00c5419
to
ca51a90
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me!
Can you fix conflicts?
Also, since this changes a lot the way ign-gazebo
is used and adds functionality that's difficult to discover, what do you think of writing a tutorial?
Just checking @mjcarroll, I remember we already discussed the use case in #537. Would exporting an empty |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the DefaultPlugins
be removed from the DefaultWorld
now that they will come from the config file?
6dd9275
to
77d102d
Compare
@diegoferigo: Empty may currently be an issue, due to an upstream To work around this in the short-term, exporting any content that doesn't point to a valid file should be sufficient to trigger this behavior. There are tests in |
Done.
Will do. |
I'm removing this from the Dome beta release. We're already in feature freeze and code freeze is in 2 days. This is a backwards-compatible feature that can be merged into Citadel then merged forward to Dome after the release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Compilation was failing, fixed in d2a18d1
How do you feel about removing the plugins from all example worlds that are using the default ones in this PR?
I'll work on a tutorial.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the DefaultPlugins be removed from the DefaultWorld now that they will come from the config file?
Yeah that's necessary so that server.config
is picked up when no SDF file is loaded. Addressed in #405 , which also has a tutorial.
a4fa69b
to
5727e16
Compare
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
* joinPaths rather than string concatenation * (env, setenv, unsetenv) where possible Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Louise Poubel <[email protected]> Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
This reverts commit fe4eda9. Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
7d2d9da
to
8e40b07
Compare
I noticed that scenebroadcaster test seems to be failing over here as well: #531, so I don't think it's related to my changes? |
Holding this until 3->4 forward ports are done |
Feature to allow loading of a default set of system plugins from a file. This behavior will trigger when a world sdf file is loaded with no plugins defined. In this case, the simulator will load the plugins from a series of locations including environment variable, the users home folder, and finally in the installation directory. This should allow users to not have to specify the same set of plugins in every world sdf file. Signed-off-by: Michael Carroll <[email protected]> Co-authored-by: Louise Poubel <[email protected]>
Feature to allow loading of a default set of system plugins from a file. This behavior will trigger when a world sdf file is loaded with no plugins defined. In this case, the simulator will load the plugins from a series of locations including environment variable, the users home folder, and finally in the installation directory. This should allow users to not have to specify the same set of plugins in every world sdf file. Signed-off-by: Michael Carroll <[email protected]> Co-authored-by: Louise Poubel <[email protected]>
* Automatically load a subset of world plugins (#281) Feature to allow loading of a default set of system plugins from a file. This behavior will trigger when a world sdf file is loaded with no plugins defined. In this case, the simulator will load the plugins from a series of locations including environment variable, the users home folder, and finally in the installation directory. This should allow users to not have to specify the same set of plugins in every world sdf file. Signed-off-by: Michael Carroll <[email protected]> Co-authored-by: Louise Poubel <[email protected]> * Added missing version namespace (#541) * Added missing version namespace Signed-off-by: Nate Koenig <[email protected]> * Fix codecheck Signed-off-by: Nate Koenig <[email protected]> Co-authored-by: Nate Koenig <[email protected]> * Fix examples in migration plugins tutorial (#543) Signed-off-by: Nick Lamprianidis <[email protected]> * Prepare for 3.7.0 release (#552) Signed-off-by: Nate Koenig <[email protected]> Co-authored-by: Nate Koenig <[email protected]> Co-authored-by: Michael Carroll <[email protected]> Co-authored-by: Louise Poubel <[email protected]> Co-authored-by: Nate Koenig <[email protected]> Co-authored-by: Nick Lamprianidis <[email protected]>
Addresses #57