<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hum... Gerrit uses a lot submodules in his/their product, with
success. In my opinion, it's not enough. There is nothing that
avoid you to set your submodule reference to a branch under
developement.</p>
<p>I prefer using a dependency mecanism, and a release system. Once
a library is validated, you produce a release, wich is a
deliverable recorded into an artifact repository. Your programs
declare a dependency to this artifact, and it's resolved
dynamically, and recursively. At least two talks exists on this,
one from [1]l-acoustics, the other from [2]ELS, the first one on a
document point-of-view, the second one on a code point-of-view.<br>
</p>
<p>Building a deliverable, and storing it into an artifact
repository allows you to add a lot of checks in the build process,
[3]unit-tests, [4]quality-gate, and so on... and grows your
libraries to a higher level. You can do the same with git
submodules for dependency resolution, but you miss the whole
Continuous Integration process.</p>
<p>You'd better build your framework, deploy it to an artifact
repository (a basic file web server), and then configure oXygen to
get this framework from this location.<br>
</p>
<p>Hope this helps,<br>
Christophe<br>
</p>
<p>[1]
<a class="moz-txt-link-freetext" href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#DITA_gradle_and_git">https://www.oxygenxml.com/events/2018/dita-ot_day.html#DITA_gradle_and_git</a><br>
[2] <a class="moz-txt-link-freetext" href="https://www.xmlprague.cz/day2-2018/#cm">https://www.xmlprague.cz/day2-2018/#cm</a><br>
[3] <a class="moz-txt-link-freetext" href="https://github.com/xspec/xspec/wiki">https://github.com/xspec/xspec/wiki</a><br>
[4] <a class="moz-txt-link-freetext" href="https://www.xmlprague.cz/day3-2019/#sonar">https://www.xmlprague.cz/day3-2019/#sonar</a><br>
</p>
<div class="moz-cite-prefix">Le 09/11/2020 à 21:02, Wendell Piez a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAAO_-xxSvajLVVv_XQmwDVDUPbYyCJS9Ac9X6BN2TXHWzBW8jw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">oXygen friends,
<div><br>
</div>
<div>Frameworks in oXygen make up a fantastic feature set. Git
is a very nice way to manage versioning in a distributed way.</div>
<div><br>
</div>
<div>I am looking at making a framework that uses libraries from
Github. Presently I am thinking of pointing to those libraries
from my framework as git submodules and maintaining them that
way.</div>
<div><br>
</div>
<div>Is this a bad idea? If my framework is eventually
distributed from Github, is this likely to be nice, or not so
nice?</div>
<div><br>
</div>
<div>Thanks - a git user for years now, but still a novice --</div>
<div>Cheers, Wendell</div>
<div>
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">...Wendell Piez...
...wendell -at- nist -dot- gov...<br>
...wendellpiez.com... ...pellucidliterature.org...
...pausepress.org...<br>
...<a href="http://github.com/wendellpiez." target="_blank"
moz-do-not-send="true">github.com/wendellpiez.</a>..
...gitlab.coko.foundation/wendell... </div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
oXygen-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:oXygen-user@oxygenxml.com">oXygen-user@oxygenxml.com</a>
<a class="moz-txt-link-freetext" href="https://www.oxygenxml.com/mailman/listinfo/oxygen-user">https://www.oxygenxml.com/mailman/listinfo/oxygen-user</a>
</pre>
</blockquote>
</body>
</html>