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

Adding a new third party library to a user defined component so that buildtool can pick it up #15656

Open
samehmohamed88 opened this issue Mar 2, 2025 · 0 comments

Comments

@samehmohamed88
Copy link
Contributor

samehmohamed88 commented Mar 2, 2025

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 18.04):
  • Ubuntu 22.04
  • Apollo installed from (source or binary):
  • Either method
  • Apollo version (3.5, 5.0, 5.5, 6.0):
  • 10
  • Output of apollo.sh config if on master branch:

When using the buildtool to create a new user defined component, I am able to update the cyberfile to depend on a new third party library (one that has not yet been used in Apollo).

However it's very difficult for buildtool to pick it up.

One option is to add it to .aem/envroot/opt/apollo/neo/packages/3rd-sdl3 and then create a latest directory with src and BUILD files and workspace.bzl, however this seems very hacky.

I am wondering if there is a better way to tell the buildtool about new third party packages?

It looks like the .workspace.json file tells the buildtool about Apt repos, but I am not sure how to update such a repo yet.

@samehmohamed88 samehmohamed88 changed the title Adding a new third party library to a user defined component Adding a new third party library to a user defined component so that buildtool can pick it up Mar 2, 2025
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

No branches or pull requests

1 participant