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

dependency scope setting issues #394

Open
DataProvided opened this issue Apr 13, 2022 · 1 comment
Open

dependency scope setting issues #394

DataProvided opened this issue Apr 13, 2022 · 1 comment

Comments

@DataProvided
Copy link

Hi,

We are developing a tool to check whether the dependencies' scopes in maven are set rightly and reasonably.

Our tools have found some issues in your project about scope setting in maven' pom.xml file.

  • in pom.xml, org.jboss:jboss-vfs scope should be compile instead of provided.

Please help us confirm whether the above reports are right and explain why it should set like these.

Thanks a lot.

@HenningL
Copy link

HenningL commented Apr 19, 2022

Are you requesting help for your issues here to understand maven better?
<dependency> <groupId>org.jboss</groupId> <artifactId>jboss-vfs</artifactId> <version>3.2.15.Final</version> <scope>provided</scope> <optional>true</optional><!-- case: when using jboss-vfs --> </dependency>

There is even a comment on it. There are some dependencies you might need in a special environment e.g. jee container which than provide different implementation which are than used via java reflection. its is not compile scope since they are not bound at compile time but loosely loaded at runtime in a special environment. My question is: why is it even listed as dependency? perhaps documentation reasons for completeness. not sure.

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