Jira Subversion plugin-in fork won't enable

[Michael]

I installed the forked version of the Jira Subversion plugin and I get the following message when an attempt is made to enable it:

"The add-on has been installed but cannot be enabled. Please refer to the logs for more information."

There is no information in the logs because it hasn't setup a logger correctly:

log4j:WARN No appenders could be found for logger (com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Any guesses about why it wouldn't be able to be enabled?

[Kinto Soft]

I'm curious: can the new version be enabled?

[Michael]

Ok, I have added myself as a watcher. I will try the new version when you release it. Thanks.

[Kinto Soft]

That is not too much useful, right...

Anyway, I'm going to publish a major version within very few hours. It will include very important changes/enhancements. So, I would recommend to add yourself as watcher from the plug-in page in order to be notified when the new relase is available... and read the new features to see whether the new version match your needs or not.

[Michael]

I tried to enable it again, I just get a countdown where it looks like Jira gives a plugin 60 seconds to enabled itself. After that I just get a message in the logs indicating it isn't enabled because it didn't meet the timeout:

2013-06-13 10:28:53,453 http-bio-8080-exec-89 INFO 627x68120x1 1wxjqhn 10.6.19.133,10.27.193.51 /rest/plugins/1.0/pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin-key [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin], 0 seconds remaining

2013-06-13 10:28:54,455 http-bio-8080-exec-89 INFO 627x68120x1 1wxjqhn 10.6.19.133,10.27.193.51 /rest/plugins/1.0/pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin-key [atlassian.plugin.manager.DefaultPluginManager] Disabling pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin

2013-06-13 10:29:04,462 http-bio-8080-exec-89 ERROR 627x68120x1 1wxjqhn 10.6.19.133,10.27.193.51 /rest/plugins/1.0/pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin-key [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

2013-06-13 10:29:04,568 http-bio-8080-exec-89 ERROR 627x68120x1 1wxjqhn 10.6.19.133,10.27.193.51 /rest/plugins/1.0/pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin-key [atlassian.plugin.manager.PluginEnabler] Unable to start the following plugins due to timeout while waiting for plugin to enable: pbeltranl.subversion.jira.pbeltranl-jira-subversion-plugin

[Kinto Soft]

Try to enable it again by clicking on the button and look at the logs again. Such kind of error is logged by the Atlassian UPM and not by the plug-in. You should see something useful in the logs.