-
Notifications
You must be signed in to change notification settings - Fork 194
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
Runtime dependencies not resolved from target file #447
Comments
For the record same failures with includeDependencyScope="compile" if objenesis is not explicitly added. |
At least that's what I would expect as per the dependency tree: According to https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html runtime |
Okay, It seems for the current implementation it is required to choose As per definition: |
@mickaelistria I think this is something to consider for 2.7 as well and for the m2e release also. |
m2e change is done, will prepare now for tycho as well. The new syntax then would be |
… file Signed-off-by: Christoph Läubrich <[email protected]>
Using https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target - objenesis is removed and and includeDependencyScope="runtime" fails resolution with:
Cannot resolve project dependencies:
[ERROR] Software being installed: org.eclipse.ui.tests 3.15.500.qualifier
[ERROR] Missing requirement: org.mockito.mockito-core 4.1.0 requires 'java.package; org.objenesis [3.1.0,4.0.0)' but it could not be found
[ERROR] Cannot satisfy dependency: org.eclipse.ui.tests 3.15.500.qualifier depends on: osgi.bundle; org.mockito.mockito-core 2.13.0
@laeubi objenesis is supposed to be resolved as it's transitive runtime dependency of mockito as per https://repo1.maven.org/maven2/org/mockito/mockito-core/4.1.0/mockito-core-4.1.0.pom, right?
The text was updated successfully, but these errors were encountered: