I am trying to add a plugin named Redmine Scrumbler to Redmine. So far I have created a folder named "plugins" in the root folder where Redmine is installed and I've cloned the plugin from this repository Redmine Scrumbler to that folder.
Now this says that if the plugin requires migration I have to migrate it. Now how do I know if the plugin requires migration or not? Also what exactly does plugin migration mean in Redmine?
Also I didn't see "plugins" folder in the root folder where Redmine is installed. Does that folder need to be created or not? (The version of Redmine is 2.4.1)
Now how do I know if the plugin requires migration or not?
Check plugin folder plugin_root/db/migrate. If the folder exists and have some migrations (files) then plugin requires to run migration. Mentioned plugin requires migration (https://github.com/256MbTeam/Redmine-Scrumbler/tree/master/db/migrate)
Also what exactly does plugin migration mean in redmine?
The plugin will update the DB structure. Plugins usually create some additional tables/columns.
Also I didn't see "plugins" folder in the root folder where Redmine is installed. Does that folder need to be created or not? (The version of Redmine is 2.4.1)
Yes. The folder should be created.
PS mentioned plugin's last update time was two years ago. It looks like the plugin is not supported any more.
Redmine Scrumbler isn't officially supported on versions >2.x. You shouldn't trust it.
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 recently started a new web project and I decided to use Symfony2 as a framework, Eclipse as IDE and Subversive as plugin for version control.
My idea was to make the 'commit' of all modifications, ignoring yes, folder 'logs' and 'cache' of the web application.
My surprise came when I imported the first Symfony project to the repository, when I do the commit, the folder 'vendor' where they are stored dependencies framework is unaffected, ie it is not uploaded to the repository. If I make changes to this folder, Subversive also treats it as modified files stored in the repository.
It is probably because I have not worked much with a management system versioning and something is going wrong, but do not understand why the folder 'vendor', which is critical for Symfony, not imported, even without any configuration to ignore files when performing 'commit'.
Thank you all.
A greetings.
PS: Even without any configuration, installing the development environment, the plugin to version control and creating a Symfony
project from scratch, Subversive ignores the vendor folder.
The documentation of chapay is very good : http://symfony.com/doc/current/cookbook/workflow/new_project_svn.html#initial-project-setup
this line helps me, not on symfony but in another project with composer where I didn't wanted to commit the vendor folder, only the composer.json :
svn propset svn:ignore "vendor" .
I am trying to deploy a version of Eclipse and would like control over the default repository list. See my earlier question.
In my other question, I learned that this is stored in the user's home directory under ".eclipse\org.eclipse.platform_3.7.0_525061626\p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.cpp.profile\.data\.settings\org.eclipse.equinox.p2.metadata.repository.prefs".
I would rather not deploy this file to a user specific location because there might already be one from another Eclipse installation and there could be more than one user account.
Is there any way that I can avoid the user profile?
I did find an equivelent file under the main Eclipse folder "eclipse\p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.cpp.profile\.data\.settings\org.eclipse.equinox.p2.metadata.repository.prefs" but changing this didn't make any difference.
Thanks,
Alan
You can use p2 touchpoints and the p2 director to install your feature to customize the version of eclipse you are trying to deploy.
See p2.inf for an example of touchpoint configuration instructions that add p2 repositories to the default install. This one is part of an sdk.product generation. If you are starting with an eclipse that already has a product, your touchpoint instructions would have to remove the repositories that were already included and then add your own.
instructions.configure=\
addRepository(type:0,location:http${#58}//download.eclipse.org/eclipse/updates/3.8,name:The Eclipse Project Updates);\
addRepository(type:1,location:http${#58}//download.eclipse.org/eclipse/updates/3.8,name:The Eclipse Project Updates);\
addRepository(type:0,location:http${#58}//download.eclipse.org/releases/juno,name:Juno);\
addRepository(type:1,location:http${#58}//download.eclipse.org/releases/juno,name:Juno);
The way that I ended up doing this was to create a lightweight plugin that starts when Eclipse loads. This then programatically adds the update site as detailed here: https://stackoverflow.com/a/7384954/101642
I am using 1.3.7 on a windows system, the plugins are placed in a different folder and I have made a few changes in the code related to the plugins.
I now need to check in this project into svn, how do i go about doing it ? specifically how do i check in he plugins ?
When a team mate of mine checks out this project, where will he find the plugins ?
I realize that similar questions have been asked here and here
However they do not address this specific problem.
The plugins you have made need to be made inline. i.e. they will be in your grails-app folder.
To make a plugin inline create a folder say "custom-plugins" in your grails-app folder and copy the modified plugin there. Now in your BuildConfig.groovy add following lines
grails.plugin.location.'plugin-name'="custom-plugins/plugin-name"
repeat this for different plugins you have changed.
I personally prefer to add "custom" in the name of modified plugin to differentiate it from original.
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 .