In grails, you can install a zip version of a plugin with grails install-plugin myplugin.zip. This adds the file to your project and modifies application.properties. I tried putting the zip in /lib, but other developers are unable to build without first manually running grails install-plugin myplugin.zip.
Is there a way to get the zip file to resolve automatically?
Grails can load a plugin from anywhere. For example, if you add the following to BuildConfig.groovy
grails.plugin.location.jsecurity = "/home/dilbert/dev/plugins/grails-jsecurity"
It will load the jsecurity plugin from the location specified
In-place plugins work a treat for all plugins and updates your application realtime as you are testing. Peter Ledbrook has written a very good blog on this ( http://blog.springsource.org/2010/06/01/whats-a-plugin-oriented-architecture/ ), see the paragraph on 'in-place plugins'.
Related
When I go to Plugin Gallery and click on "install quicksubmit plugin", I get a message saying that The loaded plugin file does not contain a folder that matches the plugin name. Where do I save this folder?
I found an explanation on PKP Help that said:
Most plugins should come with a readme file of some sort, and should also list which versions of OJS they are compatible with. To install a plugin, you should simply need to copy the files to the correct plugins subdirectory in your OJS installation. For example, if the plugin you want to install is considered a 'generic' plugin, copy the plugin folder to plugins/generic/; if it is classed as an import plugin, it should go into plugins/importexport; and so on.
But where can I find this plugins/generic/ or plugins/importexport folders?
This error is usually when you trying to direct install latest plugin into previous version of ojs please follow bellow steps to easily install this plugin.
Download the exact released version for your ojs from
https://github.com/pkp/quickSubmit .
Example if you are running ojs 3.2.0 then download the relevant zip
upload this zip file and extract to your ojs/plugins/importexport directory
after extraction login to dashboard and check in tool->import/export plugin will be installed
I have an installed eclipse RPC application and I want to add a plugin to it which I just wrote. To acheive this I copied the new plugin into the plugin folder of my application and added the plugin to the list of plugins in the config.ini file found under \configuration\config.ini.
This works, but I don't like messing around with the config file. Is there a way to get new plugins working without adding them to the list or do I have to do this for every single plugin I create?
Have you tried to export is as a plugin and put the resulting jar files inside the dropins folder of your Eclipse RCP?
I am building some small Java application to run on Goole AppEngine.
It is not clear to how should I configure eclipse so I'll be able to compile my project but I won't deploy stuff that already exists in on the platform.
(I've tried to read about the subject - here for example - but stil. it is not clear to me).
For example:
The Jersey and the Junit jars - I want them to be uploaded with my code to the cloud in the deployment process.
The AppEngine jars -I need them only for my design time - to be able to write code that is using the platform classes, but I don't want to upload them in the deployment process as they will be available to me by the platform.
Please help to get it right.
I think you need to read a bit from here Google Plugin for Eclipse
And also get the plugin from there, in addition , add the Jersy and the Junit (check first that the API's are on the WillItPlayInJava list) to the build path of the project
WillItPlayInJava
I'm using gwt-maven-plugin, version 1.2 with GWT version 2.0.3. When I run it in hosted mode (Jetty) I can't get it to load my jetty-env.xml file.
Any clues about that?
With that GWT and Maven plugin versions the embedded jetty igonres thw file /WEB-INF/jetty-env.xml, but same information can be used in the file /WEB-INF/jetty-web.xml.
So, renaming the file from "jetty-env.xml" to "jetty-web.xml" solved the issue.
I downloaded the source code for the EMF based UML2 Plugin and changed a class in the org.eclipse.uml2.uml.edit project to remove special characters when returning string representations. Now when I export the projects and place the jar files either in the dropins directory or replace my current uml2 plugin jar files in plugins directory, The UML files are no longer recognized, in short my modified plugin does not install correctly (no error is thrown and I can see the files being picked up under Plugins->Target Platform) .
However, When I run the plugin as an eclipse application (from the workspace) I can see the changes I made being reflected in the new instance of eclipse.
What can I do to ensure that the plugin installs correctly?
Is there a documented procedure of how to build the uml2 plugin (or any comparable plugin) after modification?
Select the project and open the context menu. There is an entry PDE near the bottom of the menu. In there, you can find an entry to build the plugin for deployment. This gives you the features and plugins directory with the fixed files. Copy both into your Eclipse install.
Unless the UML2 plugins require some kind of magic build script, exporting the one plugin you changed and overwriting the original in your Eclipse installation should be the easiest solution. One potential problem which comes to mind is conflicting plugin version numbers: make sure you don't have two identical versions of your modified plugin in your Eclipse installation.
When debugging plugins which apparently don't work properly at runtime, I always look at Help > About Eclipse Platform > Configuration Details. This lists all the plugins found by Equinox during startup, along with their status (see the Javadoc of the org.osgi.framework.Bundle interface for explanation).
I faced the exact same problem as you describe here . I dont have any answer to your problem but i am sharing what worked for me .
I created a local update site of the plugin on my system. Create update site for your plug-in article explains very very nicely the steps needed to accomplish this .