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

Generation failure after upgrade #1568

Closed
AllenF88 opened this issue Oct 17, 2023 · 4 comments
Closed

Generation failure after upgrade #1568

AllenF88 opened this issue Oct 17, 2023 · 4 comments

Comments

@AllenF88
Copy link

AllenF88 commented Oct 17, 2023

Hi all

Upgrading from v 1.1.0 to 1.2.1 I now get this error: generate failed: Path not present: Single Sided

here is the implementation in the pom file.

<plugin>
	<groupId>org.jsonschema2pojo</groupId>
	<artifactId>jsonschema2pojo-maven-plugin</artifactId>
	<version>1.2.1</version>
	<configuration>
		<sourceDirectory>${basedir}/src/main/resources/schema</sourceDirectory>
		<targetPackage>com.#####.integration.consumers.generated</targetPackage>
	</configuration>
	<executions>
		<execution>
			<goals>
				<goal>generate</goal>
			</goals>
		</execution>
	</executions>
</plugin>

Any ideas?

Stacktrace.log

@unkish
Copy link
Collaborator

unkish commented Oct 18, 2023

Hi

It's rather hard to say what might be the cause without minimal sample schema which would reproduce the issue

@joelittlejohn
Copy link
Owner

Yes, are you able to provide a small snippet @AllenF88? Something that sticks out immediately is that the property name contains a space, I wonder if we have some poor handling of spaces when looking up a property. This is surprising as I'm sure we have tests for that.

@AllenF88
Copy link
Author

Hi all. Apologies I thought I closed this yesterday. The issue was in one of the schemas, a ? snuck into the field name. this wasnt an issue on the older version though. But its better that its being validating.

@unkish
Copy link
Collaborator

unkish commented Oct 18, 2023

Properties with ? will be supported in next build/release (fixed with #1522)

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

3 participants