<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:15:27 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-1727] SPIKE: select particular implementation when interface is provided by multiple modules</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1727</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;In certain cases we may have multiple modules provide the same interface and there&apos;s no standard way to address it.&lt;/p&gt;</description>
                <environment></environment>
        <key id="79552">FOLIO-1727</key>
            <summary>SPIKE: select particular implementation when interface is provided by multiple modules</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="1" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                                        <assignee accountid="-1">Unassigned</assignee>
                                                                <reporter accountid="5f9abc1eb45b2e007453f423">John Malconian</reporter>
                                    <labels>
                            <label>ci</label>
                            <label>platform-backlog</label>
                    </labels>
                <created>Tue, 22 Jan 2019 18:54:13 +0000</created>
                <updated>Wed, 3 Jun 2020 16:39:24 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                <comments>
                                                            <comment id="191543" author="5f9abc1eb45b2e007453f423" created="Tue, 22 Jan 2019 18:58:14 +0000"  >&lt;p&gt;We&apos;ll start with updating the hosted folio-testing environment first and wait for the go ahead from &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; class=&quot;user-hover&quot; rel=&quot;557058:194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; data-account-id=&quot;557058:194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; accountid=&quot;557058:194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; rel=&quot;noreferrer&quot;&gt;Carole Godfrey&lt;/a&gt; before updating the folio-snapshot environment.    Since the two modules share the same interface versions,  the java-based module on master needs to be a higher version than the current version of the ruby-based module in order for Okapi&apos;s interface dependency resolution mechanism to resolve to the java-based module.  &lt;/p&gt;

</comment>
                                                            <comment id="191544" author="557058:194139f2-d44f-4adb-a0ad-8824bc5112d3" created="Tue, 22 Jan 2019 19:13:43 +0000"  >&lt;p&gt;Of note &amp;#8211; users of mod-kb-ebsco-java module require permission kb-ebsco.all to access needed backend functionality&lt;/p&gt;</comment>
                                                            <comment id="191545" author="5f9abc1eb45b2e007453f423" created="Tue, 22 Jan 2019 19:54:03 +0000"  >&lt;p&gt;mod-kb-ebsco is at version of 1.0.2-SNAPSHOT.157 on master according folio-registry.  The latest release version is v1.1.0.   mod-kb-ebsco-java is currently at 0.1.0-SNAPSHOT.   There is currently no MD for mod-kb-ebsco-java posted at folio-registry.    In order enable mod-kb-ebsco-java on folio-testing,  I&apos;ll need to manually post a MD for v0.1.0-SNAPSHOT to folio-registry.    When we are ready to enable mod-kb-ebsco-java on folio-snapshot,  we need to merge a mod-kb-ebsco-java PR that enables posting the MD to the registry as well as increment the version to v2.0.0-SNAPSHOT.    &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; does this sound right to you?   I guess I&apos;ll test the Okapi install endpoint to see which modules are resolved before implementing any changes. &lt;/p&gt;</comment>
                                                            <comment id="191546" author="5c706fbb47a54a6728e59df2" created="Tue, 22 Jan 2019 20:10:47 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; this sounds right, but why do we need to jump to v2.0.0? Did you mean v0.2.0?&lt;/p&gt;</comment>
                                                            <comment id="191547" author="5f9abc1eb45b2e007453f423" created="Tue, 22 Jan 2019 20:12:37 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; class=&quot;user-hover&quot; rel=&quot;557058:194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; data-account-id=&quot;557058:194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; accountid=&quot;557058:194139f2-d44f-4adb-a0ad-8824bc5112d3&quot; rel=&quot;noreferrer&quot;&gt;Carole Godfrey&lt;/a&gt; created &lt;a href=&quot;https://github.com/folio-org/mod-kb-ebsco-java/pull/91&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-kb-ebsco-java/pull/91&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="191548" author="5f9abc1eb45b2e007453f423" created="Tue, 22 Jan 2019 20:41:06 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; I did mean 2.0.0.  I wanted to ensure Okapi&apos;s install endpoint grabbed the latest version of the module (both modules have the same interface and interface version).   Now that I think about it, however,  I don&apos;t think this will guarantee anything since they different modules.  So,  I guess I&apos;m not sure what Okapi will do with different modules with the same interface/version and if it will be consistent.&lt;/p&gt;</comment>
                                                            <comment id="191549" author="5c706fbb47a54a6728e59df2" created="Tue, 22 Jan 2019 23:35:15 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; judging from &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1632?focusedCommentId=193183&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;this comment&lt;/a&gt; on 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1632&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1632&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create lighter-weight folio core VM&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1632
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
, Okapi will return an error.&lt;/p&gt;</comment>
                                                            <comment id="191550" author="5f9abc1eb45b2e007453f423" created="Wed, 23 Jan 2019 12:04:31 +0000"  >&lt;p&gt;Hmm. Bummer.  In the case of 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1632&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1632&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Create lighter-weight folio core VM&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1632
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 we could just remove the conflicting MDs.  In this case, however, we need to support older builds (Q3 &amp;amp; Q4 2018) so I cannot simply remove the old descriptors.    But can I?  The quarterly builds are based on static install.json files.  There is no &apos;okapi pull&apos; from folio-registry.   Instead,  the module descriptors for each module in the quarterly builds are posted directly to the Q3/Q4 okapi instance and not from the registry.   So I probably &lt;b&gt;could&lt;/b&gt; delete the old module&apos;s MDs from the registry.  However,  I&apos;m not sure who might be impacted by this outside of the our own CI environment.  &lt;/p&gt;</comment>
                                                            <comment id="191551" author="5c706fbb47a54a6728e59df2" created="Wed, 23 Jan 2019 13:59:23 +0000"  >&lt;p&gt;Doesn&apos;t the build task get the module descriptor from the registry with a GET request even if it doesn&apos;t do a pull? (I&apos;m pretty sure it does).&lt;/p&gt;

