Skip to content

Releases: mtedone/podam

Enhancing type manufacturer support

25 Dec 18:36
Compare
Choose a tag to compare
  • Pass synthetic constructor/method parameter name to a type manufacturer
  • Changed inheritance tree traversal in search for a suitable manufacturer

Simplified ClassInfoStrategy redefinition

27 Oct 18:41
Compare
Choose a tag to compare
  • Regular expressions are used to define setters and getters
  • Setters can return void or this.

Extensible attribute's instantiation

09 Oct 15:40
Compare
Choose a tag to compare
  • DataProviderStrategy delegates attribute's instantiation to a specific TypeManufacturer, which can be registered for a custom types
  • Improvements and fixes to generic type resolution

Spring dependency removed

03 Sep 16:13
Compare
Choose a tag to compare
  • Spring dependency removed
  • Fixed issue when String.class could not be instantiated

Improvements to generic types resolution and support for factory methods

20 Aug 09:49
Compare
Choose a tag to compare
  • Fixed generic types resolution for attributes implementing Map and Collection interfaces.
  • Improved generic type resolution into actual types
  • hibernate-validator is a test dependency
  • Support for factory methods

Removed log4j2.xml from classpath

27 Sep 13:34
Compare
Choose a tag to compare

Removed log4j2.xml from classpath and optimised dependencies

Set memoization to false by default

09 Jul 23:07
Compare
Choose a tag to compare

In this release we're setting memoization to false by default

Switched type manufacturing to Sprint integration

08 Jul 22:30
Compare
Choose a tag to compare

This is a major release in Podam. We've switched basic type manufacturing to Sprint integration. This has simplified the PodamFactoryImpl monolith and provided a more elegant and extensible solution. You can now create your own TypeManufacturers by implementing the TypeManufacturer interface or extending the AbstractTypeManufacturer class and by adding your type channel, header-value-router and service-activator within the Spring configuration.

Moved unit tests to Serenity BDD

21 Jun 20:41
Compare
Choose a tag to compare

In this release we've moved all JUnit tests to Serenity BDD. Now Podam requirements are specified as BDD User Acceptance Tests and are available here: http://mtedone.github.io/podam/serenity/index.html

Podam is available from Maven Central

Introduced capability to run multiple factories independently and serenity BDD for acceptance tests

25 May 15:50
Compare
Choose a tag to compare

This release introduces the capability to run multiple factories independently and it introduces serenity BDD for acceptance testing. It also fixes various bugs.