[ARCHETYPE-689] Archetype Plugin 3.3.0 introduced incompatibilities

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.3.1
• Component/s: Generator, Plugin
• Assignee: Slawomir Jaranowski
• Reporter: Joe DiPol
• Created: 08/Oct/24 22:53
• Updated: 21/Oct/24 15:45
• Resolved: 21/Oct/24 15:45

Description

Archetype Plugin 3.3.0 introduced API incompatibilities that can break existing maven archetypes. This is significant because when the plugin is invoked by users the version of the plugin is rarely specified. An example of such a breakage is https://github.com/helidon-io/helidon/issues/9305 (where all previously shipped versions of our maven archetypes broke).

The incompatibilities were introduced by https://github.com/apache/maven-archetype/pull/211 and https://github.com/apache/maven-archetype/pull/215

Changes that broke our archetypes:

1. The removal of ArchetypeGenerationRequest.getProjectBuildingRequest()
2. The changing of the return type of ArchetypeGenerationRequest.getRemoteArtifactRepositories() from List<ArtifactRepository> to List<RemoteRepository>

It also looks like a number of other methods were removed from ArchetypeGenerationRequest.

As documented in https://maven.apache.org/archetype/maven-archetype-plugin/advanced-usage.html#post-generation-script the ArchetypeGenerationRequest object is the primary API for customization by a post-generation groovy script. And the changed/removed methods were not marked for deprecation. Any archetype released before 3.3.0 that relied on this class is potentially broken.
 

Issue Links

• is caused by: ARCHETYPE-655 Get rid of Wagon API to download catalogs
• is caused by: ARCHETYPE-673 Get rid of maven-artifact-transfer
• links to: GitHub Pull Request #231