Releases: eclipse-sw360/sw360
sw360-8.1.0-M1
A version upgrade is justified, because of a number of new features have been integrated: FOSSology scans can be now triggered over the SW360 REST API. By this feature, an upload, for example from sw360antenna, could also trigger the FOSSology scan right away. It requires FOSSology being integrated with sw360.
Another new endpoint is the query for SHA1 values of a file to check if that attachment is actually already found at some release. With this endpoint, one would not need to search for release names and version before making a new entry, but just search for the source code attachment using its SHA1 value to check if an upload has been performed already.
A third new feature is the ability to agree on a clearing job for the software components of a project or product. A project owner can now send to a clearing expert a request to perform the clearing of software components right from SW360.
Features
bb9f2bafeat(REST): Trigger FOSSology process and check status99e23dcfeat(ObligationUI): Added new status fields for Obligationd025c4afeat(rest): Attachement sha1 improvement9a53e7bfeat(ProjectUI): Project Clearing Report
Corrections
7bd1fd5fix(UI/REST): Remove Trailing and leading whitespace for all fields in component, release and projecta2a4b16fix(components): components listing limited to 200 entries both in UI and excel spreadseet0de1db1fix(vulerability): vulnerability view breaks at backslash in description83e6f28fix(REST): Updated upload attachment documentation
Chores
1fc2e0bAdd pull request tempalte and .github folder (11 days ago) [email protected]
sw360-8.0.1-M1
There is some small but very relevant bug in 8.0.0, which prevents the user from creating records in special conditions. Therefore, version 8.0.0 is deprecated and replaced by version 8.0.1.
Corrections
c20fa46fix(component/release): Add component and release error in UI
sw360-8.0.0-M1
It is not really that we like to ignore minor releases, but release 8 is coming because:
- changes in the DB for external id handling, pls see migration script:
scripts/migrations/016_update_byExternalIds_component_view.py - changes in the Thrift API, allowing for SPDX BOM import pls see:
libraries/lib-datahandler/src/main/thrift/projects.thrift
And as a larger, very important feature, there is the SPDX BOM import there in a first version, adding two modes:
- Import a project with linked releases from a SPDX BOM file
- Import a list of components and releases from a SPDX BOM file
Moreover a very important feature or fix has been provided for ensuring that malformed REST requests do not lead to failure in the application. Previously, providing wrong typed references (for example: linking releases to a project) was accepted by the application and can lead to malfunction then. The following list lists the detailed changes since 7.0.1:
New Features
712ba79feat(rest): validate the linked document ids in the payload before updating it in the DBf90fcc4feat(bomImport): implement SPDX BOM import for projects and releases24999cefeat(AddProjectReleaseRelation): add a project release relation for source code snippets48de678feat(REST): Patch Releases to Project
Corrections
d34d454fix(ReleaseUI): fixed reload report in FOSSology Process336534afix(REST): fixed search component by external idbc28c54fix(EditReleaseUI): Fixed missing functionality of button to delete release to release relatione437a5bfix(spreadsheet-export): fixed the secuence of values based on headers4c0d5c9fix(thrift): add should return ID on duplicate1d65e70fix(html): fix minor bugs and stylingb7a83d6fix(ui): saving attachment usage issue for source code bundle and others
sw360-7.0.1-M1
After tagging 7.0.0, we found two bugs to be corrected to provide a sound SW360. Therefore, here a new tagged version of sw360. Everyone should use 7.0.1-M1 instead of 7.0.0.
Adding rolling version since last tag will prepare automated tagging with incrementing patch level, retaining manual tagging for major and minor version only.
Corrections
0dcd109fix(ProjectUI: fixed blank / non-responsive screen on projectda677b5fix(ui): fix issue #762
Infrastructure
a37e24dchore(readme): adding some more badgesf1a7c63feat(chore): adding rolling versions based on commit count
sw360-7.0.0-M1
Unfortunately this release has a bug, please consider the previous release or wait for 7.0.1.
The main reason for release version 7 is to have the license upgrade from EPL-1.0 to EPL-2.0. All contributing parties have submitted their consent by e-mail and on most cases also approved the referring pull request (#756).
Another change which justifies a major version jump is the required view update in the couchdb. Please see https://github.com/eclipse/sw360/blob/master/scripts/migrations/README.md for more information when migrating from an older version. The view update allows users to configure the My Projects portlet.
New Features
9b92795feat(docs): relicensing from EPL-1.0 to EPL-2.066a4126feat(Component/ReleaseUI): Added button to remove selected vendor for component and release860aa3efeat(ProjectMigration): script to migrate a project field to new valuebd99641feat(REST): Add parameter to GET release by name322c45dfeat(WelcomePageUI): display configurable content for guidelines on welcome pageabac231feat(fossology-pull-report): Added the button to pull the already generated report from fossology062c899feat(HomePageUI): Listing of MyProjects is made configurable9849cb0feat(licenseinfo): Added filter to exclude releases based on selected relationship
Corrections
2a52475fix(ProjectUI): Show proper error msg ,when loading of project fails due to access or dependency not found752bd78fix(ProjectUI): fixed 'Project is temporarily unavailable' issue due to obligation featureb32afd5fix(ReleaseUI/REST): prevent cyclic link in release0d2647dfix(licenseinfo): White page while downloading license disclosure
Infrastructure
d22aaaftest: add script to start temporary couchdb with dockerdf54014chore(cleanup): drop unused and outdated code related to the codescoop integration
sw360-6.0.0-M1
This release covers as the biggest change the new integration with the FOSSology REST API. It replaces the previous integration using an ssh login. It requires a migration of the couchdb database. More information about the scripts can be found in scripts/migrations/README.md.
Apart from changing the integration with FOSSology from ssh to the REST API, the entire data structure has been changed to be tool agnostic: A data structure for external tool requests replaces the info for the FOSSology upload. In future, albeit not supported today by the UI, also other tools could be integrated using the same data structure.
Warning Although the was much care for migrating existing data. It may happen with old datasets where source code attachments have been transferred to FOSSology using the ssh integration, the migration fails. For those datasets, the data must be changed manually. For example, just remove the status values.
Warning Migrations run per default in dry run mode, meaning that no changes are written to the database. After you have reviewed the changes (and checked that the scripts runs), you must change the DRY_RUN variable accordingly to False.
Two notable more features are provided by this release:
- Management for project obligations
- Merging release and vendor records added
New Features
653a7e3feat(ProjectUI): added project obligation logic on change of accepted license file648755afeat(REST): Added parameter to GET project by Group and Tag8eae7d3feat(rest): get attachmentUsages for a projectb8549defeat(REST): linked release hierarchy is included in the response1bc03f9feat(Project-UI) License Obligation tracker at Project Level1f506f2feat(Rest): New end points for project/component/release usage summary176557afeat(moderation): Moderation requests to all clearing admin irrespective of their group82977a0feature(merge): add wizard for merging vendorse476f39feat(rest): Added support to add role category fields while creating project86afeeffeat(Projects): enabled Project/Release mainline state change only for clearing admins578f53cfeat(fossology-rest): replaced ssh communication to fossology with RESTd19f658feat(external-tool-request): added general datastructure for external tool requests71535e6feat(Authorization): Added support to read keystore from central configuration43bd667feature(release): add release merge wizard
Corrections
ca88b44fix(ProjectUI): Added options to generate ReadmeOSS for main project only or main project with subprojects.51bc423fix(rest): Error getting component/project with unknown creator7814e7efix(ProjectUI): Obligation view for changes in linked release attachment255f54efix(ui): Added missing tooltip00c3110fix(businessrules): NPE in clearingStateSummaryComputer6bb0cc2fix(project): Keep release mainline state as it is while cloning project7b488d5fix(projectUI): NPE in SW360Utils.getApprovedClxAttachmentForRelease7181861fix(LicenseInfo): NPE in ProjectPortlet.prepareLicenseInfo and downloadLicenseInfo7df48dafix(rest): License information generation based on attachment usages from rest.466185efix(project): prevent cyclic link in linked projectsdcc4192fix(projectUI): NPE in ProjectDatabaseHandler.setReleaseRelations6f02ae7fix(component): incorrect release edit link in component edit page20211c9fix(component): component merge not workinge1921d7Fix(Project UI): Removed 'Unknown' from Project Clearing Team dropdown16c3452fix(REST): added support for createdComment field for uploadAttachements2e0d776fix(Project/Admin): Set to default text feature is not working correctly for Obligationaa71a06fix(Componnet): ComponentType field should be mandatoryc7a0737fix(links): Fixed the incorrect links
sw360-5.1.0-M1
sw360-5.1.0-M1
This release contains a number of corrections after the Liferay Portal 7.2 CE GA1 based release has been rolled out. Therefore it contains mostly corrections for the UI. In addition to these, also the REST API endpoints were further improved. The report generation has been improved: Now, external Ids can be added to the generated documents.
Because it contains many corrections, every 5.0.0-M1 installation should be updated to this release.
New Features
c86c97bfeat(License Disclosure): Change order of listed items in disclosure documents82a45cffeat(license-disclosure): External Ids incorporated in the license disclosure5b554aefeature(table-filter): add filter box, fix print
Corrections
9b02a75fix(components): Recompute aggrated fields on save17d90eefix(DownloadLicenseInfo): Corrected license selection based on attachment selection on attachmentusaged6d8540fix(EditRelease UI): Removed duplicate field 'Licenses' from edit releaseb9be0e4fix(licenseDisclosure): Added acknowledgements in TEXT and Docx format of License Disclosureb123c48fix(LicenseDisclosureDocument): Ordering and formating license disclosure document.97008f3fix(merge): allow merging of complex fields, style improvementscd4c788fix(merge): fix update conflict on component mergec6b3838fix(merge): Some fields were not merged1e6f424fix(Release-UI): Vertical scrollbar for link release to project popup20fb3d2fix(ui): Added missing search boxdcd681bfix(vendor): fix view name used when editing vendorsabc6404fix(vulnerability): Vulnerability tab loading issuedc0b9d6fix(fossology): fossology and fossolgy4fe4d4ffix(Rest-API): Corrected 'createdBy' field value for Project and Componenteb15c85fix(Rest-API): Small fix around ProjectClearingState during create and update projectfae1c99fix(Rest-Component): Corrected all components by type rest end pointf7d204efix(REST: Project) : Fixed error response for create project from resta2750bffix(rest): Fixed get component API having default vendor id as empty
Infrastructure
d9ff676chore(pom): change snapshot version from 6.0.0-SNAPSHOT to 5.1.0-SNAPSHOTe59f8b3chores(config): Fix friendly URL for license page81600f4chores(merge): Retain owner as moderatora80b82cchores(pom): Update to next development version
sw360-5.0.0-M1
sw360-5.0.0-M1
This release is the first release using the Liferay Portal 7.2 CE GA1 release. The codebase of the portal project has been updated from the previously used Liferay 6.2 version. As this represents a huge change also to related areas (pom files, etc.), the sw360 5.0.0 is bascially a sw360 4.0.1 with the newer Liferay. The following commits have been applied:
New Features
35165e6feat(auth): script to add the unsafe default client directly to DB4fd501cfeat(thrift): add timeout for thrift client
Test, Documentation and Infrastructure
3c4d3edchores(all): Upgrade to Liferay 7.2 (Part I)6657e79chores(configuration): Update Liferay configuration7fbd42echores(all): Upgrade to Liferay 7.2 (Part II)52592bfchores(build): add build plugin7d9e30echores(deploy): add new deploy profile1d5bff2chores(liferay): Feedback from Liferay 7 review36ae2c1chores(build): Fix deploy profile918d054chores(configuration): allow external files- `` chores(changelog): initial commit
Corrections
deb868cfix(tests): Use configured couch db urlda1f0b8fix(search): make search logic consistent1d830eefix(project): fix compare if no version is set0c2a341fix(Components): Fix naming component error (name's component contain...c7f03c8fix(rest): fix broken logic in updateProjectbe90070fix(rest): auth server is broken due to LifeRay api change
sw360-4.0.1-M1
This release fixes a small issue at the project creation. It was added to have a good working sw360 4 release.
Corrections
c7f03c8fix(rest): fix broken logic in updateProject
sw360-4.0.0-M1
Proudly announcing a new milestone release for SW360. We have many additions since the last release 3.3.0 in November 2018. The main reason why it turned into the 4.0.0, a major version change, was the change on the database model. According to our versioning guidelines, we have major release jumps when the DB changes. Please see below for details about how to deal with the change.
The release has the following new features:
- A first release of the project / product approval report, listing and maintaining obligations resulting from OSS use.
- Support for integration for single-sign-on and identity management server keycloak
- A lot of enhancements (new endpoints) to the REST API
- More management for using attachments (license information, source code)
- Starting to parse and show SPDX information in the Web UI
- Integration of Codescoop`s OSS library OSMAN.
Comitters
There are many different contributors which lead to new releases a release, for example doing presentations and promoting sw360. If you count the committers who have commited since 3.3.0-M1 and this release, the credits for code go to the following persons:
akapti
alexbrdn
aratib
blaumeiser-at-bosch
bs-jokri
bs-matil
dreh23
greimela-si
hemarkus
henrik
imaykay
kallesoranko
lepokle
maierthomas
maxhbr
mcjaeger
nutanv1contr
smrutis1
sweetca
Changes
New Features
Larger areas of improvements include the work on the REST API (see individual changes below) and on the reporting for projects, which includes now a project clearing report.
4b12200feat(attachment-usage): Restrict users to change the attachment usage without any WRITE access68f28f7feat(attachment-usages): Take over the attachment usages from the original project, while cloning one.29ba68dfeat(client-management): added support to dynamically manage oauth clients4722f04feat(codescoop): osman integration923d236feat(default vendor): added possibility to save a default vendor for componentse21d358feat(duplicates): added support to prevent duplicate projects/components/releasesca45db7feat(homepage): show accepted releases in MyProjects portlet093bc8afeat(licenseinfo): Add version string to file namefe58767feat(licenseinfo): Use property for controlling license info generation111e99dfeat(licenseInfoMigration): added manual migration script for license infos28d252efeat(licenses): add support for project-only obligationsed7e9f9feat(project): Reporting Improvements4f2166afeat(project): Reporting Improvements33397befeat(Projects): Added new field "domain" to project summary65fa6d5feat(Projects): displayuploadedBy&Relationin Attachment Usages1944686feat(releaselink): add release to project from release view477019bfeat(report): add common rules tableb46cb4dfeat(report): add common rules table67975c2feat(report): fill development detail and additional requirements table2acd46dfeat(REST-Doc): Updated the REST API Documentation2cdaa1cfeat(Rest-Project) : Added possibility to update project from rest endpoint.2faffb9feat(rest): add keycloak support for sw360 rest api834e676feat(rest): Added CORS module to fix CORS problems with JS clientsa666bc3feat(rest): Added CORS module: fixes after reviewd9f6164feat(rest): Added missing fields to REST API json5438233feat(rest): Allow to search only by externalId-Key (without specific value)b35b265feat(rest): make screenName auth case insensitivee270a28feat(rest): REST Authentification with ScreenName390fb16feat(rest): Search by externalIds endpoints for releases and components381469ffeat(rest): Updated response for GET requests on resource lists if there are no resources available6821256feat(rest): Whitelist fields in REST API response2c68620feat(rest): Whitelisting Fields in the REST API Responseeb0c44dfeat(search-dialog): improved multi item search dialog1dc69adfeat(spdx-import): added functionality to view and use spdx information2b788b7feat(spreadsheet): Added component categories field on spreadsheet export of Project with linked releases45ba41efeat(sso-oauth): added possibility to get oauth access tokens when pre authenticated94971ecfeat(subproject licenses): added possibility to take over license selection from subproject8ca3200feat(tabview): added better navigation support for tabview3bb68c9feat(thrift): add http proxy for thrift clients26401dafeat(thrift): add newadditionalDataField for generic data storageee7b374feat(todoMigration): migration script for todosa903ba4feat(UI-attachment): Create attachment bundle zip container, even for only one attachment9a59372feat(UI-Project): Jump to edit release from ProjectDetails19bd0fafeat(UI:PageTitle): Show selected Project/Component Name in Browser Tab2f7474ffeat(ui): Send to fossology error message.
Corrections
ba57b76fix: Security changes in source codeaa9ccf3fix(attachment): Multiple attachment upload stall issue94fedc4fix(Attachments-UI):Restrict user from adding attachements with same file name31deb6ffix(chores): updated documentation including licenses file862915ffix(component edit): fixed an issue where external id and attachment changes were not savedd10022cfix(cve-search): disable tests by assume statement and refactor8908b66fix(license-import): add missing dependency0cf598afix(license-todo): Adding TODOs to License8fee825fix(licenseinfo): Exclude old commons-lang3 dependencies8ac21e0fix(licenseinfo): NPE at Generate License Reportbe69470fix(Project UI): Fixed "Set To Default Text" feature for project license info header144a8acfix(Project): Only users with Admin access should be allowed to edit a closed projectbe38717fix(ReleaseLink): Remove self link from LinkedReleases hierarchy8015cc8fix(report): adding coverage if content exceeds the max number of characters in cell2fc4bd3fix(report): corrections to report0525fdefix(report): fix indentation and message textfb70f43fix(report): Fix merge error, fix rest payloadc8d15acfix(REST API): Attachmentupload endpoint documentationb3615b3fix(rest): do not answer with 404 if resource list is empty12931fffix(rest): Download licenseinfo file error026cb34fix(rest): Hiding unwanted fields in project listing response in REST4a1f90cfix(scripts): add missing dependency to scripts/install-thrift.sh06d113dfix(sso-oauth): feedback from review00368cffix(treetables): fix inconsistent indentation in treetables8ddce65fix(UI-Release): UI error on duplicate release creation7db8c86fix(ui): After removing a task from Home page, the task is back in the list when navigating back01453cbfix(ui): datepicker date and year selection is made available8cad8eafix(UI): Deleting submitted task under My Task Submission section.4f07ca5fix(ui): Fix infinity loop by expanding empty projects in AttachmentUsagec07932bfix(user export): fix Nullpointer Exception on user export166b03dfix(user): migrate completly from getOpenId -> getScreenname20ea660fix(users): write screenname into externalID field6acf644fix(vendors): Remove vendorId and vendor of release in case of deletion6453b69fix(vul-scheduler): fixed an issue where vulnerabilities were stored in the wrong dbc94e999fix(wsimport): remove projects from components that are createdc54ef0efix(wsimport): small fixes and some refactoring for wsimporte3c47bafix(wsimport):download url for releases3cca3b8fix(documentation): Fixed link to issue tracker in eclipse org71c6f6ffix(rest): Fix self link for user resourcec2b5f90fix(licenses): added log message and handle GPL-2.0+ case when converting licensesbbf55aafix(wsimport): removed unnecessary check
Test, Documentation and Infrastructure
The most important part on the infrastructure part is the change of the thrift compile to version 0.11.0. This has an impact to all, because an update of the installed thrift compiler is required from the previous version for all machines where the sw360 projects needs to build. Note that also the ektrop lib has been updated as well as the webjars which include the Java script components for the Web UI.
7128acdchore(common): Mail service sends notifications asynchronousbdd45d2chore(rm): Change Thrift Version in Readmec4228b0chore(thrift): update thrift version to 0.11.07089e19chore(thrift): use install/fast make target5ba0ebfchore(ui): Auto resize textarea in project view and edit mode517faaachore(ui): Display banner warning for IE0864e14chore(ui): Improve lucene search logic for project versionf51c4afchore(ui): Some fixes for UI regarding search and filtersabf5be7chore(vulnerabilities): Linked releases can be empty or null (rest create project)b6da7cachores(developer): remove developer tag in pom.xmld4d522dchores(quick-deploy): add quick deploy for portlet165f9cachore(REST): add documentation for Licenses in Releases53ae7b0refactor(db-bridge): updated ektorp library version to current 1.5.00632505refactor(velocity): update to new version6e8c349refactor(webjars): update versions of webjars
Database Schema Updates
Because of changes in the couchdb schema you likely need to run a migration script. Please find more information here: sw360/scripts/migrations/, in summary, you will need to update in the database:
- Changes to the way how the selected licenses and resulting attachment usage information is stored leads to the need to execute `011_migrate_attachment_usages_license_info...