You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge remote-tracking branch 'upstream/main' into oo-architecture
* upstream/main:
Fix NPE when saving preferences (JabRef#11509)
Switch to stream-based loading (JabRef#11479)
Save unlinked local files dialog prefs (JabRef#11493)
Add minimal support for biblatex data annotations (JabRef#11506)
Fix handling of relative-file storage and auto linking (JabRef#11492)
New Crowdin updates (JabRef#11504)
Add missing issue numbers
CSL4LibreOffice - A [GSoC '24] (JabRef#11477)
Bump src/main/resources/csl-styles from `b2be5ae` to `fd6cb3e` (JabRef#11501)
Bump gittools/actions from 1.1.1 to 1.2.0 (JabRef#11500)
Bump com.kohlschutter.junixsocket:junixsocket-core from 2.9.1 to 2.10.0 (JabRef#11498)
Bump commons-logging:commons-logging from 1.3.2 to 1.3.3 (JabRef#11499)
Bump org.jsoup:jsoup from 1.17.2 to 1.18.1 (JabRef#11497)
Bump com.kohlschutter.junixsocket:junixsocket-mysql from 2.9.1 to 2.10.0 (JabRef#11496)
Bump org.openrewrite.recipe:rewrite-recipe-bom from 2.14.0 to 2.15.0 (JabRef#11495)
FAQ updates (JabRef#11486)
Update Gradle Wrapper from 8.8 to 8.9.
Fix Chocolate.bib (JabRef#11491)
# Conflicts:
# src/main/java/org/jabref/gui/openoffice/OOBibBase.java
# src/main/java/org/jabref/gui/openoffice/OpenOfficePanel.java
# src/main/java/org/jabref/gui/openoffice/StyleSelectDialogView.java
# src/main/java/org/jabref/gui/openoffice/StyleSelectDialogViewModel.java
# src/main/java/org/jabref/preferences/JabRefPreferences.java
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,18 @@ Note that this project **does not** adhere to [Semantic Versioning](https://semv
12
12
### Added
13
13
14
14
- We added support for selecting and using CSL Styles in JabRef's OpenOffice/LibreOffice integration for inserting bibliographic and in-text citations into a document.
15
+
- We added support for selecting and using CSL Styles in JabRef's OpenOffice/LibreOffice integration for inserting bibliographic and in-text citations into a document. [#2146](https://github.com/JabRef/jabref/issues/2146), [#8893](https://github.com/JabRef/jabref/issues/8893)
16
+
- Added minimal support for [biblatex data annotation](https://mirrors.ctan.org/macros/latex/contrib/biblatex/doc/biblatex.pdf#subsection.3.7) fields in .layout files. [#11505](https://github.com/JabRef/jabref/issues/11505)
17
+
- Added saving of selected options in the [Lookup -> Search for unlinked local files dialog](https://docs.jabref.org/collect/findunlinkedfiles#link-the-pdfs-to-your-bib-library). [#11439](https://github.com/JabRef/jabref/issues/11439)
15
18
16
19
### Changed
17
20
21
+
- JabRef respects the [configuration for storing files relative to the .bib file](https://docs.jabref.org/finding-sorting-and-cleaning-entries/filelinks#directories-for-files) in more cases. [#11492](https://github.com/JabRef/jabref/pull/11492)
22
+
18
23
### Fixed
19
24
25
+
- We fixed an issue where an exception was thrown after changing "show preview as a tab" in the preferences. [#11509](https://github.com/JabRef/jabref/pull/11509)
* <spanstyle="color:green">Fix</span> : Check if you've used ```System.out.println(...)``` (the standard output stream) to log anything into the console. This is an architectural violation, as you should use the Logger instead for logging. More details on how to log can be found [here](https://devdocs.jabref.org/code-howtos/logging.html).
10
+
*Failing <b>Checkstyle</b> tests:
11
+
* <spanstyle="color:green">Fix</span>: JabRef follows a pre-defined style of code for uniformity and maintainability that must be adhered to during development. To set up warnings and auto-fixes conforming to these style rules in your IDE, follow [Step 3](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/intellij-13-code-style.html) of the process to set up a local workspace in the documentation. Ideally, follow all the [set up rules](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/) in the documentation end-to-end to avoid typical set-up errors.<br> <b>Note</b>: The steps provided in the documentation are for IntelliJ, which is the preferred IDE for Java development. The `checkstyle.xml` is also available for VSCode, in the same directory as mentioned in the steps.
* <spanstyle="color:green">Fix</span> : One common case when this test fails is when you put any class purely containing business logic at some level inside the ```model``` directory (```org/jabref/model/```). To fix this, shift the class to a subdirectory within the ```logic``` directory (```org/jabref/logic/```).
13
+
* Failing <b>OpenRewrite</b> tests:
14
+
* <spanstyle="color:green">Fix</span>: [OpenRewrite](https://docs.openrewrite.org/) is an automated refactoring ecosystem for source code. Execute the Gradle task `rewriteRun` from the `rewrite` group of the Gradle Tool window in IntelliJ to apply the automated refactoring and pass the test.<br>
* <spanstyle="color:green">Fix</span>: You have probably used Strings that are visible on the UI (to the user) but not wrapped them using ```Localization.lang(...)``` and added them to the [localization properties file](https://github.com/JabRef/jabref/blob/main/src/main/resources/l10n/JabRef_en.properties).
18
+
* <spanstyle="color:green">Fix</span>: You have probably used Strings that are visible on the UI (to the user) but not wrapped them using `Localization.lang(...)` and added them to the [localization properties file](https://github.com/JabRef/jabref/blob/main/src/main/resources/l10n/JabRef_en.properties).
18
19
Read more about the background and format of localization in JabRef [here](https://devdocs.jabref.org/code-howtos/localization.html).
* <spanstyle="color:green">Fix</span>: There are localization keys [localization properties file](https://github.com/JabRef/jabref/blob/main/src/main/resources/l10n/JabRef_en.properties) that are not used in the code, probably due to the removal of existing code. Navigate to the unused key-value pairs in the file and remove them. You can always click on the details of the failing test to pinpoint which keys are unused.
23
+
Read more about the background and format of localization in JabRef [here](https://devdocs.jabref.org/code-howtos/localization.html).
24
+
25
+
*`org.jabref.logic.citationstyle.CitationStyle``discoverCitationStyles` <spanstyle="color:red">ERROR: Could not find any citation style. Tried with /ieee.csl.</span>
26
+
* <spanstyle="color:green">Fix</span>: Check the directory `src/main/resources/csl-styles`. If it is missing or empty, run `git submodule update`. Now, check inside if `ieee.csl` exists. If it does not, run `git reset --hard` <b>inside that directory</b>.
27
+
28
+
*`java.lang.IllegalArgumentException`: Unable to load locale en-US<br> <spanstyle="color:red">ERROR: Could not generate BibEntry citation. The CSL engine could not create a preview for your item.</span>
29
+
* <spanstyle="color:green">Fix</span>: Check the directory `src/main/resources/csl-locales`. If it is missing or empty, run `git submodule update`. If still not fixed, run `git reset --hard` <b>inside that directory</b>.
* <spanstyle="color:green">Fix</span>: Check if you've used `System.out.println(...)` (the standard output stream) to log anything into the console. This is an architectural violation, as you should use the Logger instead for logging. More details on how to log can be found [here](https://devdocs.jabref.org/code-howtos/logging.html).
* <spanstyle="color:green">Fix</span>: One common case when this test fails is when you put any class purely containing business logic inside the `model` package (i.e., inside the directory `org/jabref/model/`). To fix this, shift the class to a sub-package within the `logic` package (i.e., the directory`org/jabref/logic/`). An efficient way to do this is to use IntelliJ's built-in refactoring capabilities - right-click on the file, go to "Refactor" and use "Move Class". The import statement for all the classes using this class will be automatically adjusted according to the new location.<br>
36
+
<br>
37
+
38
+
*`ANTLR Tool version 4.12.0 used for code generation does not match the current runtime version 4.13.1`
39
+
* <spanstyle="color:green">Fix</span>: Execute the Gradle task `clean` from the `build` group of the Gradle Tool Window in IntelliJ:<br>
0 commit comments