Plugin does not properly handle dependency version using set notation
---------------------------------------------------------------------
Key: MIDEA-57
URL: http://jira.codehaus.org/browse/MIDEA-57
Project: Maven 2.x Idea Plugin
Type: Bug
Versions: 2.0
Environment: XP SP2
Reporter: David Hoffer
Create m2 project that has dependency with verion specified using set notation,
such as [1.1,). Build project using install goal, everything is fine; goal
goes to repositories and finds 1.1 verison. Now run idea:idea command; the
IDEA project will not have the right artifact version if any. See email notes
of my failure below:
My project is a multi-module maven/IDEA project.
One of the modules has a dependency on a locally deployed artifact
where the current version is xrite-colorlib-api-1.1. I want to
specify 1.1 as the minimum version as that version has what I need but
subsequent versions are likely to be okay as well. Using set notation
works well for install/deploy/release goals and must not cause
failures for the idea goal.
When I ran the idea goal here is what I found:
- The main module that had a dependency on xrite-colorlib-api (using
[1.1,) did not work at all. I.e. it made the IDEA module but it had
none of it's dependencies.
- At least one other module that had a build dependency on the prior
module, had a dependency on xrite-colorlib-api-1.2-SNAPSHOT which is a
bogus version. No snapshot of this artifact exists. In any case, it
should not choose to use a snapshot when a released version is
specified.
As to your question of if it should reach out to the defined repos and
use the most up-to-date version; I would think this would be ideal (if
not required). I think the rule should be that it should create IDEA
projects that are exactly equivalent to what maven would use/build if
I ran the install goal for example. How else could developers, using
maven to generate IDEA projects, ever stay in sync with what maven is
building?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
