[
https://issues.apache.org/jira/browse/MNG-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924365#comment-17924365
]
Arnoud Glimmerveen commented on MNG-6450:
-----------------------------------------
[~gnodet]: I have tried this with 4.0.0-rc-2, but it still does not allow an
import when there is a classifier used in the import reference ('stack' in the
example below):
{noformat}
[ERROR] 'dependencyManagement.dependencies.dependency.classifier' for
my.provider:bom:pom:stack must be empty, imported POM cannot have a classifier.
@ bom-test:bom-test:1.0-SNAPSHOT, <PATH>/pom.xml, line 18, column 17
{noformat}
What was exactly fixed in relation to this issue in 4.0.0-rc-2 release?
> 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
(v8.20.10#820010)
