[
https://issues.apache.org/jira/browse/MNG-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636871#comment-14636871
]
ASF GitHub Bot commented on MNG-5840:
-------------------------------------
Github user ifedorenko commented on the pull request:
https://github.com/apache/maven/pull/60#issuecomment-123711202
What other options do we have? I guess we can create new `maven-versioning`
module, move `org.apache.maven.artifact.versioning` implementation there and
change maven-artifact to delegate to the new code. This is the only "clean"
solution I can think of, but I do not have time to do this now and not sure new
module with only a handful of classes is justifiable.
> <relativePath> is used if the groupId and artifactId match irrespective of
> the version
> --------------------------------------------------------------------------------------
>
> Key: MNG-5840
> URL: https://issues.apache.org/jira/browse/MNG-5840
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.1, 3.3.3
> Reporter: Stephen Connolly
> Assignee: Stephen Connolly
> Labels: regression
> Fix For: 3.3.5
>
> Attachments: mng-5840-testcase.tar.gz
>
>
> This is a regression. (In my view a serious one)
> Works fine with Maven 3.0 through 3.2.5
> Fails with 3.3.1 and 3.3.3
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
