Maintenance: Clean up POMs

[scottgerring]

Summary

There is a lot of information duplicated between all of our POMs that can likely be kept in the parent POM only. We should take the v2 release as an opportunity to clean it up. Using powertools-core as an example, this all seems unnecessary:

powertools-lambda-java/powertools-core/pom.xml

Lines 34 to 56 in 349ea0b

	<url>https://aws.amazon.com/lambda/</url>
	<issueManagement>
	<system>GitHub Issues</system>
	<url>https://github.com/aws-powertools/powertools-lambda-java/issues</url>
	</issueManagement>
	<scm>
	<url>https://github.com/aws-powertools/powertools-lambda-java.git</url>
	</scm>
	<developers>
	<developer>
	<name>Powertools for AWS Lambda team</name>
	<organization>Amazon Web Services</organization>
	<organizationUrl>https://aws.amazon.com/</organizationUrl>
	</developer>
	</developers>
	<distributionManagement>
	<snapshotRepository>
	<id>ossrh</id>
	<url>https://aws.oss.sonatype.org/content/repositories/snapshots</url>
	</snapshotRepository>
	</distributionManagement>

If we have a look at the powertools-batch POM, we can see that it's working fine without any of this, as its all in the parent anyway.

Why is this needed?

As we added more projects (examples, modules broken down into smaller components), the amount of repetition in the POMs themselves is becoming increasingly error-prone.

Which area does this relate to?

Governance

Solution

No response

Acknowledgment

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