Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not copy any SVM component ids #1587

Open
nikkuma7 opened this issue Jul 12, 2022 · 0 comments
Open

Do not copy any SVM component ids #1587

nikkuma7 opened this issue Jul 12, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@nikkuma7
Copy link
Contributor

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

  • Last commit id on master:
  • Operating System (lsb_release -a):

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

@nikkuma7 nikkuma7 added the bug Something isn't working label Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant