search

mojohaus / maven-native

https://www.mojohaus.org/maven-native/
MIT License
18 stars 12 forks source link

Using linkerFinalName != artifactId causes maven-install-plugin to fail #33

Closed pzygielo closed 4 years ago

pzygielo commented 5 years ago

Using linkerFinalName != artifactId causes maven-install-plugin to fail

If I set explicitly linkerFinalName it is honoured of course (i.e. linker's output is set to it), but then https://github.com/mojohaus/maven-native/blob/55634efe07e69921453c6b9a632f9715abda32b4/native-maven-plugin/src/main/java/org/codehaus/mojo/natives/plugin/NativeLinkMojo.java#L294-L295 or https://github.com/mojohaus/maven-native/blob/55634efe07e69921453c6b9a632f9715abda32b4/native-maven-plugin/src/main/java/org/codehaus/mojo/natives/plugin/NativeLinkMojo.java#L326-L327 set primary file to non-existent file. It makes maven-install-plugin to

with message The packaging plugin for this project did not assign a main file to the project but it has attachments. Change packaging to 'pom'. (or The packaging for this project did not assign a file to the build artifact depending on other assemblies being used or not) due to https://github.com/apache/maven-artifact-transfer/blob/0bdd00a9c0ead272e63729e555c729f505e0472a/src/main/java/org/apache/maven/shared/transfer/project/install/internal/DefaultProjectInstaller.java#L109