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.
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 r
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
