New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate all maintained plugins into JabRef #152

Closed
koppor opened this Issue Sep 9, 2015 · 9 comments

Comments

Projects
None yet
8 participants
@koppor
Member

koppor commented Sep 9, 2015

The plugin system of JabRef used the Java Plug-in Framework, which is not state of the art anymore. The modern way is to use Jigsaw. However, offering a plugin interface requires the interfaces to be stable. This cannot be guaranteed. Issues such as korv/Jabref-plugins#13 or lehner/LocalCopy#6 will arise. We assume that plugin functionality directly integrated in the JabRef code will ensure that it will be maintained, we removed the plugin functionality.

We ask all plugin developers to fork JabRef, integrate the plugin functionality and create a pull request. Our CONTRIBUTING.md file provides details.

In the long run, all available plugins should be integrated in JabRef.

@jdpipe

This comment has been minimized.

Show comment
Hide comment
@jdpipe

jdpipe Jan 6, 2016

Hi there

Does this also affect jabref-ooplugin?
http://jabref.sourceforge.net/OOPlugin-jabref.php

I still use this regularly, and hope that it can continue to be supported.

Cheers
JP

jdpipe commented Jan 6, 2016

Hi there

Does this also affect jabref-ooplugin?
http://jabref.sourceforge.net/OOPlugin-jabref.php

I still use this regularly, and hope that it can continue to be supported.

Cheers
JP

@simonharrer

This comment has been minimized.

Show comment
Hide comment
@simonharrer

simonharrer Jan 7, 2016

Contributor

The OO plugin is still supported as it is integrated into JabRef directly. No need to worry. :)

Contributor

simonharrer commented Jan 7, 2016

The OO plugin is still supported as it is integrated into JabRef directly. No need to worry. :)

@oscargus

This comment has been minimized.

Show comment
Hide comment
@oscargus

oscargus Feb 4, 2016

Contributor

I just found this plugin: https://github.com/kwwette/pdftasks which seems quite useful as far as I can tell. It is rather recently updated and relies on the file-field rather than the pdf-field. Should we ask the author if he could integrate it?

Contributor

oscargus commented Feb 4, 2016

I just found this plugin: https://github.com/kwwette/pdftasks which seems quite useful as far as I can tell. It is rather recently updated and relies on the file-field rather than the pdf-field. Should we ask the author if he could integrate it?

@oscargus

This comment has been minimized.

Show comment
Hide comment
@oscargus

oscargus Feb 4, 2016

Contributor

Oh, now I saw kwwette/pdftasks#1 ... Still, the impression is that this plugin makes things a bit more intuitive compared to running a cleanup. Also, this could be used as a starting point to extract additional information from PDFs etc.

Contributor

oscargus commented Feb 4, 2016

Oh, now I saw kwwette/pdftasks#1 ... Still, the impression is that this plugin makes things a bit more intuitive compared to running a cleanup. Also, this could be used as a starting point to extract additional information from PDFs etc.

@dajare

This comment has been minimized.

Show comment
Hide comment
@dajare

dajare Feb 18, 2016

I'm new to JabRef, and a bit confused about how things are going in this transition phase (as it appears to be). I'm using JabRef 3.2, but wanting/needing to use some custom export filters. These exist as "plugins":

  • net.sf.jabref.export.Chicago(English)-1.2.jar
  • net.sf.jabref.export.Turabian(English)-1.2.jar

These are available from the old resources page. Is there a way to make use of these old plugins in 3.2?

(+ Apologies if this is the wrong place for this: I got here via a link in the mailing list.)

dajare commented Feb 18, 2016

I'm new to JabRef, and a bit confused about how things are going in this transition phase (as it appears to be). I'm using JabRef 3.2, but wanting/needing to use some custom export filters. These exist as "plugins":

  • net.sf.jabref.export.Chicago(English)-1.2.jar
  • net.sf.jabref.export.Turabian(English)-1.2.jar

These are available from the old resources page. Is there a way to make use of these old plugins in 3.2?

(+ Apologies if this is the wrong place for this: I got here via a link in the mailing list.)

@mlep

This comment has been minimized.

Show comment
Hide comment
@mlep

mlep Apr 21, 2016

Contributor

@koppor Could you update the checkbox, as the list of plugins is listed in the FAQ (http://www.jabref.org/faq/)?

Contributor

mlep commented Apr 21, 2016

@koppor Could you update the checkbox, as the list of plugins is listed in the FAQ (http://www.jabref.org/faq/)?

@tobiasdiez

This comment has been minimized.

Show comment
Hide comment
@tobiasdiez

tobiasdiez Sep 27, 2016

Member

I marked the ADS fetcher plugins as done since we now have search by query and search by id as fetcher, which was exactly the purpose of these ADS plugins.

Member

tobiasdiez commented Sep 27, 2016

I marked the ADS fetcher plugins as done since we now have search by query and search by id as fetcher, which was exactly the purpose of these ADS plugins.

@tobiasdiez

This comment has been minimized.

Show comment
Hide comment
@tobiasdiez
Member

tobiasdiez commented Oct 29, 2016

@koppor koppor referenced this issue Nov 18, 2016

Open

[WIP] Integrate BibSonomy Plugin #2157

1 of 6 tasks complete

@koppor koppor referenced this issue Jan 9, 2018

Open

Add arxiv-rss #279

@tobiasdiez

This comment has been minimized.

Show comment
Hide comment
@tobiasdiez

tobiasdiez Sep 8, 2018

Member

Since plugin support is now gone for three years and we have got no user inquires asking us to include the remaining plugins, I'll close this issue now. Pullrequests that include some of the functionality of the old plugins are of course still more than welcome.

Member

tobiasdiez commented Sep 8, 2018

Since plugin support is now gone for three years and we have got no user inquires asking us to include the remaining plugins, I'll close this issue now. Pullrequests that include some of the functionality of the old plugins are of course still more than welcome.

@tobiasdiez tobiasdiez closed this Sep 8, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment