[jira] [Created] (OAK-7975) Facet extraction fails while requesting multiple facets and one of the requested facets doesn't have indexed values
Vikas Saurabh created OAK-7975:
--
Summary: Facet extraction fails while requesting multiple facets
and one of the requested facets doesn't have indexed values
Key: OAK-7975
URL: https://issues.apache.org/jira/browse/OAK-7975
Project: Jackrabbit Oak
Issue Type: Bug
Reporter: Vikas Saurabh
Assignee: Vikas Saurabh
Consider a content like
{noformat}
+ /test
- foo=bar
{noformat}
with index def faceting multiple properties - something like
{noformat}
+ /oak:index/foo/indexRules/nt:base/properties
+ foo
- propertyIndex=true
- facets = true
+ bar
- facets = true
{noformat}
Then a query like
{noformat}
SELECT [rep:facet(foo)], [rep:facete(bar)] FROM [nt:base]
{noformat}
should not fail.
Note that the failure requires requesting on multiple facets and one of them
must not have any indexed value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7975) Facet extraction fails while requesting multiple facets and one of the requested facets doesn't have indexed values
[
https://issues.apache.org/jira/browse/OAK-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-7975:
---
Component/s: lucene
> Facet extraction fails while requesting multiple facets and one of the
> requested facets doesn't have indexed values
> ---
>
> Key: OAK-7975
> URL: https://issues.apache.org/jira/browse/OAK-7975
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
>
> Consider a content like
> {noformat}
> + /test
>- foo=bar
> {noformat}
> with index def faceting multiple properties - something like
> {noformat}
> + /oak:index/foo/indexRules/nt:base/properties
>+ foo
> - propertyIndex=true
> - facets = true
> + bar
> - facets = true
> {noformat}
> Then a query like
> {noformat}
> SELECT [rep:facet(foo)], [rep:facete(bar)] FROM [nt:base]
> {noformat}
> should not fail.
> Note that the failure requires requesting on multiple facets and one of them
> must not have any indexed value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7965) Build Jackrabbit Oak #1859 failed
[ https://issues.apache.org/jira/browse/OAK-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737277#comment-16737277 ] Hudson commented on OAK-7965: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #1875|https://builds.apache.org/job/Jackrabbit%20Oak/1875/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/1875/console] > Build Jackrabbit Oak #1859 failed > - > > Key: OAK-7965 > URL: https://issues.apache.org/jira/browse/OAK-7965 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit Oak #1859 has failed. > First failed run: [Jackrabbit Oak > #1859|https://builds.apache.org/job/Jackrabbit%20Oak/1859/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/1859/console] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7898) Facet queries with UNION should do trivial merge of facets from sub-queries
[
https://issues.apache.org/jira/browse/OAK-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737244#comment-16737244
]
Julian Reschke commented on OAK-7898:
-
While releasing 1.6.16, we noticed that
`org.apache.jackrabbit.oak.query.facet.FacetResult` now has the same API
version as the variant in 1.8.10, despite their APIs not being identical. This
is because 1.6 uses the old JSR 305 annotations, while 1.8 uses JetBrains
annotations (see https://issues.apache.org/jira/browse/OAK-7511). We believe
this is ok, and any "proper" fix (like backporting the annotation change to 1.6
as well) would be very complex.
> Facet queries with UNION should do trivial merge of facets from sub-queries
> ---
>
> Key: OAK-7898
> URL: https://issues.apache.org/jira/browse/OAK-7898
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.10, 1.8.10, 1.9.12, 1.6.16
>
>
> Queries such as {noformat} //*[@name = 'Node1' or @text =
> 't2']/(rep:facet(text)) {noformat} get split into 2 sub-queries such as
> # {noformat} //*[@name = 'Node1']/(rep:facet(text)) {noformat}
> # {noformat} //*[@test = 't2']/(rep:facet(text)) {noformat}
> Trivially merging facets (union of labels and sum of counts for same labels)
> across sub-queries in generally wrong because of potential intersection rows.
> But, in common practical cases, intersections aren't a big majority so,
> albeit incorrect, trivial merge shouldn't be off huge amount. Note that usual
> path restrictions and node type restrictions are the most common case with
> {{OR}} and they do have have no intersection in almost all cases.
> Also, while we'd re-sort the merged facets but we'd make no attempt to prune
> the list to match limits on facet count implied by index-definitions. This is
> basically for 2 reasons:
> * sub-queries might get answered by separate indexes (this could be the case
> with search on different node types)
> * merge of facets would happen in query engine and we won't want to route
> back information about index-definition or its semantics from index provider
> to query engine
> That said, since it's going to give incorrect result by design, we need to
> very explicit in our documentation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7974) Detailed merge metrics
[ https://issues.apache.org/jira/browse/OAK-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737196#comment-16737196 ] Marcel Reutegger commented on OAK-7974: --- Work in progress available at https://github.com/mreutegg/jackrabbit-oak/tree/OAK-7974 > Detailed merge metrics > -- > > Key: OAK-7974 > URL: https://issues.apache.org/jira/browse/OAK-7974 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Major > Fix For: 1.12 > > > The DocumentNodeStore currently only exposes basis metrics for the merge > operation. To further analyze where time is spent, more detailed merge > metrics must be introduced. This includes: > - Creating a new commit revision timer > - Background lock acquisition timer > - Wait until head timer > - Commit suspend timer > - Commit hook timer -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OAK-7946) Doc / size index stats fails when indexes not loaded
[ https://issues.apache.org/jira/browse/OAK-7946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved OAK-7946. - Resolution: Won't Fix We decided this is a known issue, and we don't plan to change the behavior. > Doc / size index stats fails when indexes not loaded > > > Key: OAK-7946 > URL: https://issues.apache.org/jira/browse/OAK-7946 > Project: Jackrabbit Oak > Issue Type: Task > Components: lucene >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili >Priority: Major > > As a follow up to OAK-7893, it seems that sometimes the index size and doc > count stats cannot be calculated because the underlying Lucene index cannot > be obtained either because the repository is not yet started or because the > indexes weren't previously loaded / accessed except from within the stats > calculation callback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7962) FV reranking should be enabled by default
[ https://issues.apache.org/jira/browse/OAK-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7962: Fix Version/s: 1.10 > FV reranking should be enabled by default > - > > Key: OAK-7962 > URL: https://issues.apache.org/jira/browse/OAK-7962 > Project: Jackrabbit Oak > Issue Type: Task > Components: lucene >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili >Priority: Major > Fix For: 1.10, 1.9.14 > > > In order to improve the precision of the search results, reranking should be > enabled by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7947) Lazy loading of Lucene index files startup
[ https://issues.apache.org/jira/browse/OAK-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-7947: Fix Version/s: 1.9.14 > Lazy loading of Lucene index files startup > -- > > Key: OAK-7947 > URL: https://issues.apache.org/jira/browse/OAK-7947 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene, query >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > Fix For: 1.9.14 > > Attachments: OAK-7947.patch, OAK-7947_v2.patch, OAK-7947_v3.patch, > OAK-7947_v4.patch, lucene-index-open-access.zip > > > Right now, all Lucene index binaries are loaded on startup (I think when the > first query is run, to do cost calculation). This is a performance problem if > the index files are large, and need to be downloaded from the data store. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7968) Active deletion of Lucene binaries: configuration option to disable
[ https://issues.apache.org/jira/browse/OAK-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-7968: Fix Version/s: 1.9.14 > Active deletion of Lucene binaries: configuration option to disable > --- > > Key: OAK-7968 > URL: https://issues.apache.org/jira/browse/OAK-7968 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing, lucene >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > Fix For: 1.9.14 > > Attachments: OAK-7968.patch > > > Active deletion of Lucene binaries (OAK-2808) can be disabled temporarily > (OAK-6862), however I don't think there is a simple way to disable it > permanently, using a config option (OSGi config / system property). > It would be good to have such an option to support the use case where the > repository is cloned at runtime, and the clones are started. A workaround is > to call the JMX method after startup, but that's a bit inconvenient. It would > be best if the config option ensure it's also disabled during startup, even > thought it's unlikely that active deletion is scheduled during this startup > window (better be on the safe side). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7968) Active deletion of Lucene binaries: configuration option to disable
[ https://issues.apache.org/jira/browse/OAK-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737086#comment-16737086 ] Thomas Mueller commented on OAK-7968: - http://svn.apache.org/r1850741 (trunk) > Active deletion of Lucene binaries: configuration option to disable > --- > > Key: OAK-7968 > URL: https://issues.apache.org/jira/browse/OAK-7968 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing, lucene >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > Attachments: OAK-7968.patch > > > Active deletion of Lucene binaries (OAK-2808) can be disabled temporarily > (OAK-6862), however I don't think there is a simple way to disable it > permanently, using a config option (OSGi config / system property). > It would be good to have such an option to support the use case where the > repository is cloned at runtime, and the clones are started. A workaround is > to call the JMX method after startup, but that's a bit inconvenient. It would > be best if the config option ensure it's also disabled during startup, even > thought it's unlikely that active deletion is scheduled during this startup > window (better be on the safe side). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737052#comment-16737052
]
Julian Reschke commented on OAK-7368:
-
trunk: [r1832258|http://svn.apache.org/r1832258]
1.8: [r1832337|http://svn.apache.org/r1832337]
1.6: [r1850736|http://svn.apache.org/r1850736]
[r1846636|http://svn.apache.org/r1846636]
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.10, 1.8.4, 1.9.3
>
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OAK-7974) Detailed merge metrics
Marcel Reutegger created OAK-7974: - Summary: Detailed merge metrics Key: OAK-7974 URL: https://issues.apache.org/jira/browse/OAK-7974 Project: Jackrabbit Oak Issue Type: Improvement Components: documentmk Reporter: Marcel Reutegger Assignee: Marcel Reutegger Fix For: 1.12 The DocumentNodeStore currently only exposes basis metrics for the merge operation. To further analyze where time is spent, more detailed merge metrics must be introduced. This includes: - Creating a new commit revision timer - Background lock acquisition timer - Wait until head timer - Commit suspend timer - Commit hook timer -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-7368:
Comment: was deleted
(was: trunk: [r1832258|http://svn.apache.org/r1832258]
1.8: [r1832337|http://svn.apache.org/r1832337]
)
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.10, 1.8.4, 1.9.3
>
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-7368:
Fix Version/s: (was: 1.6.16)
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.10, 1.8.4, 1.9.3
>
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OAK-7578) Update spotbugs plugin to 3.1.5
[ https://issues.apache.org/jira/browse/OAK-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737041#comment-16737041 ] Julian Reschke edited comment on OAK-7578 at 1/8/19 11:58 AM: -- Reverting the change in 1.6, as spotbugs is not compatible with Java 7. was (Author: reschke): Reverting the change, as spotbugs is not compatible with Java 7. > Update spotbugs plugin to 3.1.5 > --- > > Key: OAK-7578 > URL: https://issues.apache.org/jira/browse/OAK-7578 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 1.10, 1.9.5, 1.8.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-7368:
Labels: (was: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4)
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.10, 1.8.4, 1.9.3, 1.6.16
>
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OAK-7368) update to findbugs version compatible with jdk 10
[
https://issues.apache.org/jira/browse/OAK-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737049#comment-16737049
]
Julian Reschke commented on OAK-7368:
-
Reverting the change in 1.6, as spotbugs is not compatible with Java 7.
> update to findbugs version compatible with jdk 10
> --
>
> Key: OAK-7368
> URL: https://issues.apache.org/jira/browse/OAK-7368
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Alex Deparvu
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
> Fix For: 1.10, 1.8.4, 1.9.3, 1.6.16
>
>
> Warnings running findbugs
> {noformat}
> [INFO] --- findbugs-maven-plugin:3.0.4:findbugs (findbugs) @ oak-commons ---
> [INFO] Fork Value is true
> [java] Warning: Unknown version of Java
> [java] edu.umd.cs.findbugs.JavaVersionException: Could not parse Java
> version string: 10
> [java] at edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:68)
> [java] at
> edu.umd.cs.findbugs.JavaVersion.(JavaVersion.java:44)
> [java] at
> edu.umd.cs.findbugs.DetectorFactory.isEnabledForCurrentJRE(DetectorFactory.java:248)
> [java] at
> edu.umd.cs.findbugs.FindBugs.isDetectorEnabled(FindBugs.java:256)
> [java] at edu.umd.cs.findbugs.FindBugs2$3.choose(FindBugs2.java:906)
> [java] at
> edu.umd.cs.findbugs.plan.ExecutionPlan.build(ExecutionPlan.java:179)
> [java] at
> edu.umd.cs.findbugs.FindBugs2.createExecutionPlan(FindBugs2.java:935)
> [java] at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:241)
> [java] at edu.umd.cs.findbugs.FindBugs.runMain(FindBugs.java:402)
> [java] at edu.umd.cs.findbugs.FindBugs2.main(FindBugs2.java:1200)
> {noformat}
> it seems findbugs-maven-plugin 3.0.5 (latest release) does not fix this and I
> couldn't find an open issue related to java 10.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OAK-7578) Update spotbugs plugin to 3.1.5
[ https://issues.apache.org/jira/browse/OAK-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7578: Fix Version/s: (was: 1.6.16) > Update spotbugs plugin to 3.1.5 > --- > > Key: OAK-7578 > URL: https://issues.apache.org/jira/browse/OAK-7578 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 1.10, 1.9.5, 1.8.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7578) Update spotbugs plugin to 3.1.5
[ https://issues.apache.org/jira/browse/OAK-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737045#comment-16737045 ] Julian Reschke commented on OAK-7578: - trunk: [r1834112|http://svn.apache.org/r1834112] 1.8: [r1840043|http://svn.apache.org/r1840043] 1.6: [r1850735|http://svn.apache.org/r1850735] [r1846637|http://svn.apache.org/r1846637] > Update spotbugs plugin to 3.1.5 > --- > > Key: OAK-7578 > URL: https://issues.apache.org/jira/browse/OAK-7578 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 1.10, 1.9.5, 1.8.8, 1.6.16 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (OAK-7578) Update spotbugs plugin to 3.1.5
[ https://issues.apache.org/jira/browse/OAK-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7578: Comment: was deleted (was: trunk: [r1834112|http://svn.apache.org/r1834112] 1.8: [r1840043|http://svn.apache.org/r1840043] ) > Update spotbugs plugin to 3.1.5 > --- > > Key: OAK-7578 > URL: https://issues.apache.org/jira/browse/OAK-7578 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 1.10, 1.9.5, 1.8.8, 1.6.16 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OAK-7578) Update spotbugs plugin to 3.1.5
[ https://issues.apache.org/jira/browse/OAK-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737041#comment-16737041 ] Julian Reschke commented on OAK-7578: - Reverting the change, as spotbugs is not compatible with Java 7. > Update spotbugs plugin to 3.1.5 > --- > > Key: OAK-7578 > URL: https://issues.apache.org/jira/browse/OAK-7578 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 1.10, 1.9.5, 1.8.8, 1.6.16 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-7578) Update spotbugs plugin to 3.1.5
[ https://issues.apache.org/jira/browse/OAK-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-7578: Labels: (was: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4) > Update spotbugs plugin to 3.1.5 > --- > > Key: OAK-7578 > URL: https://issues.apache.org/jira/browse/OAK-7578 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 1.10, 1.9.5, 1.8.8, 1.6.16 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OAK-7973) Release Oak 1.4.24
Julian Reschke created OAK-7973: --- Summary: Release Oak 1.4.24 Key: OAK-7973 URL: https://issues.apache.org/jira/browse/OAK-7973 Project: Jackrabbit Oak Issue Type: Task Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian JIRA (v7.6.3#76005)
