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

Module org.testfx should not contain package org.assertj.core.error.future #682

Closed
koppor opened this issue Aug 25, 2019 · 5 comments
Closed

Comments

@koppor
Copy link

koppor commented Aug 25, 2019

Expected Behavior

No module issues during compilation.

Actual Behavior

I get following output:

Module org.testfx contains package org.assertj.core.error.future,
module org.assertj.core exports package org.assertj.core.error.future to org.testfx

Refs JabRef/jabref#3421 --> https://travis-ci.org/JabRef/jabref/jobs/576385529

I will try to create an MWE. I hope, however, that someone has an idea for that.

Specifications

  • Version: org.testfx:testfx-core:4.0.+ -> 4.0.17-alpha-SNAPSHOT, org.testfx:testfx-junit5:4.0.+ -> 4.0.17-alpha-SNAPSHOT
  • Platform: openjdk version "11.0.2" 2019-01-15
javafx {
    version = "11.0.2"
    modules = [ 'javafx.controls', 'javafx.fxml', 'javafx.web', 'javafx.swing' ]
}
@koppor
Copy link
Author

koppor commented Aug 25, 2019

Downgrade to 4.0.15 helped to solve this issue.

@brcolow
Copy link
Collaborator

brcolow commented Aug 27, 2019

I didn't know that 4.0.+ versions would grab SNAPSHOTS, that's a bit scary. The latest JPMS stuff on master is super sketchy right now. Trying to figure out how to get everything working in a modular world. So far it's quite confusing :).

@brcolow
Copy link
Collaborator

brcolow commented Sep 14, 2019

Can you test with the latest SNAPSHOT?

@koppor
Copy link
Author

koppor commented Oct 6, 2019

I tried, but now I am having trouble with hamcrest :-/. See JabRef/jabref#5397. Could not dive into it more.

@koppor
Copy link
Author

koppor commented Oct 6, 2019

Will create another issue if I find out more. The current gut feeling is that is an issue with hamcrest

@koppor koppor closed this as completed Oct 6, 2019
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