Add support for ConstructorProperties when populating property values about modelmapper HOT 3 OPEN

For Java 1.5 backward compatibility you can could create an optional sub module dependency that is built with 1.6. Then in your core module you do some simple reflection like if org.modelmapper.jdk16.ContructorPropertiesStrategy exists (which would only be true if the user included as a dependency and is using 1.6 >). If it exists you dynamically invoke the class. If it does not then its a NOOP. The Springframework I know does this in several places.

from modelmapper.

So all of my 1.6 functionality would need to go into a sub-module?

from modelmapper.

You can include the ConstructorProperties annotation in your distribution and add the strategy. If on Java 5, users should not use the annotation or strategy. If on Java 6+, the rt.jar will occur first in the classpath and your definition won't be evaluated by the Java compiler. If the ContructorPropertiesStrategy is used, on the first invocation you can verify the Java version to disallow accidental use by 1.5 clients.

The above technique is the only way I know how to handle @SafeVarargs to make Java 6 generated code lint free in Java 7.

I ran into this since jOOQ 3.1 now supports pluggable mappers. The previous mapper could match constructor arguments for immutable instances, but ModelMapper cannot. I'd prefer using ModelMapper to use projections and that jOOQ's mapper is slow by not retaining a reflection cache. For now I'm writing custom providers, but I find that a little ugly since it doesn't demotivates developers from using immutable domain models.

from modelmapper.