<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:07:17 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>[RMB-30] Trouble with a schema file referring to another schema in raml-util</title>
                <link>https://folio-org.atlassian.net/browse/RMB-30</link>
                <project id="10140" key="RMB">RAML Module Builder</project>
                    <description>&lt;p&gt;Using relative links between schema for RAML does work okay for both sets of tools (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-573&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-573&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Use a consistent method for RAML to refer to a parent JSON schema which refers to another JSON schema&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-573
        &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;
), i.e. use the relative pathname in the schema files, and as the schema key name in the RAML file.&lt;/p&gt;

&lt;p&gt;However, when attempting to refer to a schema file in the shared &quot;raml-util&quot; then there can be a problem.&lt;/p&gt;

&lt;p&gt;(Note that some early comments below would need some adjustment.&lt;br/&gt;
See the diagnosis at &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-30?focusedCommentId=134578&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;21/Jun/17&lt;/a&gt;&lt;br/&gt;
and the solution at &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-30?focusedCommentId=134580&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;22/Jun/17&lt;/a&gt; onwards.)&lt;/p&gt;</description>
                <environment></environment>
        <key id="56721">RMB-30</key>
            <summary>Trouble with a schema file referring to another schema in raml-util</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="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="61cd0ca0bce5e00069e98be7">David Crossley</assignee>
                                                                <reporter accountid="61cd0ca0bce5e00069e98be7">David Crossley</reporter>
                                    <labels>
                            <label>raml</label>
                            <label>sprint19</label>
                    </labels>
                <created>Wed, 31 May 2017 03:34:56 +0000</created>
                <updated>Tue, 5 Sep 2017 07:56:55 +0000</updated>
                            <resolved>Wed, 9 Aug 2017 06:16:31 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                                                            <comment id="134563" author="61cd0ca0bce5e00069e98be7" created="Wed, 31 May 2017 03:35:56 +0000"  >&lt;p&gt;So for example, for the raml-module-builder repository, if it was like this then it is processed okay:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
raml-module-builder/ramls/schemas/
raml-module-builder/raml-util/schemas/

in raml-module-builder/ramls/schemas/job.schema
  &lt;span class=&quot;code-quote&quot;&gt;&quot;$ref&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;../../raml-util/schemas/parameters.schema&quot;&lt;/span&gt;

in raml-module-builder/ramls/jobs.raml
  - ../../raml-util/schemas/parameters.schema: !include ../raml-util/schemas/parameters.schema

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;However with the current location (raml-module-builder/domain-models-api-interfaces/src/main/resources/raml/schemas) or any other place, then raml-for-jax-rs in RMB cannot handle it.&lt;/p&gt;</comment>
                                                            <comment id="134564" author="5c38e8d616ac1e4f7cbc660a" created="Thu, 1 Jun 2017 20:03:51 +0000"  >&lt;p&gt;Isn&apos;t this more specifically an RMB issue? When I check these files with raml-cop, they validate fine.&lt;/p&gt;</comment>
                                                            <comment id="134565" author="61cd0ca0bce5e00069e98be7" created="Thu, 1 Jun 2017 22:42:55 +0000"  >&lt;p&gt;The raml-module-builder repo is the only one at the moment that uses $ref in a schema to refer to another schema in the &quot;raml-util&quot; area. When we try to use the relative pathname as the schema key, then raml-cop is fine because its underlying parser does not utilise the schema key name (just the &quot;!include&quot; path). The raml-for-jax-rs (underlying the RMB) then chokes.&lt;/p&gt;

&lt;p&gt;However all is okay in other repos where the raml-util directory is at the same directory tree level as its &quot;ramls&quot; directory.&lt;/p&gt;

&lt;p&gt;So yes it is &quot;only&quot; the RMB that has a problem if the directories are not like that.&lt;/p&gt;

&lt;p&gt;The complicated issues with raml-for-jax-rs are linked in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-573&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-573&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Use a consistent method for RAML to refer to a parent JSON schema which refers to another JSON schema&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-573
        &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 seems like another wrinkle.&lt;/p&gt;</comment>
                                                            <comment id="134566" author="712020:32bb56ac-50e7-4787-b4af-ed3089d9401c" created="Mon, 5 Jun 2017 12:33:55 +0000"  >&lt;p&gt;hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;&lt;br/&gt;
