Skip to content

JPMS package conflict #1054

@xenoterracide

Description

@xenoterracide

I'm not certain that this is really a spring-graphql issue, might be one with upstream, but I don't see why. I'm definitely not creating a graphql package, this reads like some proxy or class generation that I don't know about. This error does kind of read like the problem is coming from graphql java.

Error occurred during initialization of boot layer
java.lang.module.ResolutionException: Module com.xenoterracide.controller.registration contains package graphql, module com.graphqljava exports package graphql to com.xenoterracide.controller.registration

I thought maybe it was resources/graphql but renaming that doesn't seem to work.

this is my module definition for my test which is not committed.

module spring.app.commons.controller.registration.test {
  opens com.xenoterracide.controller.registration to org.junit.platform.commons, spring.core;
  requires org.assertj.core;
  requires com.xenoterracide.jpa;
  requires org.junit.jupiter.api;
  requires org.junit.jupiter.params;
  requires spring.beans;
  requires spring.boot.test;
  requires spring.test;
  requires spring.boot.test.autoconfigure;
  requires spring.orm;
}

this is the controller and gradle subproject https://github.com/xenoterracide/spring-app-commons/blob/a332c7b6cb6a6d86465aac981344280d13caad95/module/controller-registration/src/main/java/com/xenoterracide/controller/registration/RegistrationCtrlr.java#L1

the above jpms module would go in src/test/java/module-info.java

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: invalidAn issue that we don't feel is valid

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions