[
https://jira.codehaus.org/browse/MNG-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286932#comment-286932
]
Markus KARG commented on MNG-2742:
----------------------------------
I understand that for stable builds, it is necessary to give the exact versions
of each plugin. But in some cases this argument is just ridiculous. For
example: If I want my code to compile using Java 1.5, I just omit any
configuration in the pom.xml and everything is fine. Actually I do not tell
Maven 3.0.3 which plugin to use then, nor its version. But as soon as I want to
tell the compiler that my code uses Java 6 syntax, I have to give the exact bug
fix number (2.3.2):
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
This is totally ridiculous as I STILL do not care about the name or version of
the plugin, but NOW I must not only tell that it is named maven-compiler-plugin
or that I want release 2.3 to be used, but ALSO that the exact bug fix 2.3.2 is
to be used. I even more CANNOT tell the system anymore that I want to get the
latest compiler plugin bug fix as now the version is fixed (this would have
worked well without this config entry, as soon as I download a later Maven ZIP
for example).
So in fact, the force to write the version leads to WORSE results as one will
not get the latest bug fixes then!
So please, make "use the latest bug fix" the default and don't force people to
check for later release numbers manually...! It is MORE essential to get
IMPROVED plugins and LESS essential to have THE SAME each time. BTW, if that
policy really leads to more unstable results, then the plugin authors have done
something REALLY wrong...!
> Using a version range in a plugin dependency causes "failure to resolve
> artifact" error
> ---------------------------------------------------------------------------------------
>
> Key: MNG-2742
> URL: https://jira.codehaus.org/browse/MNG-2742
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.4
> Environment: Windows XP SP2, java version "1.5.0_08"
> Reporter: Matthew Adams
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: mvn.txt, pom.xml
>
>
> If I declare a dependency in a plugin using an exact version, Maven correctly
> resolves the artifact. If, however, I change the dependency's version to a
> version range, Maven no longer resolves the artifact. I'm using the very
> same artifact and version range in my project's dependencies and everything
> works ok. See my attached pom.xml file for details, in particular, the
> comments "<!-- Using version range here ok -->" and "<!-- Can't use version
> range here! -->".
> I am using the "major.minor.revision-buildNumber" version string syntax as
> described on the wiki.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
