Thus, it is not ensured that a plugin is maintained for a long time. The experience we have in JabRef is that people are working for JabRef and its plugins during their PhD and then move on to new things. Having the code integrated in JabRef ensures that we do not rely on maintenance of third parties. Thus, changing internal data structures does not break any plugin, because we ensure that everything works during in internal change. Moreover, having no plugin support assures that all functions in JabRef remains up to date with other JabRef code. We decided that reducing the amount of issues and having more (other) features in JabRef is more important. It was not, because plugins are bad per se, but increase our maintenance effort tremendously. Regarding the plugins, we decided to drop support for it in the version 3.0. They are also not enough to pay someone to do work we don't like to. They are also far from being enough to do so. There is no funding agency and the donations are not used for covering our living costs. They could finish their PhD or PostDoc phase, but they invest time in JabRef, because they just like to. The JabRef team just consists of volunteers spending their free time for JabRef. Java.io.IOException: Server returned HTTP response code: 503 for URL: Īt net.sf.downloadToString(URLDownload.java:123) ~Īt net.sf.nConfig(GoogleScholarFetcher.java:166) ~Īt net.sf.GoogleScholarFetcher.processQueryGetPreview(GoogleScholarFetcher.java:82) ~Īt net.sf.GeneralFetcher.lambda$actionPerformed$4(GeneralFetcher.java:191) ~Īt .runWorker(ThreadPoolExecutor.java:1142) Īt $n(ThreadPoolExecutor.java:617) Īt (Thread.java:745) Ġ1:30:53.124 WARN net.sf.GoogleScholarFetcher - Error fetching from Google ScholarĪt (Thread.java:745) I think, you often heard it in the context of open source projects, but I'll try to rephrase it for the context of JabRef.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |