<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.Shkpostityyli17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FI" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">We are making good progress on the 2.0 release with changes being merged now to the develop branch in Git rather than having a separate v2.0 branch we started out with. You can “see” the progress in dev.oskari.org with
the quotes signifying that you really shouldn’t be seeing that many differences really. What is being done is mostly reflected on the server side with updated components all over. There are modifications that need to be done on Oskari-based applications because
the libraries we use have changes in Java packages and in some cases the API. A friendly reminder: you will need to upgrade an existing Oskari instance to version 1.56.0 before you can upgrade to 2.0. You can see the changes required for applications on the
sample-server-extension repository: </span><a href="https://github.com/oskariorg/sample-server-extension/milestone/5?closed=1"><span lang="EN-US">https://github.com/oskariorg/sample-server-extension/milestone/5?closed=1</span></a>
<span lang="EN-US">(also Geotools/JTS upgrade requires some changes if you use those in application specific code).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">That being said we are using this opportunity about knowing the update path and requirements for changes to apps on the server-side due to library updates to clean up some older dependencies, code and migrations to give
more room to work with in the future. For example we have (finally) updated the last of the services in oskari-server to use Mybatis instead of Ibatis for database operations and we can now drop Ibatis as a dependency. If you use it in your applications you
can probably just add it as a dependency in your app and everything should work. Reseting migrations for core Oskari module also allows us to rename the database tables to start with oskari_-prefix instead of the legacy portti_-prefix or no prefix. On this
topic I would like an opinion if anyone is using the portti_keyword tables in Oskari database? They are not really used currently and we would like to drop the tables and services related to it because of that.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">On another note I’m considering renaming all the Maven artifacts from the current groupId fi.nls.oskari to org.oskari (and perhaps some artifactId:s to match the folder they are stored in). This will require some changes
in the pom.xml files on applications as well but not too much I think. Is someone strongly (or mildly) against this renaming? We have started using it on the more recent modules.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> Sami<o:p></o:p></span></p>
</div>
</body>
</html>