> Is there a workaround for this? Use <type>zip</type>
>I'm not sure I follow the > reasoning for > why you'd need to change the extension when deploying? isn't > that left > to the plugin that created the artifact? war, ejb, jar, ear etc? I > guess it's not a problem to have zip files with a .example > extension as > long as they're to be accessed programatically, but I was thinking of > having links to my 'example' artifacts so they could be downloaded. > Probably it was a mistake from my side but I wanted to have a guard which stops you from deploying/installing to maven repositories artifacts which cannot be downloaded by maven. The implementation is mostly symmetrical with artifact downloading routines in maven core When you have artifact of type "example" ( <type>example<type> ) it has to have extension .example and reside in the folder "examples". Only maven plugins and ejb jars are handled in a special way. This is something we want to change in close future and make it to certain degree customisable. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