creating relative paths entries works with a limited amount of ../../&lt;br/&gt;
can we set this as an open issue that the /raml and /raml-util should both be root directories in an rmb project?&lt;br/&gt;
i dont really know how to fix this &lt;/p&gt;</comment>
                                                            <comment id="134567" author="61cd0ca0bce5e00069e98be7" created="Wed, 7 Jun 2017 06:31:52 +0000"  >&lt;p&gt;I enhanced the note in raml-module-builder/README.md to advise about the placement of those directories.&lt;/p&gt;

&lt;p&gt;Our other RMB-using modules do already have such an arrangement.&lt;/p&gt;</comment>
                                                            <comment id="134568" author="61cd0ca0bce5e00069e98be7" created="Wed, 7 Jun 2017 06:32:31 +0000"  >&lt;p&gt;Regarding actually &quot;fixing&quot;, there are various similar open issues at raml-for-jax-rs. It might assist to add another bug report for this specific case.&lt;/p&gt;</comment>
                                                            <comment id="134569" author="712020:32bb56ac-50e7-4787-b4af-ed3089d9401c" created="Wed, 7 Jun 2017 06:33:25 +0000"  >&lt;blockquote&gt;&lt;p&gt;I enhanced the note in raml-module-builder/README.md to advise about the placement of those directories.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;thanks!&lt;/p&gt;</comment>
                                                            <comment id="134570" author="61cd0ca0bce5e00069e98be7" created="Wed, 7 Jun 2017 06:33:33 +0000"  >&lt;p&gt;For &quot;raml-module-builder&quot; i have done this:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt; 
git mv domain-models-api-interfaces/src/main/resources/raml domain-models-api-interfaces/raml
git mv raml-util domain-models-api-interfaces/raml-util
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The RMB does build with success. Using that snapshot in mod-inventory-storage runs its tests with success.&lt;/p&gt;

&lt;p&gt;Now ready in branch &lt;a href=&quot;https://github.com/folio-org/raml-module-builder/tree/folio-573-rmb-30-filename-schema-key&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-573-rmb-30-filename-schema-key&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; class=&quot;user-hover&quot; rel=&quot;712020:32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; data-account-id=&quot;712020:32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; accountid=&quot;712020:32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; rel=&quot;noreferrer&quot;&gt;shale99&lt;/a&gt;: Are you happy with that directory arrangement?&lt;/p&gt;</comment>
                                                            <comment id="134571" author="712020:32bb56ac-50e7-4787-b4af-ed3089d9401c" created="Wed, 7 Jun 2017 06:42:04 +0000"  >&lt;p&gt;yea, that works for me&lt;/p&gt;</comment>
                                                            <comment id="134572" author="61cd0ca0bce5e00069e98be7" created="Wed, 7 Jun 2017 06:44:03 +0000"  >&lt;p&gt;Beaut. I will go ahead.&lt;/p&gt;</comment>
                                                            <comment id="134573" author="61cd0ca0bce5e00069e98be7" created="Wed, 7 Jun 2017 07:08:13 +0000"  >&lt;p&gt;Drat. It was fine here on macOS with its &quot;tmp&quot; filesystem. However following the merge of &lt;a href=&quot;https://github.com/folio-org/raml-module-builder/pull/85&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull/85&lt;/a&gt; it failed on the build on the server.&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:java (generate_interfaces) on project domain-models-api-interfaces: An exception occured &lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; executing the Java class. &lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;: InvocationTargetException: Directory &lt;span class=&quot;code-quote&quot;&gt;&apos;/tmp/1496818545170-0/../../raml-util/schemas&apos;&lt;/span&gt; could not be created
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I reverted the PR merge.&lt;/p&gt;</comment>
                                                            <comment id="134574" author="61cd0ca0bce5e00069e98be7" created="Fri, 9 Jun 2017 09:29:33 +0000"  >&lt;p&gt;Beware too many dotdots.&lt;/p&gt;

&lt;p&gt;Putting the &quot;raml-util&quot; git submodule directly inside the &quot;raml&quot; directory does work for the &quot;raml-module-builder&quot; repo, i.e. at raml-module-builder/domain-models-api-interfaces/src/main/resources/raml/raml-util/&lt;/p&gt;

