[UIMA-6458] Spurious "parsedVersion.osgiVersion" in file names in target

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: parent-pom-15, 3.4.0SDK, 3.2.0ruta
• Component/s: Build, Packaging and Test, Ruta
• Assignee: Richard Eckart de Castilho
• Reporter: Richard Eckart de Castilho
• Created: 18/May/22 13:40
• Updated: 08/Jun/22 09:57
• Resolved: 20/May/22 13:10

Description

When building projects that contain Eclipse plugins (e.g. UIMA Java SDK or UIMA Ruta), the profile build eclipse plugins from the parent POM is activated and that sets the finalName to ${project.artifactId}${parsedVersion.osgiVersion}. The ${parsedVersion.osgiVersion} is set during the build process by the maven-build-helper-plugin. It appears that some parts of Maven do not like the finalName being set with the ${parsedVersion.osgiVersion}. In particular, the maven-install-plugin copies the pom.xml file to the target folder under an only partially resolved final name such as org.apache.uima.ruta.example.extensions${parsedVersion.osgiVersion}.pom. However, then the maven-install-plugin installs this file as ${artifactId}${version}.pom (resolved) into the local repository. It seems that the maven-deploy-plugin also correctly deploys the file as ${artifactId}${version}.pom (resolved) into the distribution repository.

Optimally, it seems we should not set finalName at all. I have a feeling this is a historical artifact any no longer necessary with modern Eclipse, maven-bundle-plugin, tycho, etc.

Issue Links

• links to: GitHub Pull Request #19
• links to: GitHub Pull Request #86