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

Use same libray for both publishing and as project #3

Open
sagarnayak opened this issue Mar 1, 2021 · 1 comment
Open

Use same libray for both publishing and as project #3

sagarnayak opened this issue Mar 1, 2021 · 1 comment

Comments

@sagarnayak
Copy link

I have project A which is used as a package.
Project B uses A as a dependency. B is used as a dependency in project C.

What will be the structure of project B?

@prasad79
Copy link
Collaborator

prasad79 commented Mar 6, 2021

Hi sagarnayak,
Good question. I'll have to try a demo implementation to give you an exact answer to this.
Did you implement this related case in a project?
If yes, and its open source, please do share the project link and I can give it a try.

In your case generating a pom file with dependencies included for Project A & B will be required when Project C tries to include Package B.. it will get the list of dependencies for Package A automatically.
let me know your thoughts and findings and we can document it.

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