<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Another way to deal with this might be
to unjar the files ourselves at startup. The files could live in
the same place they live today. <br>
<br>
We would just have keep track of versioning. If a newer version
of the theme is installed we overwrite the old version in
standlone/configuration/themes. Of course, if the theme has been
modified by the user we wouldn't overwrite, but instead just unjar
to another location.<br>
<br>
On 2/12/2016 9:44 AM, Stian Thorgersen wrote:<br>
</div>
<blockquote
cite="mid:CAJgngAdaa0OvWtXTD7nUGXsE5S7zF-C=zKUSEe3vPNgM75W=Sg@mail.gmail.com"
type="cite">
<p dir="ltr">Currently we include built-in themes in the themes
jar as well as extracted to standalone/configuration/themes. We
have to remove the extracted files.</p>
<p dir="ltr">This is due to patching. The patching tools only
supports patching modules, not files. If we need to patch the
theme templates (quite likely we will) we can then only patch
the jar. As the extracted themes override the jar it won't work
unless we remove them.</p>
<p dir="ltr">The main problem with removing the extracted files is
that they are useful for someone that needs to modify the
templates. I think the best would just be to give people
instructions on how to extract these from the jar. It's just a
zip after all.</p>
<p dir="ltr">Thoughts??</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></pre>
</blockquote>
<br>
</body>
</html>