It must be exact in the sense that you can't just say 6.1 and expect to know that mean 6.1.x.
If you mean 6.1.x, I believe you have to specify a range - something like <version>[6.1.0,)</version> (actually, this really say version greater than 6.1.0, so 7.0.x would be included) --Chuck -----Original Message----- From: Thierry Boileau [mailto:[EMAIL PROTECTED] Sent: Friday, February 23, 2007 11:30 AM To: [email protected] Subject: Re: RC4 dist. refers to nonexistent Jetty version Hello Mikkel, do you confirm that the POM file must reference an exact version of Jetty? Actually, we were not sure about the way Maven manage versions. We hoped a kind of behaviour which allows to provide only a minor version (e.g. 6.1)... If it's not the case, the pom file will be updated with the latest release of Jetty. Best regards, Thierry Boileau > It makes sense to use the minor version number internally but I still > think that the pom file should be updated to refer to an existing > Jetty version. > If not it will be impossible to build projects using Maven! > > Any plans to fix this? > > - Mikkel > > On 2/23/07, Thierry Boileau <[EMAIL PROTECTED]> wrote: >> Hello Mikkel, >> >> the provided release of Jetty is 6.1.1 but for internal reason it's >> referenced with it's minor version (6.1). >> The complete version number has been provided in the changes file (in >> release RC3). >> >> Best regards, >> Thierry Boileau >> >> Mikkel Jensen a écrit : >> > Hi there, >> > >> > It seems that the latest release refers to Jetty version 6.1. >> > This version does not seem to exist on ibiblio or other repositories. >> > Instead it should probably be 6.1.0 or 6.1.1 if any of these are >> > considered stable. >> > >> > - Mikkel >> > >> >
