Recent changes to bugs

#36 Don't use version ranges for dependencies

2014-11-05T09:43:38.772000Z

status: accepted --> closed-fixed

#35 Beanshell dependency issue

2014-11-05T09:43:24.992000Z

status: accepted --> closed-fixed

#36 Don't use version ranges for dependencies

2014-09-10T19:36:45.949000Z

Group: unassinged --> 0.9.15

#35 Beanshell dependency issue

2014-09-10T19:36:16.085000Z

status: open --> accepted
Group: --> 0.9.15

#35 Beanshell dependency issue

2014-09-10T19:34:22.836000Z

I will change the dependency version number to a fix version, as the common wisdom is that version ranges shouldn't be used in Maven.

#36 Don't use version ranges for dependencies

2014-09-10T19:07:52.625000Z

(BTW, apparently, Sonetype keeps the last SNAPSHOT version forever, except in this case it got confused because accidentally there was a Maven 2 SNAPSHOT there too...)

#36 Don't use version ranges for dependencies

2014-09-10T18:47:04.866000Z

status: open --> accepted
assigned_to: Dániel Dékány

#36 Don't use version ranges for dependencies

2014-09-10T18:45:44.096000Z

Thanks for pointing this out, because the problem not only affects FMPP users but all FreeMarker users who have used version ranges. I haven't realized that it's not backward compatible to create a public snapshot repo... because, whoever used a version range on FreeMarker now starts to pick up snapshot versions instead of stables, which isn't funny. It's especially not fun as Sonetype deletes "old" (few days old) snapshots yet somehow Maven still wants to picking up 2.3.21-SNAPSHOT and then it fails.

For these reasons I have just deleted the snapshot repo of FreeMarker.

Regardless, I also change that dependency to 2.3.21 with the next FMPP release.

Don't use version ranges for dependencies

2014-09-10T17:04:43.043000Z

It's well known that version ranges don't work in Maven so should not be used. We just had a case where the dependency on freemarker was failing because it was resolving to 2.3.21-SNAPSHOT so the project could not be release and then it was failing because that snapshot was deleted because they upgraded to a release candidate. Since version ranges are known to know work correctly they should not be used, fixed versions should be used instead and users can override with dependencyManagement if needed.

Don't use version ranges for dependencies

2014-09-10T17:04:43.043000Z

Ticket 36 has been modified: Don't use version ranges for dependencies
Edited By: Dániel Dékány (ddekany)
Status updated: u'open' => u'accepted'
Owner updated: None => u'ddekany'