maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Fabulich (JIRA)" <>
Subject [jira] Commented: (MNG-2585) Overriding default naming
Date Tue, 03 Oct 2006 15:25:27 GMT
    [ ] 
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:

> Overriding default naming
> -------------------------
>                 Key: MNG-2585
>                 URL:
>             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
> 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:
For more information on JIRA, see:


View raw message