Add package when javaType is not a fully qualified name

[eltabo]

I am working in a POC with OCPP 1.6/2.0 that use json schemas with a not fully qualified javatype (example attacched). May be useful check if a specified javatype is fqn or not and hence add the package name if needed.

[joelittlejohn]

Hi @eltabo. Thanks for submitting this. I think this is a good change, but we need an integration test that checks this behaviour before we can merge this PR. Could you add one?

[eltabo]

I have added some integration tests.

[brydesigns]

So in 1.1.1, "javaType":"Foo" produces com.example.Foo, "javaType":"subpackage.Foo" and "javaType":".subpackage.Foo" both produce subpackage.Foo, and I still have no idea how to produce com.example.subpackage.Foo.... I'm using <sourceSortOrder>FILES_FIRST</sourceSortOrder> because I have a subdirectory schema that incorrectly packages a "$ref":"../bar.json" reference, so that might be affecting my results (OS or SUBDIRS_FIRST do at least create subpackage).

• subpackage/foo.json (javaType=Foo, has a reference to ../bar.json)
• bar.json (javaType=Bar)
• foo-bar.json (javaType=FooBar, has a reference to subpackage/foo.json)

targetPackage=com.example

No sourceSortOrder:

• com.example.FooBar
• com.example.subpackage.Foo
• com.example.subpackage.Bar

Files first:

• com.example.FooBar
• com.example.Foo
• com.example.Bar

What I would prefer:

• com.example.FooBar
• com.example.Bar
• com.example.subpackage.Foo