Certainly, this example borders on rudeness. (Is someone waiting on a surgical table for the answer?) Other open source projects with which I am involved have had similar problems. One thing that might help here is a bit of language on the home page explaining that Jena is an all-volunteer project, but that there are forms of commercial support available, and that someone with particular needs for support should investigate them. Sometimes just being reminded that "you get what you pay for" helps adjust people's expectations.
Just to check, I think there might be a typo in the words of the proposed policy, Andy: 'cause additional work, are "reproducable", or a really questions'. You mean 'are [not] "reproducable"', right? Also, do I understand the policy correctly that a proposed issue that implies additional work should get closed, not as a blank rejection, but for discussion on-list and/or on the way to opening other, more appropriately "factored" issues? --- A. Soroka The University of Virginia Library > On Apr 21, 2016, at 7:35 AM, Andy Seaborne <[email protected]> wrote: > > I'd like to open a discussion on what is and is not a reasonable JIRA so that > we can close ones that are outside what JIRA is good for. > > I closed this on the principle that repeatedly asking the same question in > many places in just a few hours is unhelpful. > > Here, the JIRA version doesn't have as much information as the StackOverflow > question which itself is fragments that don't illustrate the problem. > > (My bet on the cause is either repackaging or classloaders!) > > I think we need to not allow JIRA items that cause additional work, are > "reproducable", or a really questions. > > If we get ones that are questions, direct to mailing lists without answer on > JIRA. (does not apply so much to this is one) > > if they don't have a complete, minimal example, ask for one, once. If none > is forthcoming, close the JIRA. It can take significant time to figure out > what a test case is and that time is taken away from answering other > questions. > > Andy > > > -------- Forwarded Message -------- > Subject: [jira] [Closed] (JENA-1166) Jena TDB > java.lang.ExceptionInInitializerError > Date: Thu, 21 Apr 2016 08:11:25 +0000 (UTC) > From: Andy Seaborne (JIRA) <[email protected]> > Reply-To: [email protected] > To: [email protected] > > > [ > https://issues.apache.org/jira/browse/JENA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Andy Seaborne closed JENA-1166. > ------------------------------- > Resolution: Cannot Reproduce > Assignee: Andy Seaborne > > The report on StackOverflow contains more information but is still > incomplete. The SO entry was created 3h before this JIRA. Patience. > >> Jena TDB java.lang.ExceptionInInitializerError >> ---------------------------------------------- >> >> Key: JENA-1166 >> URL: https://issues.apache.org/jira/browse/JENA-1166 >> Project: Apache Jena >> Issue Type: Bug >> Components: TDB >> Affects Versions: Jena 3.0.1 >> Environment: Ubuntu 14.04, Java 1.8.0_77 >> Reporter: Ritesh Kumar Singh >> Assignee: Andy Seaborne >> Original Estimate: 24h >> Remaining Estimate: 24h >> >> Exception in thread "main" java.lang.ExceptionInInitializerError >> >> Caused by: java.lang.NullPointerException >> at >> org.apache.jena.tdb.sys.EnvTDB.processGlobalSystemProperties(EnvTDB.java:33) >> at org.apache.jena.tdb.TDB.init(TDB.java:250) >> at org.apache.jena.tdb.sys.InitTDB.start(InitTDB.java:29) >> at org.apache.jena.system.JenaSystem.lambda$init$40(JenaSystem.java:114) >> at java.util.ArrayList.forEach(ArrayList.java:1249) >> at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:179) >> at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:156) >> at org.apache.jena.system.JenaSystem.init(JenaSystem.java:111) >> at org.apache.jena.tdb.TDBFactory.<clinit>(TDBFactory.java:40) >> ... 2 more >> Link to issue details: >> https://stackoverflow.com/questions/36755846/jena-tdb-java-lang-exceptionininitializererror > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > >
