jira-importer commented on issue #281: URL: https://github.com/apache/maven-install-plugin/issues/281#issuecomment-2771863948
**[Witold Markowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wmarkow)** commented I tried to bisect but I had some issues with snapshot repository so I gave up. But anyway, it was not so hard to find out that this issue is a side effect of MINSTALL-121; now **packaging** is not used for file extension. My case is that I'm developing some maven plugin with custom packaging - let's say **xyz**. The main **jar** artifact produced during the build is not so important for me. What is important, is the **zip** file produced by **maven-assembly-plugin**. I was able to install this **zip** file in my local repository (by using **instal-file** goal) with **xyz** file extension. Then in some other project I can use this artifact (by defining a dependency with **<type>xyz</type>**) and Maven is happy that (at least) the artifact is available in my local repository. I'm not sure right now if I'm trying to hack Maven system by doing this :) Please advice. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
