Skip to content

adapt to new SW360 release #34

Closed

Description

@gernot-h

From a comment by @heliocastro in #14 (comment):

Just FIY, we're in full mode towards next SW360 release, where we we kicked away liferay and whole authentication methods changed and extended API calls will exist, so some refactoring will be needed on sw360python as well.
( Yes, i'm willing to help as well )

Activity

  1. self-assigned this
    on May 27, 2026
  2. t-graf commented on May 27, 2026

    @t-graf
    Collaborator

    @gernot-h please have a look at the branch 34-adapt-to-new-sw360-release.
    Do we need more?

  3. gernot-h commented on May 27, 2026

    @gernot-h
    CollaboratorAuthor

    I don't have access to our v20 server yet and as our test instance will be switched anyways next week, I planned to look into the changes next week, would that be still in time for you? In the meantime, I'd suggest to create a PR from your branch, probably marked as draft, so that other users will notice it quickly. By the way, I think we should mention v20 explicitly in the ChanegLog.

  4. linked a pull request that will close this issueAdapt to new sw360 release #51on May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions