You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alex Dubov (JIRA)" <ji...@apache.org> on 2018/04/03 01:34:00 UTC

[jira] [Commented] (MNG-6387) Pom files should have a dedicated mime type registered ("application/pom+xml" or similar)

    [ https://issues.apache.org/jira/browse/MNG-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423353#comment-16423353 ] 

Alex Dubov commented on MNG-6387:
---------------------------------

https://issues.apache.org/jira/browse/MRM-755

This sort of issues.

But on more diverse scale - for example, when hosting stuff on S3 and populating Content-Type metadata using a common mime database.

> Pom files should have a dedicated mime type registered ("application/pom+xml" or similar)
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-6387
>                 URL: https://issues.apache.org/jira/browse/MNG-6387
>             Project: Maven
>          Issue Type: Wish
>          Components: POM
>            Reporter: Alex Dubov
>            Priority: Trivial
>
> For the sake of convenience working with ever growing abundance of packages, and, thus, pom files, is not it time to give the humble pom file its own, dedicated mime type (something to the tune of "application/pom+xml")?
> Presently, the fact that pom files don't have a dedicated mime type causes all kinds of minor but annoying issues in all kinds of least expected places.
> Considering that registering a mime type with IANA is a pretty straightforward process and that pom files are widely used for all kinds of automation purposes (and not exclusively by maven anymore), I, on behalf of the wider community, urge you to consider registering a dedicated pom mime type.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)