bootable classifier should be configurable

[mareknovotny]

i tried to change the default bootable jar suffix with outputFileName in wildfly-jar-maven-plugin see this mareknovotny@3dd49ad. As it is bound to package goal all works fine. The jar is generated correctly, but if i do mvn clean install the installed artifact is actually default bootable jar not the one with defined file name in outputFileName.
How to propagate that outputFileName into install goal?

[INFO] --- maven-install-plugin:2.4:install (default-install) @ jsf-ejb-jpa ---
[INFO] Installing /home/mnovotny/projects/git/wildfly-jar-maven-plugin/examples/jsf-ejb-jpa/target/jsf-ejb-jpa.war to /home/mnovotny/.m2/repository/org/wildfly/plugins/jsf-ejb-jpa/4.0.4.Final-SNAPSHOT/jsf-ejb-jpa-4.0.4.Final-SNAPSHOT.war
[INFO] Installing /home/mnovotny/projects/git/wildfly-jar-maven-plugin/examples/jsf-ejb-jpa/pom.xml to /home/mnovotny/.m2/repository/org/wildfly/plugins/jsf-ejb-jpa/4.0.4.Final-SNAPSHOT/jsf-ejb-jpa-4.0.4.Final-SNAPSHOT.pom
[INFO] Installing /home/mnovotny/projects/git/wildfly-jar-maven-plugin/examples/jsf-ejb-jpa/target/jsf-ejb-jpa-standalone.jar to /home/mnovotny/.m2/repository/org/wildfly/plugins/jsf-ejb-jpa/4.0.4.Final-SNAPSHOT/jsf-ejb-jpa-4.0.4.Final-SNAPSHOT-bootable.jar

[jfdenise]

@mareknovotny , we are attaching the bootable jar file with the classifier "bootable". The name of the installed artifact follows the Maven GroupId, ArtifactId, Version, Classifier, Type naming.
To change the name of the installed artifact, you would need to change the artifactId of your project to have pom and artifact in sync.

[mareknovotny]

Do you have an example of that?
@Rikkola tries to override classifier and we thought that outputFileName should do that or plugin should apply that. Concrete example is at kiegroup/kie-wb-distributions#1114 and it is part of already existing war artifact module.
So your recommendation is to create new module just for bootable jar ?

[jfdenise]

@mareknovotny , if you install any Bootable JAR example, you will get the artifactid-version-bootable.jar being installed. As in your pasted example: jsf-ejb-jpa-4.0.4.Final-SNAPSHOT-bootable.jar
'bootable' is the classifier we are using.
From the PR you linked it seems that you need this classfier to be configurable. You would like to set it to "standalone". Right?

[mareknovotny]

yes, that is true. We need that classifier to be standalone instead of bootable.

[jfdenise]

Which version of the bootable JAR are you currently using? I think it makes sense to add this ability.

[Rikkola]

Hi, we are on 4.0.3.Final

[jfdenise]

You want to keep the 4.x or you can upgrade to 5.x?

[mareknovotny]

we would like to keep in 4.x for now if possible, as we do try to use that version with EAP XP

[jfdenise]

Ok, I am going to release a 4.1.0.Final

[jfdenise]

@mareknovotny @Rikkola Would that work for you: https://github.com/jfdenise/wildfly-jar-maven-plugin/tree/Issue_270