&lt;p&gt;See branch &lt;a href=&quot;https://github.com/folio-org/raml-module-builder/tree/folio-573-rmb-30-filename-schema-key-2&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;folio-573-rmb-30-filename-schema-key-2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The build is successful on both macOS and on Ubuntu Linux.&lt;/p&gt;</comment>
                                                            <comment id="134575" author="61cd0ca0bce5e00069e98be7" created="Fri, 16 Jun 2017 07:57:15 +0000"  >&lt;p&gt;I did various testing for the location of the &quot;raml-util&quot; directory, for RMB&apos;s own RAMLs and for mod-configuration. For some it did work on macOS but not on Linux. (See attached results.txt)&lt;/p&gt;

&lt;p&gt;Summary: If there are schema files that use $ref to another schema in raml-util, then that &quot;raml-util&quot; is best placed inside the &quot;ramls&quot; directory. In the RAML file, use the filename as the schema key name (not relative pathname).&lt;/p&gt;</comment>
                                                            <comment id="134576" author="61cd0ca0bce5e00069e98be7" created="Mon, 19 Jun 2017 06:00:21 +0000"  >&lt;p&gt;After that &quot;careful&quot; testing (working on both macOS and Ubuntu Linux) when i merged the &lt;a href=&quot;https://github.com/folio-org/raml-module-builder/tree/folio-573-rmb-30-filename-schema-key-3&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;branch&lt;/a&gt; (&lt;a href=&quot;https://github.com/folio-org/raml-module-builder/pull/87&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull/87&lt;/a&gt;), it then failed on our Jenkins server:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
java.lang.IllegalArgumentException: Unrecognised URI, can&apos;t resolve &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt;: file:/tmp/raml-util/schemas/parameters.schema
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The reason that it seemed to work locally on Linux, was that there was a left-over old &quot;/tmp/raml-util&quot; from a previous failed build.&lt;/p&gt;

&lt;p&gt;Sorry for the noise.&lt;/p&gt;</comment>
                                                            <comment id="134577" author="61cd0ca0bce5e00069e98be7" created="Mon, 19 Jun 2017 08:43:09 +0000"  >&lt;p&gt;After a tweak similar to what was suggested above, the branch now does work:&lt;/p&gt;

&lt;p&gt;Use relative pathname as schema key name in RAML. &#8233;This is the relative pathname that is used as the $ref in the parent schema file.&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
raml-module-builder/domain-models-api-interfaces/raml/schemas/
raml-module-builder/domain-models-api-interfaces/raml/raml-util/schemas/

in raml-module-builder/domain-models-api-interfaces/raml/schemas/job.schema
  &lt;span class=&quot;code-quote&quot;&gt;&quot;$ref&quot;&lt;/span&gt; : &lt;span class=&quot;code-quote&quot;&gt;&quot;../raml-util/schemas/parameters.schema&quot;&lt;/span&gt;

in raml-module-builder/domain-models-api-interfaces/raml/jobs.raml
  - ../raml-util/schemas/parameters.schema: !include raml-util/schemas/parameters.schema
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;During the compile phase, on Linux that is created at &quot;/tmp/raml-util&quot;.&lt;/p&gt;</comment>
                                                            <comment id="134578" author="61cd0ca0bce5e00069e98be7" created="Wed, 21 Jun 2017 04:06:58 +0000"  >&lt;p&gt;It works in that specific situation. During the compilation phase, either raml-for-jax-rs (or perhaps jsonschema2pojo) creates a temporary directory and copies the schema files to it. If a schema has $ref with relative path to another schema (e.g. ../raml-util/schema/...) with only one set of dot-dots then they are copied to &quot;/tmp/raml-util&quot; and the build is successful. Of course more than one set, and it will not.&lt;/p&gt;

&lt;p&gt;(Perhaps raml-for-jax-rs version 2 has better handling. 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-523&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-523&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Decide if FOLIO should enable using RAML 1.0&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-523
        &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;
)&lt;/p&gt;

&lt;p&gt;As our raml-util now has schema files which refer to other files in that area, then compiling say mod-users-bl puts those schema in &quot;/tmp/mod-login&quot; and friends.&lt;/p&gt;

