[ https://issues.apache.org/jira/browse/UIMA-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-6458: --------------------------------------------- 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. was: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. > Spurious "parsedVersion.osgiVersion" in file names in target > ------------------------------------------------------------ > > Key: UIMA-6458 > URL: https://issues.apache.org/jira/browse/UIMA-6458 > Project: UIMA > Issue Type: Bug > Components: Build, Packaging and Test > Reporter: Richard Eckart de Castilho > Priority: Major > Fix For: parent-pom-16 > > > 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. -- This message was sent by Atlassian Jira (v8.20.7#820007)