Parent POM modified without version number upgrade
Opened this issue · 1 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. Use the parent POM (as3commons-project) from the Google Code repository
2. Attempt to build an application using AS3Commons with the Flex 3.6 SDK
3. Maven downloads the wrong SDK dependency (4.1.0.16076)
What is the expected output? What do you see instead?
If you are changing a major dependency of the project, the version number of
the POM needs to be incremented. Otherwise, versions of AS3Commons that work
with the Flex 3 SDK can no longer use it via Maven, because Maven now has the
wrong information.
What version of the product are you using? On what operating system?
Using as3commons-reflect 1.3 on Windows
Please provide any additional information below.
Most repositories (Adobe Cairngorm, projects.yoolab.org) have the older version
of the parent POM. The dev.yoolab.org has the latest 1.0.0 POM with the new
information.
The way I think something like this should be handled is to increment the
version of the parent POM when major dependencies are upgraded. The child
project POMs would then be upgraded to the new version as well. This would mean
that any previous releases would continue to work as expected without bringing
in extraneous dependencies.
Original issue reported on code.google.com by michael....@gmail.com
on 31 Oct 2011 at 12:55
GoogleCodeExporter commented
Hi there,
sorry for replying so late. Thanks for the heads-up, we'll try and make sure
the parent pom's version gets incremented next time changes are made to it.
cheers,
Roland
Original comment by ihatelivelyids
on 5 Dec 2011 at 10:27