Either way, the definition of "Maven (latest)" is wrong, because if
"Maven (latest)" meant the latest Maven 1 (as we already have Maven 2
(latest) and Maven 3 (latest)) it's using Maven 2.x (incorrect), and if
"Maven (latest)" meant the latest Maven loaded (3.1), it's still
incorrectly using 2.x.
My suggestions:
1.) Get rid of "Maven (latest)" as it's just too vague and its
definition changes over time across major versions. Move any projects
on that to "Maven 2 (latest)" (as that's what it presently means anyway).
2.) Either change the text "Maven 3 (latest)" to "Maven 3.0.x (latest)"
(as it's not clear what Maven 3 latest means--3.0.x or 3.1) and consider
adding a new "Maven 3.1.x (latest)", *or* just change the text of "Maven
3 (latest) to "Maven 3.1.x (latest)" possibly without adding a "Maven
3.0.x (latest)".
Regards,
Glen
On 07/31/2013 10:11 AM, Marshall Schor wrote:
Following the "principle of least surprise", I would have expected that "Maven
(latest)" without any suffix of 1, 2 or 3, would mean the same as the lastest
Maven, which is Maven 3.0.5 at the moment.
Perhaps this can be fixed?
-Marshall
On 7/31/2013 6:53 AM, Glen Mazza wrote:
Sorry, I didn't realize Maven latest meant Maven 1 latest, there's Maven 2
(latest) and Maven (3) latest, and there's even Maven 3.0.5.
Never mind. :)
Glen
On 07/31/2013 06:51 AM, Glen Mazza wrote:
Hi, when I configure my Roller Maven builds and choose "Maven (latest)",
i.e., a desire to see the app run successfully on the newest Maven you have
loaded, no matter what, I'm not getting the latest available (3.0.4) but just
the old 2.2.1:
