Christopher,
thank you - this fixes the problem in both cases for me!
Morten
On 19/11/2007, Christopher Oezbek <[EMAIL PROTECTED]> wrote:
> Yes, this is definitely a problem with the current code (good that this is
> not in JabRef 2.2 :-).
>
> The problem must be in
>
> net.sf.jabref.plugin.PluginCore.initialize()
>
> I applied the following fix:
>
> try {
> File parent = new File(PluginCore.class.getProtectionDomain()
> .getCodeSource().getLocation().toURI()).getParentFile();
>
> if (!parent.getCanonicalFile().equals(
> new File(".").getCanonicalFile())) {
> directoriesToSearch.add(new File(parent, "/src/plugins"));
> directoriesToSearch.add(new File(parent, "/plugins"));
> }
> } catch (Exception e) {
> // no problem, we just use paths relative to current dir.
> }
>
> So this should also now look for the plugin and src/plugins folder beside
> the jar.
>
> Cheers,
> Christopher
>
> On Mon, 19 Nov 2007 12:30:02 +0100, Morten Omholt Alver
> <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > plugins should get loaded when placed in the plugins directory below
> > the JabRef jar. However, running under Linux I find that this works
> > only if I run the "java -jar JabRef.jar" command from that directory.
> > If I run it from elsewhere, e.g. with "java -jar
> > jabref/build/lib/JabRef.jar", the plugins don't get detected. If I run
> > JabRef by double-clicking the jar file in Nautilus (Gnome file
> > manager), the plugins also don't get detected.
> >
> > This may not be such a great problem, but I'd say that it doesn't work
> > as expected. Am I doing something wrong?
> >
> >
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Jabref-devel mailing list
Jabref-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jabref-devel