&lt;p&gt;Could we add mod-kb-ebsco-java as an &quot;extra&quot; module (as with mod-codex-&amp;#42;), so that it&apos;s posted to Okapi as part of the initial dependency resolution request?&lt;/p&gt;</comment>
                                                            <comment id="191552" author="5f9abc1eb45b2e007453f423" created="Wed, 23 Jan 2019 15:50:27 +0000"  >&lt;p&gt;yeah, you&apos;re right.  I guess we could add as an extra module although that seems a bit hacky.  Probably the likeliest solution at this point.  &lt;/p&gt;</comment>
                                                            <comment id="191553" author="5f8314dfbdef80006f6f572d" created="Tue, 29 Jan 2019 15:21:23 +0000"  >&lt;p&gt;I suppose even if Okapi had a &quot;replaces&quot; feature, like Debian (see 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;OKAPI-661&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/OKAPI-661&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Test effect of module renaming on Okapi dep resolution&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            OKAPI-661
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
) then.. if the interface and version are the same, the new module would still be pulled for a Q4 (or?) If so, &lt;br/&gt;
I think we should have a separate repo, just like Debian &amp;#8212; which has a repo per distribution.&lt;/p&gt;</comment>
                                                            <comment id="191554" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Tue, 29 Jan 2019 15:57:21 +0000"  >&lt;p&gt;How about codex? We have different modules implementing the same codex interface and version.&lt;/p&gt;</comment>
                                                            <comment id="191555" author="5f9abc1eb45b2e007453f423" created="Tue, 29 Jan 2019 16:01:38 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt; I don&apos;t think that any modules specify codex interfaces as a dependency, do they?  We typically declare the codex modules explicitly when installing.  &lt;/p&gt;</comment>
                                                            <comment id="191556" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Tue, 29 Jan 2019 16:13:29 +0000"  >&lt;p&gt;Does UI module count? &lt;a href=&quot;https://github.com/folio-org/ui-search/blob/master/package.json#L29&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-search/blob/master/package.json#L29&lt;/a&gt; &lt;/p&gt;</comment>
                                                            <comment id="191557" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Tue, 29 Jan 2019 16:31:18 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; Guys, I renamed this to represent the spike about finding the general solution. I cloned the original issue an linked it here.&lt;/p&gt;

&lt;p&gt;Question 1: do we need a general solution in order to complete 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1753&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1753&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Replace mod-kb-ebsco with mod-kb-ebsco-java in snapshot and test environments&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1753
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
? Wouldn&apos;t bumping the interface version solve the problem (to &quot;force&quot; the module upgrade).&lt;/p&gt;

&lt;p&gt;Question 2: it sounds like what we are after is the ability to control what implementation is used. Maybe we could add this to the MD?&lt;/p&gt;</comment>
                                                            <comment id="191558" author="5c706fbb47a54a6728e59df2" created="Tue, 29 Jan 2019 16:44:21 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ab8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; class=&quot;user-hover&quot; rel=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; data-account-id=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; accountid=&quot;557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d&quot; rel=&quot;noreferrer&quot;&gt;Jakub Skoczen&lt;/a&gt; &amp;#8211; are you suggesting that the MD contain the &quot;replaces&quot; functionality suggested by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt;? There is still the use case proposed by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt;, that a multi-tenant shared environment could offer multiple implementations of an interface as legitimate alternatives, not as a replacement (also not addressed by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt;&apos;s proposal to have separate module descriptor registries).&lt;/p&gt;</comment>
                                                            <comment id="191559" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Tue, 29 Jan 2019 16:47:33 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c706fbb47a54a6728e59df2&quot; class=&quot;user-hover&quot; rel=&quot;5c706fbb47a54a6728e59df2&quot; data-account-id=&quot;5c706fbb47a54a6728e59df2&quot; accountid=&quot;5c706fbb47a54a6728e59df2&quot; rel=&quot;noreferrer&quot;&gt;Wayne Schneider&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt; &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; class=&quot;user-hover&quot; rel=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; data-account-id=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; accountid=&quot;557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c&quot; rel=&quot;noreferrer&quot;&gt;Hongwei Ji&lt;/a&gt; Copy-paste what I wrote on slack:&lt;/p&gt;

&lt;p&gt;I think there are two use cases here:&lt;br/&gt;
&#8226; the module knows that it wants a particular implementation, perhaps because it&#8217;s newer or performs better. This is the case for mod-kb-ebsco-java&lt;br/&gt;
&#8226; service-provider wants to enforce a particular implementation for their hosting (this is more like the CODEX providers scenario)&lt;br/&gt;
It seems to me we would need two different features here:&lt;br/&gt;
&#8226; in the ModuleDescriptor for the module to &#8220;ask&#8221; for a particular implementation (I think this may be better than the &quot;replaces&quot; Adam proposes because replacing is only one use-case)&lt;br/&gt;
&#8226; in the /install to &#8220;force&#8221; a particular implementation for the tenant&lt;/p&gt;</comment>
                                                            <comment id="191560" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Tue, 29 Jan 2019 20:36:22 +0000"  >&lt;p&gt;I see the second feature is very much needed, and it also exists already as folks pointed out. For the first feature, I feel it blurs the line a bit between module and interface. From a practical perspective, feature 2 can do what feature 1 needs.&lt;/p&gt;</comment>
                                                            <comment id="191561" author="5f8314dfbdef80006f6f572d" created="Wed, 30 Jan 2019 15:54:01 +0000"  >&lt;p&gt;Replaces feature added to okapi - 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;OKAPI-661&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/OKAPI-661&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Test effect of module renaming on Okapi dep resolution&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            OKAPI-661
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
. This should make it easier to rename modules in the future&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10001">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                        <issuelink>
            <issuekey id="81074">FOLIO-1753</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="53554">OKAPI-337</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="54016">OKAPI-661</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10144"><![CDATA[Core: Platform]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzzcmf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 22 Jan 2019 19:13:43 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                </customfields>
    </item>
</channel>
</rss>