Hi Everyone
Due to this proposal received a very positive results from both the
committer team and the community[1], we are taking action now.
The new repository, skywalking-java[2], has been created. And the code
transfer has begun. After the agent side is finished, we will remove
the codes from
java agent is really skywalking for Java language :P If you ask me
Sheng Wu 吴晟
Twitter, wusheng1108
Daming 于2021年8月24日周二 上午10:05写道：
>
> Hi,
> ++1 , (I am very glad to heart splitting repo.)
>
> ---
> Personally, skywalking-java looks like skywalking for Java language. Could
> we name it
I think we don't have any tech block for the repo split.
If more people think it is reasonable, we can do that. And, we have to
keep the version continuous when the repo splits.
Sheng Wu 吴晟
Twitter, wusheng1108
kezhenxu94@apache 于2021年8月24日周二 上午9:53写道：
>
> Hi, I’m big +1 to split the repo into
Hi,
++1 , (I am very glad to heart splitting repo.)
---
Personally, skywalking-java looks like skywalking for Java language. Could
we name it skywalking-agent-java or skywalking-java-agent? (Even I know we
named other languages in this format, skywalking-{language})
Haochao Zhuang
Hi, I’m big +1 to split the repo into two,
the reason for me is to make it more clear and reasonable to maintain,
also, for new contributors they usually don't understand why Java agent
is different with other languages' agents and they usually mix the backend
with Java agent because they are in
Hi
In case not everyone noticed, the main CI-IT task time of our main
repo is closing in one hour.
Our e2e tasks and plugin tests are still efficient, but CI-IT will be
a time blocker for us shortly.
In my mind, the only option would be to split the java agent from the
main repo codebase and
