[jira] (MNG-3695) Allow dependencies' scopes to be managed without explicit versions
[
https://jira.codehaus.org/browse/MNG-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-3695:
---
Fix Version/s: (was: Issues to be reviewed for 4.x)
> Allow dependencies' scopes to be managed without explicit versions
> --
>
> Key: MNG-3695
> URL: https://jira.codehaus.org/browse/MNG-3695
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
>Affects Versions: 2.0.9
>Reporter: Mark Hobson
>
> Currently, a dependency's version or a dependency's version and scope can be
> managed in dependency management, but a dependency's scope alone cannot be
> managed. For example, we cannot express the following:
> {noformat}
>
> javax.mail
> mail
> provided
>
> {noformat}
> Of course it does work if we also specify a version, but there are times when
> we want to merely control the scope and not change the resolved version.
> When we try the above example we get:
> {noformat}[INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process.
> Here is the information we do have for this artifact:
> o GroupID: javax.mail
> o ArtifactID: mail
> o Version: <<< MISSING >>>
> o Type:jar
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {javax.mail:mail:null:jar}: The version cannot be empty.
> at
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
> at
> org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:58)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.createManagedVersionMap(DefaultMavenProjectBuilder.java:452)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:912)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375){noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-3695) Allow dependencies' scopes to be managed without explicit versions
[
https://jira.codehaus.org/browse/MNG-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339953#comment-339953
]
Jason van Zyl commented on MNG-3695:
You have to specify versions in dependencyManagement. There's no way we can
change this now.
> Allow dependencies' scopes to be managed without explicit versions
> --
>
> Key: MNG-3695
> URL: https://jira.codehaus.org/browse/MNG-3695
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
>Affects Versions: 2.0.9
>Reporter: Mark Hobson
> Fix For: Issues to be reviewed for 4.x
>
>
> Currently, a dependency's version or a dependency's version and scope can be
> managed in dependency management, but a dependency's scope alone cannot be
> managed. For example, we cannot express the following:
> {noformat}
>
> javax.mail
> mail
> provided
>
> {noformat}
> Of course it does work if we also specify a version, but there are times when
> we want to merely control the scope and not change the resolved version.
> When we try the above example we get:
> {noformat}[INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process.
> Here is the information we do have for this artifact:
> o GroupID: javax.mail
> o ArtifactID: mail
> o Version: <<< MISSING >>>
> o Type:jar
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {javax.mail:mail:null:jar}: The version cannot be empty.
> at
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
> at
> org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:58)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.createManagedVersionMap(DefaultMavenProjectBuilder.java:452)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:912)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375){noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-3695) Allow dependencies' scopes to be managed without explicit versions
[
https://jira.codehaus.org/browse/MNG-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-3695.
--
Resolution: Won't Fix
> Allow dependencies' scopes to be managed without explicit versions
> --
>
> Key: MNG-3695
> URL: https://jira.codehaus.org/browse/MNG-3695
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
>Affects Versions: 2.0.9
>Reporter: Mark Hobson
> Fix For: Issues to be reviewed for 4.x
>
>
> Currently, a dependency's version or a dependency's version and scope can be
> managed in dependency management, but a dependency's scope alone cannot be
> managed. For example, we cannot express the following:
> {noformat}
>
> javax.mail
> mail
> provided
>
> {noformat}
> Of course it does work if we also specify a version, but there are times when
> we want to merely control the scope and not change the resolved version.
> When we try the above example we get:
> {noformat}[INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process.
> Here is the information we do have for this artifact:
> o GroupID: javax.mail
> o ArtifactID: mail
> o Version: <<< MISSING >>>
> o Type:jar
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {javax.mail:mail:null:jar}: The version cannot be empty.
> at
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
> at
> org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:58)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.createManagedVersionMap(DefaultMavenProjectBuilder.java:452)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:912)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375){noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-3695) Allow dependencies' scopes to be managed without explicit versions
[
https://jira.codehaus.org/browse/MNG-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-3695:
--
Fix Version/s: (was: 3.2)
Issues to be reviewed for 4.x
> Allow dependencies' scopes to be managed without explicit versions
> --
>
> Key: MNG-3695
> URL: https://jira.codehaus.org/browse/MNG-3695
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
>Affects Versions: 2.0.9
>Reporter: Mark Hobson
> Fix For: Issues to be reviewed for 4.x
>
>
> Currently, a dependency's version or a dependency's version and scope can be
> managed in dependency management, but a dependency's scope alone cannot be
> managed. For example, we cannot express the following:
> {noformat}
>
> javax.mail
> mail
> provided
>
> {noformat}
> Of course it does work if we also specify a version, but there are times when
> we want to merely control the scope and not change the resolved version.
> When we try the above example we get:
> {noformat}[INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] An invalid artifact was detected.
> This artifact might be in your project's POM, or it might have been included
> transitively during the resolution process.
> Here is the information we do have for this artifact:
> o GroupID: javax.mail
> o ArtifactID: mail
> o Version: <<< MISSING >>>
> o Type:jar
> [INFO]
>
> [INFO] Trace
> org.apache.maven.artifact.InvalidArtifactRTException: For artifact
> {javax.mail:mail:null:jar}: The version cannot be empty.
> at
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
> at
> org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:122)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:158)
> at
> org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:58)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.createManagedVersionMap(DefaultMavenProjectBuilder.java:452)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:912)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375){noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
