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

Cut fasten-core in two modules depending on the target use #202

Open
tmortagne opened this issue Jan 25, 2021 · 1 comment
Open

Cut fasten-core in two modules depending on the target use #202

tmortagne opened this issue Jan 25, 2021 · 1 comment

Comments

@tmortagne
Copy link
Member

Currently, fasten-core include and depends on many things, many things which are useless and can create conflicts when used as a library for local analysis.

It would help a lot if all local analysis related tool (LocalMarger, DirectGrpah, etc.) were moved in a separate module on which fasten-core would depend. Then things like the Maven plugin and javacg-opal could depend on the new module instead of fasten-core.

@proksch
Copy link
Contributor

proksch commented May 19, 2022

I completely agree... I do not like the fact at all, that core contains many executables. core should be for data-structures and closely-related utils only, everything that gets executed should be moved to separate plugins. As of now, core has 167 (transitive) dependencies, having such a monster of a library makes it VERY painful to include it in other projects.

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