[ http://jira.codehaus.org/browse/MNG-2585?page=comments#action_76460 ] Dan Fabulich commented on MNG-2585: -----------------------------------
This applies not just to .NET libraries, but to all Windows DLLs, in fact. The correct solution, I believe, is to make the default repository layout correctly honor the "finalname" attribute on POMs. See the document here: http://docs.codehaus.org/display/MAVENUSER/BEA+Maven+Requirement+Documents > Overriding default naming > ------------------------- > > Key: MNG-2585 > URL: http://jira.codehaus.org/browse/MNG-2585 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories, POM, Artifacts, Multiple > Language Support > Affects Versions: 2.0.4 > Reporter: Jonathan Gilbert > > Currently all artifacts in a maven2 repository must be named > ${artifactId}-${version}[-${classifier}].${packaging}. Sometimes this is > simply not possible. Jars can be renamed easily enough, but other binaries > cannot. > My case involves .NET. .NET assemblies are completely analogous to java jars > - simply a packaging of classes. The crucial difference though is that .NET > assemblies cannot be renamed (as classes are located based upon their > containing assembly name). There are plenty of existing third party .NET > libraries which currently cannot be placed in a maven repository. (Note that > if the assembly is renamed such that, for instance, it has no version in the > name, this is no problem as .NET embeds this information into the assembly > itself.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
