[jira] [Updated] (MINDEXER-206) Search Backend SMO and RR handle different Artifact.extension
[ https://issues.apache.org/jira/browse/MINDEXER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MINDEXER-206: - Fix Version/s: (was: 7.1.3) > Search Backend SMO and RR handle different Artifact.extension > - > > Key: MINDEXER-206 > URL: https://issues.apache.org/jira/browse/MINDEXER-206 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > > The two backends should not force caller to construct Query differently, but > handle their own implementation specifics silently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINDEXER-206) Search Backend SMO and RR handle different Artifact.extension
[ https://issues.apache.org/jira/browse/MINDEXER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MINDEXER-206: - Fix Version/s: 7.1.3 (was: 7.1.2) > Search Backend SMO and RR handle different Artifact.extension > - > > Key: MINDEXER-206 > URL: https://issues.apache.org/jira/browse/MINDEXER-206 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > Fix For: 7.1.3 > > > The two backends should not force caller to construct Query differently, but > handle their own implementation specifics silently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINDEXER-206) Search Backend SMO and RR handle different Artifact.extension
[ https://issues.apache.org/jira/browse/MINDEXER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MINDEXER-206: - Fix Version/s: 7.1.2 (was: 7.1.1) > Search Backend SMO and RR handle different Artifact.extension > - > > Key: MINDEXER-206 > URL: https://issues.apache.org/jira/browse/MINDEXER-206 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Tamas Cservenak >Priority: Major > Fix For: 7.1.2 > > > The two backends should not force caller to construct Query differently, but > handle their own implementation specifics silently. -- This message was sent by Atlassian Jira (v8.20.10#820010)