jira-importer commented on issue #137: URL: https://github.com/apache/maven-install-plugin/issues/137#issuecomment-2771839303
**[Jay Stramel](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jay_stramel)** commented The problem with the custom artifact handler is that all artifacts share the same extension. For example, let's say you want to create a SAR packager plug-in. It is fairly easy to create a SAR file. However, most things don't recognize the SAR extension as a java archive (because it's JBoss specific). To work around this, you might create a second artifact (an attached artifact) that is the same as the SAR file, but with a JAR extension and a different classification. When the install plug-in copies the JAR artifact, it will rename it to a SAR extension because that is what the POM specifies as the package. This will make other things difficult also. For example: creating both a JAR and an EJB3 archive for working with the new EJB spec. So, how do we get this fixed? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
