Errbot: How can I import one plugin from another - errbot

In this case I have a simple JIRA plugin, I'd like to create another plugin that also interacts with JIRA via the first plugin. I have been trying variations of errbot.plugin_manager.get_plugin_obj_by_name('jira') but I haven't found the right way to do this.

You are in luck, it just got implemented in the 4.3.0 version released yesterday:
Basically you need to declare the dependency in the .plug with DependsOn in the [Core] section then you can get the plugin object you depend on with self.get_plugin('pluginName').
https://github.com/errbotio/errbot/blob/master/docs/user_guide/plugin_development/dependencies.rst

Related

How to upgrade Sceneform's source code to androidx?

I am using androidStudio-4.1 version and there the sceneform plugin is deprecated. So I included a module from GitHub https://github.com/google-ar/sceneform-android-sdk and use the same steps as suggested on Github but getting an error at "import android.support.annotation.Nullable;" and another related import issue.
I understood that I need to upgrade Sceneform's source code to androidx but I do not know how to do this.
Please suggest me.
There is a fork of Sceneform which is currently being kept up to date and which already has this update to AndroidX included and tested:
https://github.com/thomasgorisse/sceneform-android-sdk
It might be useful to consider using this as you may get better support and a wider community of people to share information with if you do.
See also the thread which refers to this fork and some recent experience using Sceneform after the official depreciation of the origin library: https://github.com/google-ar/arcore-android-sdk/issues/1049
replace line "import android.support.annotation.Nullable;" with "import androidx.annotation.Nullable;" through-out folder files ('sceneformsrc', 'sceneformux').
Make sure that you only implement one sceneform inside build.gradle file.
Goto build --> Rebuild Project, the problem will be resolved

ApiMember in java client does not include Format

When I use the Eclipse plugin to generate a client it includes ApiMember as seen below. Problem is that the ApiMember in 'net.servicestack: client' does not include 'Format'. Is there an option I have overlooked or is this a bug?
#ApiMember(DataType="number", Format="decimal", Name="ActionDefCost")
I ended up resolving this be removing the Format property and relying on the OpenApi plugin to generate the correct property for me. If I ever find a need to specify Format explicitly then maybe I will have propose adding it to ApiMember in the Java client.
I just saw this, apologies. I've added the new missing properties to ServiceStack Java libraries in this commit.
This change is available from the latest v1.0.35 release of net.servicestack:android and net.servicestack:client packages.

CodeNarc Maven Plugin

We have a project that uses Groovy extensively and we use Maven to build our artifacts. (IntelliJ as our IDE)
We wanted to incorporate some automated code-style checking, and thought we might use codecarc-maven-plugin. However, since that was from Codehaus, which gone now, is the plugin actively supported somewhere else?
Any other good options to run a Groovy style checker automatically during a Maven build?
That's a good catch. I'll add a pull request to update the website link. You can find the new plugin information on GitHub: https://github.com/gleclaire/codenarc-maven-plugin

Moodle Atto 'plugin not found'

I've been trying to use the Atto plugin template (https://github.com/justinhunt/moodle-atto_newtemplate) to try and create my own Atto plugin. I've made the changes outlined in the README, and got shifter to run via npm. It appears to generate the build folder that matches the other plugins.
I'm able to see the plugin in configuration, and it's showing up in the Atto Toolbar Settings, but, when I pop open a text editor, I don't get an icon, and the console logs moodle-editor_atto-editor: Plugin 'testplugin' could not be found - skipping initialisation
I've found a few references in the docs that shifter is no longer used, and grunt is the new way to go, but I can't find any actual docs on this, and no gruntfile seems to exist anywhere.
Has anyone come across this before? What am I missing?
You will need to run shifter on your YUI code for it to work - the usual way of doing that, for Moodle 2.9 and above is to use grunt - see https://docs.moodle.org/dev/Grunt for more details.
Not sure if this was ever resolved. The template is really helpful and it also comes with lib, db, and version PHP scripts. The string that you use as the plugin name has to be consistent throughout these scripts, as well as in your JS file. By default, it is set to atto_NEWTEMPLATE. Did you perhaps change this string to atto_testplugin in one place but not in all the others?

How can I enable Groovy plugin features in my eclipse plugin?

I am writing an eclipse plugin which needs to support features from the Groovy eclipse plugin.
The Groovy website talks about Groovy eclipse plugins, and Groovy compiler support within eclipse and maven, but I did not find anything similar to what I need to do here.
If I look at the list of available plugin dependencies, I see a number of them:
How can I enable some discovery mechanism or otherwise, in order to install the Groovy plugin after the installation of my plugin completes?
Which plugin can I add as dependency to achieve this? Or should I have to individually add all of them?
If you want to add single plug-ins you can easily do that in the Manifest-Editor of your plug-in. If you need to add a dependency to a feature, you need to create a feature for your own plug-in and add the additional feature dependency in the feature-Editor.
To find out which groovy plug-ins are required to add the "groovy compiler support", I suppose you must rather look at the groovy features in your installation. Usually complex features like a compiler or the like are grouped within a feature.
Add on:
I think the discovery mechanism is already integrated in p2.
I suppose these plug-ins are part of a feature. Find this feature and add that to your product.
For stability I would recommend to add the specific plug-ins to your product/feature. That way you can be sure, people are using the exact version you proposed in your implmentation.

Resources