create new releases by copying existing releases. Unfortunately SW360 copies in these cases also the SVM component ID to the new release
(External id: com.siemens.svm.component.id)
Please describe your issue in few words here.
while creating a new release by coping existing releases, its coping the external id also and this ID's create a problem in SW360 and SVM Portal.
How to reproduce
Describe the bug and list the steps you used when the issue occurred.
Screenshots
If applicable, add screenshots to help explain your problem.
Description
create new releases by copying existing releases. Unfortunately SW360 copies in these cases also the SVM component ID to the new release
(External id:
com.siemens.svm.component.id
)Please describe your issue in few words here. while creating a new release by coping existing releases, its coping the external id also and this ID's create a problem in SW360 and SVM Portal.
How to reproduce
Describe the bug and list the steps you used when the issue occurred.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions
Logs
Any logs (if any) generated in
SW360 logs
Logs generated under /var/log/sw360/sw360.log
Tomcat logs
Logs generated under /var/log/tomcat/error.log