&lt;p&gt;A successful build does remove its temp space. However those extraneous directories do remain.&lt;/p&gt;

&lt;p&gt;That seems fragile, e.g. perhaps that could get confused by a build process of another module.&lt;/p&gt;</comment>
                                                            <comment id="134579" author="61cd0ca0bce5e00069e98be7" created="Wed, 21 Jun 2017 04:07:23 +0000"  >&lt;p&gt;A potential solution could be a shared &quot;schema-util&quot; inside each &quot;schemas&quot; directory.&lt;/p&gt;

&lt;p&gt;However that will be tortuous in the raml-util/schemas/mod-* directories.&lt;/p&gt;</comment>
                                                            <comment id="134580" author="61cd0ca0bce5e00069e98be7" created="Thu, 22 Jun 2017 06:52:06 +0000"  >&lt;p&gt;Ah, of course, there is a solution. For any schema file that needs to refer to another schema file that is outside of its space, then move that parent schema file up to a higher level directory. This does work for both of our current complex ones, i.e. raml-module-builder own ramls and for mod-users-bl.&lt;/p&gt;</comment>
                                                            <comment id="134581" author="61cd0ca0bce5e00069e98be7" created="Fri, 30 Jun 2017 07:03:47 +0000"  >&lt;p&gt;Added &lt;a href=&quot;https://github.com/folio-org/raml-module-builder/blob/master/README.md#step-6-design-the-raml-files&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;documentation&lt;/a&gt; to RMB to explain the best location of the shared raml-util and using $ref in schema.&lt;/p&gt;

&lt;p&gt;Followed that for the raml-module-builder&apos;s own docs and for mod-configuration.&lt;br/&gt;
(Now moving on to the others.)&lt;/p&gt;

&lt;p&gt;For the shared ones in raml-util mod-users-bl (not yet done) its schema files need to move up one level, i.e.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
cd folio-org/raml
mv schemas/mod-users-bl/*.json schemas
and adjust paths in ramls/schema.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;(&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c38e8d616ac1e4f7cbc660a&quot; class=&quot;user-hover&quot; rel=&quot;5c38e8d616ac1e4f7cbc660a&quot; data-account-id=&quot;5c38e8d616ac1e4f7cbc660a&quot; accountid=&quot;5c38e8d616ac1e4f7cbc660a&quot; rel=&quot;noreferrer&quot;&gt;Kurt Nordstrom&lt;/a&gt;, &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; class=&quot;user-hover&quot; rel=&quot;712020:32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; data-account-id=&quot;712020:32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; accountid=&quot;712020:32bb56ac-50e7-4787-b4af-ed3089d9401c&quot; rel=&quot;noreferrer&quot;&gt;shale99&lt;/a&gt;)&lt;/p&gt;</comment>
                                                            <comment id="134582" author="61cd0ca0bce5e00069e98be7" created="Mon, 17 Jul 2017 07:20:30 +0000"  >&lt;p&gt;There is &lt;a href=&quot;https://github.com/folio-org/raml/pull/22&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull/22&lt;/a&gt; in folio-org/raml and i have success building mod-users-bl with that. &lt;/p&gt;</comment>
                                                            <comment id="134583" author="61cd0ca0bce5e00069e98be7" created="Wed, 9 Aug 2017 06:16:31 +0000"  >&lt;p&gt;Closed.&lt;/p&gt;

&lt;p&gt;All necessary mod-* repositories now have &quot;raml-util&quot; inside the &quot;ramls&quot; directory. See RMB README.&lt;/p&gt;

&lt;p&gt;(As a separate issue, the user-related mod-* repositories had their RAMLs moved to raml-util proper.)&lt;/p&gt;</comment>
                                                            <comment id="134584" author="61cd0ca0bce5e00069e98be7" created="Tue, 22 Aug 2017 01:37:45 +0000"  >&lt;p&gt;There is an example for mod-circulation-storage needing to link to shared schema in raml-util.&lt;br/&gt;
Do: &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;cd ramls; grep \$ref *.json&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt; and see the corresponding RAML files.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="80194">FOLIO-592</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="79341">FOLIO-614</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80284">FOLIO-573</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56707">RMB-50</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzxonj:</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>Thu, 1 Jun 2017 20:03:51 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>