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

adapter.http: remove /aas submount from AAS repository #9

Merged
merged 1 commit into from
Mar 6, 2024

Conversation

jkhsjdhjs
Copy link

The submount has been removed from the spec, yay!

The submount has been removed from the spec, yay!
@Frosty2500
Copy link
Collaborator

Looks good to me.

@jkhsjdhjs jkhsjdhjs merged commit b9ba39a into feature/http_api Mar 6, 2024
7 checks passed
@jkhsjdhjs jkhsjdhjs deleted the http_api/remove_aas_submount branch April 1, 2024 20:19
Frosty2500 pushed a commit that referenced this pull request Nov 11, 2024
…sitory

Previously, we used the `rwth-iat` fork to pull the SDK from,
inside the docker file, due to the fact, that the `eclipse-basyx`
repository, did not contain the necessary branch.
Now that this is the case, it makes sense to always use the
official repository.

This also fixes the dependency issues of missing dependencies, as
they have been fixed in the main repository.

Fix #8
Fix #9
s-heppner added a commit that referenced this pull request Nov 17, 2024
…sitory

Previously, we used the `rwth-iat` fork to pull the SDK from,
inside the docker file, due to the fact, that the `eclipse-basyx`
repository, did not contain the necessary branch.
Now that this is the case, it makes sense to always use the
official repository.

This also fixes the dependency issues of missing dependencies, as
they have been fixed in the main repository.

Fix #8
Fix #9
Ornella33 pushed a commit that referenced this pull request Jan 13, 2025
…sitory

Previously, we used the `rwth-iat` fork to pull the SDK from,
inside the docker file, due to the fact, that the `eclipse-basyx`
repository, did not contain the necessary branch.
Now that this is the case, it makes sense to always use the
official repository.

This also fixes the dependency issues of missing dependencies, as
they have been fixed in the main repository.

Fix #8
Fix #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants