Summary: | app-text/jabref-2.9.2 - broken symbolic link /usr/share/jabref/api | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonas Stein <jstein> |
Component: | Current packages | Assignee: | Nicolas Bock <nicolasbock> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | java, sci |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jonas Stein
2014-01-04 22:18:17 UTC
The ant build system for 2.9.2 doesn't produce API documentation and I can't get an answer from upstream as to why (I'll keep pushing them, but don't know how long a resolution will take). The beta version, jabref-2.10_beta2 produces documentation. I have been running it for a while now and it seems just as stable as 2.9.2. Would you mind giving the beta a try? If the beta is missing any features you need, please open a new bug and I will add it to the ebuild. Jonas, I will close this bug in a week or two. Have you had a chance to try out the beta? The beta works fine here. I get just a warning on console during startup: log4j:WARN No appenders could be found for logger (org.java.plugin.ObjectFactory). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Jabref itself works fine. I am getting that warning too. Have a look at [1] which explains what it means. I opened a bug report with upstream [2]. Please feel free to add to it in case it needs more details. [1] http://logging.apache.org/log4j/1.2/faq.html#noconfig [2] https://sourceforge.net/p/jabref/bugs/1207/ Closing. Won't fix this version, since the beta seems to run fine. If anyone has issues with the beta version, please open a separate bug report. |