Re: Version ranges not working

2012-09-30 Thread Hervé BOUTEMY
Le lundi 1 octobre 2012 02:31:44 Jesse Long a écrit : > I have created a ticket - http://jira.codehaus.org/browse/MNG-5353 thank you I changed it from "Bug" to "Wish": no, nobody ever asked for such a behaviour, it's really a new idea AFAIK which BTW seems a good enhancement IMHO now we need to c

Re: Version ranges not working

2012-09-30 Thread Hervé BOUTEMY
yes, please share experience about ranges: when it is useful, how, and so on we really need to write this "Guide to using version ranges" https://jira.codehaus.org/browse/MNG-1368 so we stop telling "ranges are a bad practice" but tell what they are useful for Regards, Hervé Le samedi 29 septe

Re: Keystore.jks file corrupted while maven packaging

2012-09-30 Thread Anders Hammar
Maybe you have turned on filtering? If not, the file should just be copied as-is. /Anders On Sun, Sep 30, 2012 at 10:14 AM, anjan wrote: > Hi, > > I am a beginner in Maven. > I kept my keystor.jks file under {project-tla}/src/main/resources. While > packaging process, Maven copying all the files

Re: Version ranges not working

2012-09-30 Thread Ron Wheeler
On 30/09/2012 9:11 PM, Jesse Long wrote: Regarding documentation, Maven generates a dependencies report, from the pom.xml, which the user can read. Regarding changing the artifactId for incompatibility, if you declare that you use semantic version number, then the user can tell that there is

Re: Version ranges not working

2012-09-30 Thread Jesse Long
Regarding documentation, Maven generates a dependencies report, from the pom.xml, which the user can read. Regarding changing the artifactId for incompatibility, if you declare that you use semantic version number, then the user can tell that there is incompatibility by noticing that the major

Re: Version ranges not working

2012-09-30 Thread Jesse Long
On 29/09/2012 05:29, Hervé BOUTEMY wrote: Le vendredi 28 septembre 2012 09:52:50 Jesse Long a écrit : My point is really about exclusive upper bounds. ok, now I'm starting to see the precise idea and believe it can avoid breaking subtle logic [1.7,1.8) could exclude anything "starting with" 1.8

Keystore.jks file corrupted while maven packaging

2012-09-30 Thread anjan
Hi, I am a beginner in Maven. I kept my keystor.jks file under {project-tla}/src/main/resources. While packaging process, Maven copying all the files from resources/ to classes inside the war. While doing so my keystore.jks file is corrupting. Please guide me whether my keystor file is in wrong

Re: [PATCH provided] How to generate an announcement from GitHub with Changes plugin?

2012-09-30 Thread Dennis Lundberg
Thank you! I'll review the patch. It might take a little while before I get to it, but I promise that I will. On 2012-09-30 13:40, Markku Saarela wrote: > Hi > > Created issue MCHANGES-290 > and patch is applied. > > Markku > > On 09/30/2012 08:43

Re: Version ranges not working

2012-09-30 Thread Benson Margulies
I think that Ron has hit the nail on the head here, and what he says has become best practice, via many bruises, in the open source community. Maven has a fundamental version model. That model is does not cover all possible real-world situations, as per JvZ's email and many others. In particular,

Re: Version ranges not working

2012-09-30 Thread Ron Wheeler
As the project manager and the one responsible for dealing with the phone calls from irate client managers when the SaaS crashes or does bad things to a bunch of their busy users, I want the developers to test with the version that they built with and run with the version that they tested. In

Re: Version ranges not working

2012-09-30 Thread Mark Struberg
In practice it gets more complicated if you are a framework. The safest way is to even change your package name to reflect the API change. LieGrue, strub - Original Message - > From: Ron Wheeler > To: users@maven.apache.org > Cc: > Sent: Sunday, September 30, 2012 7:08 PM > Subject:

Re: Version ranges not working

2012-09-30 Thread Ron Wheeler
Read what I wrote: If you are making an artifact that is not upward compatible, you need to prevent people from thinking that they can just up the version number in their GAV and they will get a better version with bugs fixed. You are in fact giving them a new artifact that will not only NOT fix

Re: Version ranges not working

2012-09-30 Thread Jochen Wiedmann
And while you're at it, please take care that the absence of a versionRange is supported. On Thu, Sep 27, 2012 at 11:19 PM, Paul French wrote: > Okay I see the problem. > > How about allowing a user to plugin a Version class that implements > Comparator > > class MavenVersion implements Compar

Re: [PATCH provided] How to generate an announcement from GitHub with Changes plugin?

2012-09-30 Thread Markku Saarela
Hi Created issue MCHANGES-290 and patch is applied. Markku On 09/30/2012 08:43 AM, Markku Saarela wrote: Hi, Thanks, i'll look those. Markku On 09/30/2012 12:06 AM, Dennis Lundberg wrote: Hi Support for a report based on issues at GitHub wa

Re: Version ranges not working

2012-09-30 Thread Laird Nelson
On Sun, Sep 30, 2012 at 12:28 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I have other thoughts but my 2.75 yr old son now is demanding to play > racing cars on my phone, so I need to hit send on this mail now ;-) > I love it when priorities rear their ugly head. :-) Trust

Re: Version ranges not working

2012-09-30 Thread Stephen Connolly
I think I forgot an "in theory"... But anyway, yes that is my point. The needs of the build are different from the needs of the runtime and the needs of the test. Maven is about specifying the needs of the build (it is a build tool after all) and because it does testing and because it has handy pl