[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulceanu updated OAK-3919: - Fix Version/s: (was: 1.38.0) 1.40.0 > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.40.0 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulceanu updated OAK-3919: - Fix Version/s: (was: 1.36.0) > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.38.0 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulceanu updated OAK-3919: - Fix Version/s: 1.38.0 > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.36.0, 1.38.0 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3919: -- Fix Version/s: (was: 1.14.0) > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.16.0 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3919: -- Fix Version/s: 1.16.0 > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.14.0, 1.16.0 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3919: -- Fix Version/s: (was: 1.12.0) > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.14.0 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3919: -- Fix Version/s: 1.14.0 > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.12.0, 1.14.0 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3919: -- Fix Version/s: (was: 1.10.0) > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.12 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-3919: -- Fix Version/s: 1.12 > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig >Priority: Major > Labels: modularization, technical_debt > Fix For: 1.10.0, 1.12 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-3919: --- Fix Version/s: (was: 1.8) 1.10 > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig > Labels: modularization, technical_debt > Fix For: 1.10 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Saar updated OAK-3919: Fix Version/s: (was: 1.6) 1.8 > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig > Labels: modularization, technical_debt > Fix For: 1.8 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3919) Properly manage APIs / SPIs intended for public consumption
[ https://issues.apache.org/jira/browse/OAK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-3919: Component/s: core > Properly manage APIs / SPIs intended for public consumption > --- > > Key: OAK-3919 > URL: https://issues.apache.org/jira/browse/OAK-3919 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig > Labels: modularization, technical_debt > Fix For: 1.6 > > > This is a follow up to OAK-3842, which removed package export declarations > for all packages that we either do not want to be used outside of Oak or that > are not stable enough yet. > This issue is to identify those APIs and SPIs of Oak that we actually *want* > to export and to refactor those such we *can* export them. > Candidates that are currently used from upstream projects I know of are: > {code} > org.apache.jackrabbit.oak.plugins.observation > org.apache.jackrabbit.oak.spi.commit > org.apache.jackrabbit.oak.spi.state > org.apache.jackrabbit.oak.commons > org.apache.jackrabbit.oak.plugins.index.lucene > {code} > I suggest to create subtask for those we want to go forward with. -- This message was sent by Atlassian JIRA (v6.3.4#6332)