Re: JENA-626 Re: Towards release 3.1.0

[Saikat Maitra]

Hi Andy,

No problem at all.

Regards
Saikat

On Wed, Apr 20, 2016 at 2:04 AM, Andy Seaborne  wrote:

> Saikat,
>
> Sorry this has taken so long to get looked at.
>
> Andy
>
>

[jira] [Resolved] (JENA-1165) Feature to handle undefined prefixes by converting to URIs

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-1165.
-
   Resolution: Fixed
Fix Version/s: Jena 3.1.0

> Feature to handle undefined prefixes by converting to URIs
> --
>
> Key: JENA-1165
> URL: https://issues.apache.org/jira/browse/JENA-1165
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> When discussing queries and data, prefixes are often omitted.
> This JIRA proposes handling undefined prefixes by converting them to some 
> recognizable URIs.
> This feature would be off by default. 
> It would be settable in command line tools such as {{qparse}}, {{sparql}}, 
> {{riot}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-1165) Feature to handle undefined prefixes by converting to URIs

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1165:

Attachment: (was: Q.rq)

> Feature to handle undefined prefixes by converting to URIs
> --
>
> Key: JENA-1165
> URL: https://issues.apache.org/jira/browse/JENA-1165
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> When discussing queries and data, prefixes are often omitted.
> This JIRA proposes handling undefined prefixes by converting them to some 
> recognizable URIs.
> This feature would be off by default. 
> It would be settable in command line tools such as {{qparse}}, {{sparql}}, 
> {{riot}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-1165) Feature to handle undefined prefixes by converting to URIs

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1165:

Attachment: (was: dwim)

> Feature to handle undefined prefixes by converting to URIs
> --
>
> Key: JENA-1165
> URL: https://issues.apache.org/jira/browse/JENA-1165
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> When discussing queries and data, prefixes are often omitted.
> This JIRA proposes handling undefined prefixes by converting them to some 
> recognizable URIs.
> This feature would be off by default. 
> It would be settable in command line tools such as {{qparse}}, {{sparql}}, 
> {{riot}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-1167) VALUES gets pushed to front wrongly.

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1167:

Attachment: Q.rq
dwim
D.ttl

