[
https://jira.codehaus.org/browse/MNG-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-2585:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Overriding default naming
> -------------------------
>
> Key: MNG-2585
> URL: https://jira.codehaus.org/browse/MNG-2585
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
