[jira] [Commented] (MNG-6450) Allow importing a POM with a classifier

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov commented on MNG-6450:
-------------------------------------

[~rfscholte], it doesn't sound that stupid to generate a BOM POM. If we relax this, current usecases wouldn't actually break because there is no change for them.
[~yborovikov], do you have a sample project for this already. I'd be interested to see how you imagine this plugin to work. As far as I know the Spring Framework BOM POM is managed manually and it works fine.

> Allow importing a POM with a classifier
> ---------------------------------------
>
>                 Key: MNG-6450
>                 URL: https://issues.apache.org/jira/browse/MNG-6450
>             Project: Maven
>          Issue Type: Improvement
>          Components: Dependencies, POM
>    Affects Versions: 3.0
>            Reporter: Yegor Borovikov
>            Priority: Major
>              Labels: easy-fix, pull-request-available
>
> Currently, a POM-packaged artifact with a classifier cannot be imported - there is an explicit check for that in [DefaultModelValidator|https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java#L480]. I couldn't find anything in Maven documentation that would mention/explain this limitation. According to [~rfscholte] this [might be|https://www.mail-archive.com/dev@maven.apache.org/msg114101.html] "historical".
> Example use case: a BOM (bill of materials) plugin could generate a BOM POM and attach it (with a classifier) to the project. However, currently there's no way to import the generated BOM because of the restriction.



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