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
IIUC, you propose creating a separate repository under jvm-profiling-tools org to hold jbang aliases for jattach, async-profiler and related tools.
I'm always happy to see more ways to facilitate adoption of async-profiler and friends, however, I find it a bit confusing to do it this way. If we are talking about accessing profiler commands via jbang, isn't it counterintuitive to connect them through an external location, which is neither a home for jbang nor for the profiler? Currently, jbang-catalog is at least tied with ap-loader that provides those commands. But when it becomes a separate repository, it will no longer be tightly connected with the project, making maintenance unobvious and complicated.
At the moment we have jbang aliases for
jvm-profling-tools/ap-loader
with a jbang-catalog.Means that you need to do
jbang <alias>@jvm-profiling-tools/ap-loader
for everything.If there was a jvm-profling-tools/jbang-catalog repo we could shorten this to just:
jbang <alias>@jvm-profiling-tools
shorter and easier to remember imo.
wdyt?
The text was updated successfully, but these errors were encountered: