Skip to content

Commit e9856a4

Browse files
authored
Merge pull request #1249 from eclipse/mcj/chore/tag134
chore(rel): changing files for tagging 13.4 tested-by:travis
2 parents 83e9871 + ba92db2 commit e9856a4

File tree

3 files changed

+62
-9
lines changed

3 files changed

+62
-9
lines changed

CHANGELOG.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,58 @@ This is the changelog file of the sw360 project. It starts with the first releas
44

55
https://github.com/sw360/sw360portal/releases
66

7+
## sw360-13.4.0-M1
8+
9+
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.
10+
11+
This release provides also features, however, some smaller news are there, for example, new REST endpoints or new functions in the UI.
12+
13+
### Migrations
14+
15+
For this version, no database migration is necessary.
16+
17+
### Credits
18+
19+
The following github users have contributed to the source code since the last release (in alphabetical order):
20+
21+
```
22+
abdul.kapti@siemens-healthineers.com
23+
jaideep.palit@siemens.com
24+
kumar.ravindra@siemens.com
25+
michael.c.jaeger@siemens.com
26+
nam1.nguyenphuong@toshiba.co.jp
27+
smruti.sahoo@siemens.com
28+
yosuke.yamada.no@hitachi.com
29+
```
30+
31+
Please note that also many other persons usually contribute to the project with reviews, testing, documentations, conversations or presentations.
32+
33+
### Features
34+
35+
* `3089008c` feat(rest): Support map of release id to usage as request body in addition to previous array of release id for
36+
* `df2f6dad` feat(VirusScanSchedulerService): Scheduler Service for deletion of attachment from local FS
37+
* `276650a9` feat(ObligationHelpTextforProject): Provide the different obligation help text from the Projects Screen
38+
* `ec37c480` feat(moderations): Pagination in requests tab for moderations
39+
* `0d739556` feat(obligationlevelhelptext):Provide info text for different obligation Level
40+
* `83282112` feat(ProjectUI): feature to add License Info to linked releases from License Clearing tab
41+
* `afdac6f5` feat(ProjectVersion): Added the project version in the search Project filter
42+
* `4b1a1b3f` feat(ProjectUI): Fixed copy of projects removes linked subprojects
43+
* `d44b63ba` feat(ProjectGroupFilter):Filter the projects in Advanced Search based on Projects Group
44+
* `4140a8ad` feat(rest): Added new endpoints to update attachment info of Project, Component, Release
45+
* `96443359` feat(rest): Added rest endpoint to update project-release-relationship information of linked releases in a project
46+
* `756190b4` feat(ProjectUI): feature to display the source files linked with the licenses
47+
48+
### Corrections
49+
50+
* `ef27ad5d` fix(rest): Auto-set release clearing state
51+
* `debfe70d` Fix: Rest interface can not handle licenses which do not exist in the database #534
52+
* `2d56d0b4` fix: Wrong error handling when deleting multiple components #851 nam1.nguyenphuong@toshiba.co.jp
53+
* `9a31049d` fix(script): Build failure of sw360dev.Dockerfile and compileWithDocker.sh
54+
* `9f32b882` fix(readmeossdownload): Null pointer while downloading readme_oss
55+
* `f0aa5cbf` fix(ui/rest): Issue fetching releases by external ids and null value in external id breaks the release view
56+
* `baaa9f42` fix(search): search releases while linking to project
57+
* `00083ea8` fix(backend): Issues with boolean and timestamp field deserialization and get attachment info REST
58+
759
## sw360-13.3.0-M1
860

961
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.).

