You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
System information
apollo.sh config
if onmaster
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 alatest
directory withsrc
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.The text was updated successfully, but these errors were encountered: