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

Java 9 Quick Win Pre Modules - Backport to 1.3.1? #187

Closed
nhojpatrick opened this issue Oct 11, 2017 · 3 comments
Closed

Java 9 Quick Win Pre Modules - Backport to 1.3.1? #187

nhojpatrick opened this issue Oct 11, 2017 · 3 comments

Comments

@nhojpatrick
Copy link
Member

Lots of people might still be using hamcrest 1.3, or other frameworks might not wanting to be instantly upgrade to Java 9 modules.

What is the developer views regarding doing a 1.3.1 and adding "Automatic-Module-Name" to aid people left behind?

@noopur2507
Copy link

Eclipse Java Development Tools (JDT) is using org.hamcrest.core 1.3.0 while running JUnit 4 tests. Since it does not have Automatic-Module-Name set in its manifest, it is currently not possible to use the hamcrest.core JAR on the modulepath in a Java 9 project.

Can we have a new version of hamcrest.core as suggested in this bug report with Automatic-Module-Name?

@namannigam-zz
Copy link

Not just this, I would say hamcrest would have to look into the “Split Packages” Dependencies as well.

@tumbarumba
Copy link
Member

Now that Hamcrest 2.1 is out (#224), does this solve this problem?

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

4 participants