README.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
[![Build Status](https://travis-ci.org/eclipse/sw360.svg?branch=master)](https://travis-ci.org/eclipse/sw360)
33
[![Slack Channel](https://img.shields.io/badge/slack-sw360chat-blue.svg?longCache=true&logo=slack)](https://join.slack.com/t/sw360chat/shared_invite/enQtNzg5NDQxMTQyNjA5LThiMjBlNTRmOWI0ZjJhYjc0OTk3ODM4MjBmOGRhMWRmN2QzOGVmMzQwYzAzN2JkMmVkZTI1ZjRhNmJlNTY4ZGI)
44
[![Changelog](https://badgen.net/badge/changelog/%E2%98%85/blue)](https://github.com/eclipse/sw360/blob/master/CHANGELOG.md)
5-
[![version](https://img.shields.io/badge/version-13.0.0-blue)](https://github.com/eclipse/sw360/releases/tag/sw360-13.0.0-M1)
5+
[![version](https://img.shields.io/badge/version-13.4.0-blue)](https://github.com/eclipse/sw360/releases/tag/sw360-13.4.0-M1)
66

77
### SW360 Portal
88

@@ -23,7 +23,7 @@ It is comprised of one frontend (portal) part, backend (services) part and addit
2323
* Database: we store software components and metadata about them in CouchDB.
2424
* Rest: this REST API provides access to project resources for external integration.
2525

26-
The reference platform is the Ubuntu server 18.04 (which is an LTS version). However, it runs well on other OSes (see below).
26+
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).
2727

2828
### Project structure
2929

@@ -38,8 +38,8 @@ This is a multi module maven file. please consider that we have the following mo
3838
### Required software
3939

4040
* Java 11, tested with OpenJDK
41-
* CouchDB, at least 2.1 (tested, may work with other releases of CouchDB as well)
42-
* Liferay Portal CE 7.3.3 GA4
41+
* CouchDB, at least 2.1 (tested, may work with other releases of CouchDB as well), runs best with 3.1.1
42+
* Liferay Portal CE 7.3.3 GA4 or 7.3.4 GA5
4343
* Apache Tomcat 9.0.X (which is bundled with Liferay)
4444
* couchdb-lucene for search, please refer to installation details in the wiki, because a patch is required
4545

@@ -51,6 +51,7 @@ In addition, the Liferay instance must provide the following dependecies via OSG
5151
* Apache Commons IO 2.6
5252
* Apache Commons Lang 2.4
5353
* Apache Commons Logging 1.2
54+
* Apache Commons Compress 1.20
5455
* Google Gson 2.8.5
5556
* Google Guava 21.0
5657
* Jackson Annotations 2.9.8
@@ -68,7 +69,7 @@ http://maven.apache.org/download.html#Installation
6869

6970
Then, you must install Apache Tomcat, CouchDB. And, Java of course.
7071

71-
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.
72+
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.
7273

7374
### PROBLEMS
7475

@@ -119,18 +120,18 @@ You may also specify the paths using these properties:
119120
- backend artifacts: `backend.deploy.dir`
120121
- rest artifacts: `rest.deploy.dir`
121122
- liferay artifacts (frontend, libraries): `liferay.deploy.dir`
122-
Be aware that you have to deploy the liferay artifacts in the Liferay auto-deploy folder.
123+
Be aware that you have to deploy the Liferay artifacts in the Liferay auto-deploy folder.
123124
On the other hand you must not deploy rest and backend artifacts to the auto-deploy folder.
124125

125-
**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:
126+
**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:
126127

127128
```
128129
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
129130
```
130131

131132
### Liferay Configuration
132133

133-
You should provide below property configuration based on his/her liferay deployment
134+
You should provide below property configuration based on his/her Liferay deployment
134135
environment as found in the master pom.xml file.
135136

136137
Please note that you should run the Liferay installation procedures as found on the

pom.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@
5151
<!-- note that 6.1.0-SNAPSHOT relates to 6.0.${patchlevel} -->
5252
<!-- pls see also the profile cli -->
5353
<revision>13.4.${patchlevel}</revision>
54-
<patchlevel>0-SNAPSHOT</patchlevel>
54+
<patchlevel>0</patchlevel>
5555
<java.version>11</java.version>
5656
<ektorp.version>1.5.0</ektorp.version>
5757
<thrift.version>0.13.0</thrift.version>

0 commit comments

Comments
 (0)