Issue #386 duplicate

Adding own plug-in to classpath.xml prevents the plug-in system for adding/removing other plug-ins

Jan Börner
created an issue

I developed an own plug-in and installed it manually, that means I copied the jar file to the plugins directory and referenced it in the classpath.xml file. Since that I can't install or remove any other plug-in via the web applications plugin page. Analyzing the log file, it looks like the plug-in system tries to lookup for my own plug-in in a public maven repository.

====== Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Could not find artifact de.triology.scm.plugins .bugzilla:scm-bugzilla-plugin:jar:1.0.0-SNAPSHOT in central (http://repo1.maven.org/maven2/) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:37 5) at sonia.scm.plugin.AetherPluginHandler.collectDependencies(AetherPluginHandler.java:274) ... 106 more ======

So I expected that not official, self-written plug-ins do not affect the managing of official plug-ins in the web application.

Comments (2)

  1. Sebastian Sdorra repo owner

    A plugin should never installed manually. If you want to install a custom plugin, you have to create a package with the scmp:package maven goal. The package can be installed with the "Install Package" on the plugin tab. However the problem is related to issue #395, so i will mark this issue as duplicate of issue #395.

  2. Log in to comment