Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Oliver Kopp
    @koppor

    Hey everyone wanting to be an active member of the Google Summer of Code happening. Maybe you know that an organization has a limited number of slots available. Let us outline what makes an outstanding proposal from our side:

    • submitted 4 weeks before the deadline. This allows us to provide feedback, which can be incorpated.
    • 5 pull requests to JabRef code before submitting a propsal. On the one hand, this enables the applicants to get into the code before the start (and thus an estimation of the diffiultiy). On the other hand, this shows us true interest in our project.

    For sure, this is impossible when seeing actual workload of possible mentees. However, it should be possible to submit an initial propsal two weeks before the deadline and hand in one serious pull request.

    We warmthly invite you to prepare for GSoC 2022 and take part in open source development this year.

    For more information see https://google.github.io/gsocguides/student/being-turned-down.

    Rakesh Swain
    @rakeswain
    Hello Everyone. I am trying to setup jabref locally but facing this issue java.lang.IllegalArgumentException: Unsupported class file major version 60 while doing gradlew assemble or gradlew clean. I see that its gradlew java compatibility issue but I have the correct java version installed (16.0.1) and jmods are in the right place. Any hints on how to get over this?
    Christoph
    @Siedlerchr
    HI, I encountered a simliar issue. The problem might be the gradle wrapper beeing to old. Just got to jabref/gradle/gradle.properties and change the distribution url to https\://services.gradle.org/distributions/gradle-7.0.2-bin.zip
    that should work then
    Rakesh Swain
    @rakeswain
    Thank you @Siedlerchr . My build is passing now.
    Ali
    @Ali96kz

    Hello, can't resolve these issue, could somebody help me?

    Execution failed for task ':startScripts'.
    > Could not resolve all files for configuration ':runtimeClasspath'.
       > Could not find javafx-base-16-linux.jar (org.openjfx:javafx-base:16).
         Searched in the following locations:
             file:/Users/ali_zhagparov/.m2/repository/org/openjfx/javafx-base/16/javafx-base-16-linux.jar

    There is only javafx-base-16-mac.jar

    Carl Christian Snethlage
    @calixtus
    This error looks like you may hove not setup up jdk and/or javafx properly. Please try again setting up your working environment according to our guide here - maybe also again from scratch. Please also check if your environment variables are set up right. Maybe try to call javac -version from bash to see, if you have the right jdk configured.
    1 reply
    Oliver Kopp
    @koppor
    @Ali After which task is startScrips executed? I am not fully aware about that task. Did you run gradlew assemble?
    1 reply
    Jonatan Asketorp
    @k3KAW8Pnf7mkmdSMPHz27

    Is anyone else getting,

    Jun 28, 2021 12:45:02 PM javafx.scene.CssStyleHelper calculateValue
    WARNING: Caught 'java.lang.ClassCastException: class java.lang.String cannot be cast to class javafx.scene.paint.Paint (java.lang.String is in module java.base of loader 'bootstrap'; javafx.scene.paint.Paint is in module javafx.graphics of loader 'app')' while converting value for '-fx-background-color' from rule '*#preferencesContainer *.tab-pane>*.tab-header-area>*.tab-header-background' in stylesheet file:/Users/JAsketorp/Documents/RandomJava/jabref/build/resources/main/org/jabref/gui/Dark.css

    With darkmode?

    Christoph
    @Siedlerchr
    Yep, I think I had this before
    Timucin Merdin
    @tmrd993
    This exception gets thrown on the latest commit (Win 10):
    ERROR org.jabref.gui.JabRefMain - Could not access app-directory at C:\Users\Timucin\AppData\Local\org.jabref\JabRef
    java.nio.file.NoSuchFileException: C:\Users\Timucin\AppData\Local\org.jabref\JabRef
    Is this file supposed to exist?
    Also, when trying to add a new library, this exception gets thrown: java.util.NoSuchElementException: No value present
    at java.base/java.util.Optional.get(Optional.java:143)
    at org.jabref/org.jabref.model.database.BibDatabaseContext.getFulltextIndexPath(BibDatabaseContext.java:223)
    This is caused by getFulltextIndexPath() in the BibDatabaseContext class
        public Path getFulltextIndexPath() {
            Path appData = getFulltextIndexBasePath();
            LOGGER.info("Index path for {} is {}", getDatabasePath().get(), appData.toString());
            if (getDatabasePath().isPresent()) {
                return appData.resolve(String.valueOf(this.getDatabasePath().get().hashCode()));
            }
            return appData.resolve("unsaved");
        }
    Commenting out the logger info fixes it
    Christoph
    @Siedlerchr
    Ah thanks for the info, it's related to the new pdf search feature. Can you please open a new PR?
    I guess the logger needs to be moved before the return
    Timucin Merdin
    @tmrd993
    Sure, I'll do it tommorow. Should I also open a new issue for it?
    Christoph
    @Siedlerchr
    Seems like someone found the same error JabRef/jabref#7934
    bfrodsham
    @bfrodsham
    Hello! I'm a new contributor and I'm looking for some help getting the local workspace set up. I'm using the guide. I'm at this part of the guide: "After that, you can use the Gradle Tool Window to build all parts JabRef and run it. To do so, expand the JabRef project in the Gradle Tool Window and navigate to Tasks. From there, you can
    Build and run JabRef by double-clicking JabRef | Tasks | application | run." However, I'm unable to expand the JabRef project as it says. Any ideas what I might've done wrong? I'll attach an image as well.
    1 reply
    bfrodsham
    @bfrodsham
    Any help is appreciated, thanks.
    Carl Christian Snethlage
    @calixtus
    Looks like an issue gradle recently had with java.
    Please make sure you have the latest JDK16 and JavaFX16 installed. Then make sure your local main branch is up to date (git fetch --all, then git checkout main, then git merge upstream/main)
    (You can't see the gradle tasks because gradle fails to build it' s buildscript)
    Christoph
    @Siedlerchr
    @MarcelPa Sorry, I think I accidently reported your post. Can you please open an issue at our github tracker?
    Marcel P
    @MarcelPa

    @MarcelPa Sorry, I think I accidently reported your post. Can you please open an issue at our github tracker?

    Sure, will do :-)

    Houssem Nasri
    @HoussemNasri
    Hi, is it normal behavior that we can define custom field names
    Christoph
    @Siedlerchr
    Yes, that's totally valid!
    4 replies
    And also complete new entry types
    ketchupninja
    @ketchupninja

    Hi, I'm having trouble using gradle to build Jabref locally. I'm on Windows 10, using a local installation of Gradle 7.2, using JDK 16.0.2, and 64-bit JRE 1.8.

    The "gradlew assemble" command results in the build failing the task "':generateBstGrammarSource'" due to the reason 'Process 'command 'C:\jdk-16.0.2\bin\java.exe'' finished with non-zero exit value 1'.

    Running with the -debug flag reveals the more specific issue "error(1): cannot write file : java.io.FileNotFoundException: src-gen\main\java\org\jabref\logic\bst\C:\BstParser.java (The filename, directory name, or volume label syntax is incorrect)"

    Just looking in src-gen via the file explorer confirms it's a bunch of empty folders.

    I'm not sure why the C: drive is showing up in a path like that. It may be related to the fact that my JDK installation/JAVA_HOME environment variable are set to C:/jdk-16.0.2 ?

    Carl Christian Snethlage
    @calixtus
    Hi @ketchupninja, thanks for you question. Im slightly confused why you are using jdk 16 with jre 1.8? Have you tried uninstalling all older versions of JRE? Did you use LibericaJDK 16?
    ketchupninja
    @ketchupninja
    Ah, I was confused about the distinction between JRE and JDK. I've removed the unnecessary JRE and other old versions of Java. I was following the local workspace guide and using OpenJDK 16.02. The problem persists, but I'll try using LibericaJDK16.
    ketchupninja
    @ketchupninja
    Switching my JDK installation to Liberica hasn't affected anything. generateBstGrammarSource still fails to find "src-gen\main\java\org\jabref\logic\bst\C:\BstParser.java".
    2 replies
    Brittany
    @jiezheng5
    Hi,
    I am using Ubuntn 20.04 and IntelliJ, and I closely followed every step of contributing guide at https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace. I can build and run perfectly fine with gradlew but it was a pain to get working with IntelliJ. Even though I already enabled auto imports in IntelliJ following distributing guide, I still got lots of read lines in IntelliJ indicating missing dependency, and the error message is "java: package org.jabref.logic.importer.fileformat.bibtexml does not exist". I searched online, and I already tried restart cache, delete .idea folder then re-import, move the folder, none worked.
    thanks very much for your time.
    image.png
    Christoph
    @Siedlerchr
    @ketchupninja Can you try to isntall the jdk in the default location? And in which folder is your JabRef workspace located?
    5 replies
    Carl Christian Snethlage
    @calixtus
    @jiezheng5 yes, i can totally relate to that. Thats why i'm always compiling with gradlew run because of these problems. But @koppor prefers using intellij to build an run since it's compiles somewhat quicker. Anyway, there seems to be something wrong with the project folder structure. Could you show us what "File->Project Structure->Modules shows?" displays on the right hand side below "+ Add content root"?
    10 replies
    Benedikt Tutzer
    @btut

    Hi @jiezheng5

    I still got lots of read lines in IntelliJ indicating missing dependency, and the error message is "java: package org.jabref.logic.importer.fileformat.bibtexml does not exist".

    When you get the red lines, does Idea still build and run fine? I have that some times (red lines but still building and running). Invalidating caches (File -> Invalidate Caches, but from what I understand you already tried that) helps. I usually do a gradlew clean and then invalidate the caches.

    5 replies
    Brittany
    @jiezheng5
    image.png
    ketchupninja
    @ketchupninja
    In the local workspace setup guide, it instructs us to delete Log4jPlugins. I wanted to clarify a couple points about this.
    1. Is this only necessary if we want to make use of IntelliJ's internal build system, and it is not necessary otherwise?
    2. Deleting this file generates warnings because this file is referenced other places in the code base. Should these warnings simply be ignored?
    1 reply
    Brittany
    @jiezheng5
    2021-11-13_05-09.png

    Error: Could not find or load main class org.jabref.gui.JabRefMain
    Caused by: java.lang.ClassNotFoundException: org.jabref.gui.JabRefMain

    I can never get jabref to run in IntelliJ and I am using Ubuntn 20.04. I can always run with gradle.
    I also noticed that the generated folder under src-gen is always empty after running gradle assemble and gradle run. I have tried multiple times and all possible sequences of the following steps:

    File -> Invalidate Cache...
    File -> Open -> build.gradle -> open as project,
    gradle clean
    gradle assemble
    gradle run

    then run JabRef Main in IntelliJ, always got the same error:
    Error: Could not find or load main class org.jabref.gui.JabRefMain
    Caused by: java.lang.ClassNotFoundException: org.jabref.gui.JabRefMain

    any suggestions are greatly appreciated,

    7 replies
    Jonatan Asketorp
    @k3KAW8Pnf7mkmdSMPHz27
    Skärmavbild 2021-11-13 kl. 10.07.34.png
    Brittany
    @jiezheng5
    2021-11-13_16-06.png
    Brittany
    @jiezheng5
    2021-11-13_05-09.png
    3 replies
    Oliver Kopp
    @koppor
    Did you know that IntelliJ supports running test cases separately? And that also debug run is possible?
    grafik.png
    Navigate to the test class by pressing Ctrl+Shift+T. At each @Test method, you can click on the green play button