You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/10/30 23:47:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17781163#comment-17781163 ]
Tamas Cservenak commented on MINDEXER-206:
------------------------------------------
Counter arguments:
* RR backend is really about (resolver level) files, so packaging here does not makes sense
* SMO service provider requires and forces use of {{p}} for packaging, in fact, they force it wrongfully, see {{takari-jar}} packaging.
In short, unsure is this issue is really an issue at all...
> 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.1
>
>
> 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)