8000 Could AOP's package be part of a normal package rather than a separate dependency library? · Issue #33 · XianyuTech/aspectd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Could AOP's package be part of a normal package rather than a separate dependency library? #33

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

Closed
lfkdsk opened this issue Nov 22, 2019 · 1 comment

Comments

@lfkdsk
Copy link
lfkdsk commented Nov 22, 2019

It is very inconvenient to transfer the Main Package to the AOP Module for AOP functions, and the Main Package will be unidirectionally dependent by AOP, making it difficult to use classes in the AOP Module.

@lfkdsk lfkdsk changed the title Can AOP's package be part of a normal package rather than a separate dependency library? Could AOP's package be part of a normal package rather than a separate dependency library? Nov 22, 2019
@kangwang1988
Copy link
Contributor
kangwang1988 commented Jan 20, 2020

@lfkdsk
Are you refering to that "AOP package should import the dependency of App package", and AOP's main should call app's main?

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

2 participants
0