Maintenance: E2E test handler parent pom out of sync with project version

[phipag]

Summary

The project version in the E2E test handlers that get deployed is not updated when performing a new release. This causes the E2E tests to run on a stale version of Powertools.

We are currently on version 2.3.0 but the project version and Powertools version in the handler parent pom is 2.0.0:

powertools-lambda-java/powertools-e2e-tests/handlers/pom.xml

Lines 1 to 26 in 4bf7abd

	<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>software.amazon.lambda</groupId>
	<artifactId>e2e-test-handlers-parent</artifactId>
	<version>2.0.0</version>
	<packaging>pom</packaging>
	<name>Handlers for End-to-End tests</name>
	<description>Fake handlers that use Powertools for AWS Lambda (Java).</description>
	<properties>
	<lambda.powertools.version>2.0.0</lambda.powertools.version>
	<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	<maven.compiler.source>11</maven.compiler.source>
	<maven.compiler.target>11</maven.compiler.target>
	<lambda.java.core>1.3.0</lambda.java.core>
	<lambda.java.serialization>1.1.6</lambda.java.serialization>
	<lambda.java.events>3.16.1</lambda.java.events>
	<maven.shade.version>3.5.0</maven.shade.version>
	<aspectj.plugin.version>1.13.1</aspectj.plugin.version>
	<maven.compiler.version>3.11.0</maven.compiler.version>
	<aws.sdk.version>2.32.2</aws.sdk.version>
	<aspectj.version>1.9.20.1</aspectj.version>
	</properties>

Why is this needed?

This is needed to make sure that we run E2E tests against the most recent Powertools version.

Which area does this relate to?

Governance

Solution

We need to include the handler pom in the parent pom of the project to make sure that it is also updated when running mvn versions:set during the release workflow.

Acknowledgment

• This request meets Powertools for AWS Lambda (Java) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, TypeScript