> VALUES gets pushed to front wrongly.
> 
>
> Key: JENA-1167
> URL: https://issues.apache.org/jira/browse/JENA-1167
> Project: Apache Jena
>  Issue Type: Bug
>  Components: ARQ
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
> Attachments: D.ttl, Q.rq, dwim
>
>
> {noformat}
> Query: Q.rq
>  1PREFIX rdfs: 
>  2PREFIX ex:  
>  3SELECT ?label {
>  4{
>  5FILTER (bound(?arg1))
>  6}
>  7?arg1 rdfs:label ?label
>  8}
>  9VALUES ?arg1 { ex:a  UNDEF }
> Data: D.ttl
>  1@prefix rdfs: .
>  2@prefix ex: .
>  3
>  4ex:a rdfs:label "A".
>  5ex:b rdfs:label "B".
> Execute: qparse --print=op --print=opt --query Q.rq
> (prefix ((rdfs: )
>  (ex: ))
>   (project (?label)
> (join
>   (join
> (filter (bound ?arg1)
>   (table unit))
> (bgp (triple ?arg1 rdfs:label ?label)))
>   (table (vars ?arg1)
> (row [?arg1 ex:a])
> (row)
>   
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> (prefix ((rdfs: )
>  (ex: ))
>   (project (?label)
> (sequence
>   (table (vars ?arg1)
> (row [?arg1 ex:a])
> (row)
>   )
>   (sequence
> (filter (bound ?arg1)
>   (table unit))
> (bgp (triple ?arg1 rdfs:label ?label))
> Execute: sparql --engine=ref --query Q.rq --data D.ttl
> -
> | label |
> =
> -
> Execute: sparql --query Q.rq --data D.ttl
> -
> | label |
> =
> | "A"   |
> -
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-1165) Feature to handle undefined prefixes by converting to URIs

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1165:

Attachment: (was: D.ttl)

> Feature to handle undefined prefixes by converting to URIs
> --
>
> Key: JENA-1165
> URL: https://issues.apache.org/jira/browse/JENA-1165
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> When discussing queries and data, prefixes are often omitted.
> This JIRA proposes handling undefined prefixes by converting them to some 
> recognizable URIs.
> This feature would be off by default. 
> It would be settable in command line tools such as {{qparse}}, {{sparql}}, 
> {{riot}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1165) Feature to handle undefined prefixes by converting to URIs

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252684#comment-15252684
 ] 

ASF GitHub Bot commented on JENA-1165:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/136


> Feature to handle undefined prefixes by converting to URIs
> --
>
> Key: JENA-1165
> URL: https://issues.apache.org/jira/browse/JENA-1165
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Attachments: D.ttl, Q.rq, dwim
>
>
> When discussing queries and data, prefixes are often omitted.
> This JIRA proposes handling undefined prefixes by converting them to some 
> recognizable URIs.
> This feature would be off by default. 
> It would be settable in command line tools such as {{qparse}}, {{sparql}}, 
> {{riot}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: Unset prefixes

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/136


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JENA-1165) Feature to handle undefined prefixes by converting to URIs

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252681#comment-15252681
 ] 

Andy Seaborne commented on JENA-1165:
-

Merged with 
http://git-wip-us.apache.org/repos/asf/jena/commit/316772ce


> Feature to handle undefined prefixes by converting to URIs
> --
>
> Key: JENA-1165
> URL: https://issues.apache.org/jira/browse/JENA-1165
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Attachments: D.ttl, Q.rq, dwim
>
>
> When discussing queries and data, prefixes are often omitted.
> This JIRA proposes handling undefined prefixes by converting them to some 
> recognizable URIs.
> This feature would be off by default. 
> It would be settable in command line tools such as {{qparse}}, {{sparql}}, 
> {{riot}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Establishing JIRA principles/etiquette.

[A. Soroka]

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  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 + (UTC)
> From: Andy Seaborne (JIRA) 
> Reply-To: dev@jena.apache.org
> To: dev@jena.apache.org
> 
> 
> [ 
> 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.(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)
> 
> 

[jira] [Updated] (JENA-1165) Feature to handle undefined prefixes by converting to URIs

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1165:

Attachment: Q.rq
dwim
D.ttl

> Feature to handle undefined prefixes by converting to URIs
> --
>
> Key: JENA-1165
> URL: https://issues.apache.org/jira/browse/JENA-1165
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Attachments: D.ttl, Q.rq, dwim
>
>
> When discussing queries and data, prefixes are often omitted.
> This JIRA proposes handling undefined prefixes by converting them to some 
> recognizable URIs.
> This feature would be off by default. 
> It would be settable in command line tools such as {{qparse}}, {{sparql}}, 
> {{riot}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (JENA-1167) VALUES gets pushed to front wrongly.

[Andy Seaborne (JIRA)]

Andy Seaborne created JENA-1167:
---

 Summary: VALUES gets pushed to front wrongly.
 Key: JENA-1167
 URL: https://issues.apache.org/jira/browse/JENA-1167
 Project: Apache Jena
  Issue Type: Bug
  Components: ARQ
Affects Versions: Jena 3.0.1
Reporter: Andy Seaborne


{noformat}
Query: Q.rq
 1  PREFIX rdfs: 
 2  PREFIX ex:  
 3  SELECT ?label {
 4  {
 5  FILTER (bound(?arg1))
 6  }
 7  ?arg1 rdfs:label ?label
 8  }
 9  VALUES ?arg1 { ex:a  UNDEF }
Data: D.ttl
 1  @prefix rdfs: .
 2  @prefix ex: .
 3  
 4  ex:a rdfs:label "A".
 5  ex:b rdfs:label "B".
Execute: qparse --print=op --print=opt --query Q.rq
(prefix ((rdfs: )
 (ex: ))
  (project (?label)
(join
  (join
(filter (bound ?arg1)
  (table unit))
(bgp (triple ?arg1 rdfs:label ?label)))
  (table (vars ?arg1)
(row [?arg1 ex:a])
(row)
  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(prefix ((rdfs: )
 (ex: ))
  (project (?label)
(sequence
  (table (vars ?arg1)
(row [?arg1 ex:a])
(row)
  )
  (sequence
(filter (bound ?arg1)
  (table unit))
(bgp (triple ?arg1 rdfs:label ?label))
Execute: sparql --engine=ref --query Q.rq --data D.ttl
-
| label |
=
-
Execute: sparql --query Q.rq --data D.ttl
-
| label |
=
| "A"   |
-
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (JENA-1166) Jena TDB java.lang.ExceptionInInitializerError

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne closed JENA-1166.
---
Resolution: Incomplete

> 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.(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)

[jira] [Commented] (JENA-1166) Jena TDB java.lang.ExceptionInInitializerError

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251831#comment-15251831
 ] 

Andy Seaborne commented on JENA-1166:
-

The original posting was incomplete and failed to say that it worked in Eclipse 
but not outside.

The new information is a dump of another project.

Complete, minimal example please - not a project dump.

The quoted email does contain the answer.



> 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.(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)

[jira] [Commented] (JENA-1166) Jena TDB java.lang.ExceptionInInitializerError

[Ritesh Kumar Singh (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251801#comment-15251801
 ] 

Ritesh Kumar Singh commented on JENA-1166:
--

I guess this issue is not new. On googling I found this in the mail archive: 
https://mail-archives.apache.org/mod_mbox/jena-users/201602.mbox/%3c56b47b8a.2040...@apache.org%3E

Though, there was no specific solution mentioned.

> 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.(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)

[jira] [Reopened] (JENA-1166) Jena TDB java.lang.ExceptionInInitializerError

[Ritesh Kumar Singh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ritesh Kumar Singh reopened JENA-1166:
--

The issue can be reproduced by compiling and running this framework: 
https://github.com/gone-phishing/SDW

Running the above framework using eclipse doesn't give an error as I guess 
eclipse does the bundling on its own but when launching via the command line, I 
had the same issue on several systems. 



> 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.(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)

Establishing JIRA principles/etiquette.

[Andy Seaborne]

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 + (UTC)
From: Andy Seaborne (JIRA) 
Reply-To: dev@jena.apache.org
To: dev@jena.apache.org


 [ 
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.(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)

[jira] [Closed] (JENA-1166) Jena TDB java.lang.ExceptionInInitializerError

[Andy Seaborne (JIRA)]

 [ 
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.(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)

[jira] [Closed] (JENA-1166) Jena TDB java.lang.ExceptionInInitializerError

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne closed JENA-1166.
---
Resolution: Invalid

> 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
>   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.(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)

[jira] [Reopened] (JENA-1166) Jena TDB java.lang.ExceptionInInitializerError

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne reopened JENA-1166:
-

> 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
>   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.(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)