diff --git a/CHANGELOG.md b/CHANGELOG.md index a6773b9f11..e4c9d377c5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,58 @@ This is the changelog file of the sw360 project. It starts with the first releas https://github.com/sw360/sw360portal/releases +## sw360-13.4.0-M1 + +This tag covers many corrections and bug fixes after the 13.3 release. Th eproductive use of 13.3 has revealed a number of issues resulting from the big persistence layer switch. + +This release provides also features, however, some smaller news are there, for example, new REST endpoints or new functions in the UI. + +### Migrations + +For this version, no database migration is necessary. + +### Credits + +The following github users have contributed to the source code since the last release (in alphabetical order): + +``` +abdul.kapti@siemens-healthineers.com +jaideep.palit@siemens.com +kumar.ravindra@siemens.com +michael.c.jaeger@siemens.com +nam1.nguyenphuong@toshiba.co.jp +smruti.sahoo@siemens.com +yosuke.yamada.no@hitachi.com +``` + +Please note that also many other persons usually contribute to the project with reviews, testing, documentations, conversations or presentations. + +### Features + +* `3089008c` feat(rest): Support map of release id to usage as request body in addition to previous array of release id for +* `df2f6dad` feat(VirusScanSchedulerService): Scheduler Service for deletion of attachment from local FS +* `276650a9` feat(ObligationHelpTextforProject): Provide the different obligation help text from the Projects Screen +* `ec37c480` feat(moderations): Pagination in requests tab for moderations +* `0d739556` feat(obligationlevelhelptext):Provide info text for different obligation Level +* `83282112` feat(ProjectUI): feature to add License Info to linked releases from License Clearing tab +* `afdac6f5` feat(ProjectVersion): Added the project version in the search Project filter +* `4b1a1b3f` feat(ProjectUI): Fixed copy of projects removes linked subprojects +* `d44b63ba` feat(ProjectGroupFilter):Filter the projects in Advanced Search based on Projects Group +* `4140a8ad` feat(rest): Added new endpoints to update attachment info of Project, Component, Release +* `96443359` feat(rest): Added rest endpoint to update project-release-relationship information of linked releases in a project +* `756190b4` feat(ProjectUI): feature to display the source files linked with the licenses + +### Corrections + +* `ef27ad5d` fix(rest): Auto-set release clearing state +* `debfe70d` Fix: Rest interface can not handle licenses which do not exist in the database #534 +* `2d56d0b4` fix: Wrong error handling when deleting multiple components #851 nam1.nguyenphuong@toshiba.co.jp +* `9a31049d` fix(script): Build failure of sw360dev.Dockerfile and compileWithDocker.sh +* `9f32b882` fix(readmeossdownload): Null pointer while downloading readme_oss +* `f0aa5cbf` fix(ui/rest): Issue fetching releases by external ids and null value in external id breaks the release view +* `baaa9f42` fix(search): search releases while linking to project +* `00083ea8` fix(backend): Issues with boolean and timestamp field deserialization and get attachment info REST + ## sw360-13.3.0-M1 This tag is applied to have the migration from cloudant to ektorp in one single step. Ektorp is a Java library which provides an object oriented interface to the (REST-based) access to couchdb. It has been used in sw360 from day 1. Now we concluded to replace ektorp: it does not support paging; having our server growing larger and lager and serving more and more users, receiving results sets from a couchdb view without paging is a pain. And it did not look like it will be supported, because the ektorp project looks calm now (last commit to master in 2017). Among the available options for replacing ektorp, we choose the java-client from the open source project cloudant (version 2.19.1, see https://github.com/cloudant/java-cloudant). It supports paging and offers potentially other interesting features (caching, compatibility with MongoDB, etc.). diff --git a/README.md b/README.md index 956c99d44c..dee5d58f4d 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ [![Build Status](https://travis-ci.org/eclipse/sw360.svg?branch=master)](https://travis-ci.org/eclipse/sw360) [![Slack Channel](https://img.shields.io/badge/slack-sw360chat-blue.svg?longCache=true&logo=slack)](https://join.slack.com/t/sw360chat/shared_invite/enQtNzg5NDQxMTQyNjA5LThiMjBlNTRmOWI0ZjJhYjc0OTk3ODM4MjBmOGRhMWRmN2QzOGVmMzQwYzAzN2JkMmVkZTI1ZjRhNmJlNTY4ZGI) [![Changelog](https://badgen.net/badge/changelog/%E2%98%85/blue)](https://github.com/eclipse/sw360/blob/master/CHANGELOG.md) -[![version](https://img.shields.io/badge/version-13.0.0-blue)](https://github.com/eclipse/sw360/releases/tag/sw360-13.0.0-M1) +[![version](https://img.shields.io/badge/version-13.4.0-blue)](https://github.com/eclipse/sw360/releases/tag/sw360-13.4.0-M1) ### SW360 Portal @@ -23,7 +23,7 @@ It is comprised of one frontend (portal) part, backend (services) part and addit * Database: we store software components and metadata about them in CouchDB. * Rest: this REST API provides access to project resources for external integration. -The reference platform is the Ubuntu server 18.04 (which is an LTS version). However, it runs well on other OSes (see below). +The reference platform is the Ubuntu server 20.04 (which is an LTS version) as it is supported in sw360vagrant. However, it runs well on other OSes (see below). ### Project structure @@ -38,8 +38,8 @@ This is a multi module maven file. please consider that we have the following mo ### Required software * Java 11, tested with OpenJDK -* CouchDB, at least 2.1 (tested, may work with other releases of CouchDB as well) -* Liferay Portal CE 7.3.3 GA4 +* CouchDB, at least 2.1 (tested, may work with other releases of CouchDB as well), runs best with 3.1.1 +* Liferay Portal CE 7.3.3 GA4 or 7.3.4 GA5 * Apache Tomcat 9.0.X (which is bundled with Liferay) * couchdb-lucene for search, please refer to installation details in the wiki, because a patch is required @@ -51,6 +51,7 @@ In addition, the Liferay instance must provide the following dependecies via OSG * Apache Commons IO 2.6 * Apache Commons Lang 2.4 * Apache Commons Logging 1.2 +* Apache Commons Compress 1.20 * Google Gson 2.8.5 * Google Guava 21.0 * Jackson Annotations 2.9.8 @@ -68,7 +69,7 @@ http://maven.apache.org/download.html#Installation Then, you must install Apache Tomcat, CouchDB. And, Java of course. -The software is tested with with debian 8, debian 9, ubuntu 16.04, ubuntu 18.04, macosx 10.8 - 10.14. We run Liferay with PostgreSQL 9.X or 10 as the Liferay CE requires, but HSQL (provided with the liferay bundle) runs also OK. +The software is tested with with debian 8, debian 9, ubuntu 16.04, ubuntu 18.04, ubuntu 20.04 macosx 10.8 - 10.15. We run Liferay with PostgreSQL 9.X or 10 as the Liferay CE requires, but HSQL (provided with the liferay bundle) runs also OK. ### PROBLEMS @@ -119,10 +120,10 @@ You may also specify the paths using these properties: - backend artifacts: `backend.deploy.dir` - rest artifacts: `rest.deploy.dir` - liferay artifacts (frontend, libraries): `liferay.deploy.dir` -Be aware that you have to deploy the liferay artifacts in the Liferay auto-deploy folder. +Be aware that you have to deploy the Liferay artifacts in the Liferay auto-deploy folder. On the other hand you must not deploy rest and backend artifacts to the auto-deploy folder. -**Note:** the test framework for the REST API needs the tests running in order to generate the API documentation. So, for building the REST API artefacts, please switch in the rest subprojects and execute: +**Note:** the test framework for the REST API needs the tests running in order to generate the API documentation. So, for building the REST API artefacts, please switch in the rest sub projects and execute: ``` mvn package -P deploy -Dbase.deploy.dir=. -Dliferay.deploy.dir=${LIFERAY_INSTALL}/deploy -Dbackend.deploy.dir=${LIFERAY_INSTALL}/tomcat-9.0.17/webapps -Drest.deploy.dir=${LIFERAY_INSTALL}/tomcat-9.0.17/webapps @@ -130,7 +131,7 @@ mvn package -P deploy -Dbase.deploy.dir=. -Dliferay.deploy.dir=${LIFERAY_INSTALL ### Liferay Configuration -You should provide below property configuration based on his/her liferay deployment +You should provide below property configuration based on his/her Liferay deployment environment as found in the master pom.xml file. Please note that you should run the Liferay installation procedures as found on the diff --git a/pom.xml b/pom.xml index 775f28c235..b0340c08d3 100644 --- a/pom.xml +++ b/pom.xml @@ -51,7 +51,7 @@ 13.4.${patchlevel} - 0-SNAPSHOT + 0 11 1.5.0 0.13.0