[
https://jira.codehaus.org/browse/MIDEA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MIDEA-83.
-------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> When creating the model file, the parent POM's version of a dependency is
> added to the IDEA project's Libraries instead of the project POM's version
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDEA-83
> URL: https://jira.codehaus.org/browse/MIDEA-83
> Project: Maven IDEA Plugin (RETIRED)
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Windows XP, Sun JDK 1.5.0 (09)
> Reporter: Immo Huneke
>
> Create a parent POM that has a dependencyManagement section. Within this,
> define a dependency on the latest released version of a library.
> Now create a new Maven project that specifies the parent POM as its parent.
> Within this project, define a dependency on a later, unreleased version of
> the same library. Note we are not overriding a dependency in the parent POM
> (as per http://jira.codehaus.org/browse/MIDEA-57) but defining a new
> dependency, only inheriting the default properties of the dependency from the
> parent's dependencyManagement section.
> When you run "mvn idea:idea" from the command line, everything works fine.
> But open the new project in IntelliJ IDEA and you will see that the older
> version of the library has been attached, consequently any references in the
> Java code to new APIs available only in the new version of the library will
> remain unresolved.
> I am using version 2.1 of Maven, but cannot find version 2.1 of the IDEA
> plugin anywhere, so I expect I'm using version 2.0 of the plugin. If someone
> could build a version 2.1 and make it available please on a publicly
> accessible repository, I would like to test whether this has been fixed in
> 2.1.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)