1 |
If you are using JAVA_PKG_STRICT and install dev-java/java-dep-check, |
2 |
you will start to see messages like the following: |
3 |
>>> Merging dev-java/xstream-1.2-r2 to / |
4 |
* Possibly unneeded dependencies found in package.env: |
5 |
* commons-cli-1 |
6 |
|
7 |
This means that xstream is recording a dependency on commons-cli-1 to |
8 |
package.env but the class files installed by xstream don't reference any |
9 |
classes from commons-cli in the constant pool. For most packages this |
10 |
means that you just remove the usage from the ebuild but the tool will |
11 |
also give you false positives if the dependency is only needed at |
12 |
runtime and is loaded a provider framework for example. These false |
13 |
positives will eventually be hidden by mandating the use of |
14 |
java-pkg_register-dependency for these dependencies and then we can use |
15 |
the values given to that function to filter those out from the results |
16 |
of java-dep-check. |
17 |
|
18 |
Regards, |
19 |
Petteri |