Re: Activating profiles based on OS doesn't seem to work right

2007-02-08 Thread Franz Allan Valencia See
Good day to you, Matt, Thanks for the additional info. Yes, plexus-utils Os.java is the one handling the comparison in the os activation. Also, it is the reference that I use for [1] ( I placed it under maven user since I don't have write access to the PLEXUS wiki ). Furthermore, yes, the os.xx

Re: Activating profiles based on OS doesn't seem to work right

2007-02-08 Thread Matt Brozowski
On Feb 6, 2007, at 1:58 PM, Graham Leggett wrote: Hi all, I've been trying to use profile activation based on OS to work around maven's lack of support for exposing the OS family (you can test against the current OS family, you just cannot find out what the current OS family is using ${m

Re: Activating profiles based on OS doesn't seem to work right

2007-02-07 Thread Graham Leggett
On Wed, February 7, 2007 3:46 am, Franz Allan Valencia See wrote: > I don't know why this should not work ( and I don't have a Mac to try > it on). Try entering the os name all in small caps ( i.e. "mac os x" > ). Small case works, even though when you print the value of ${os.name} the operating

Re: Activating profiles based on OS doesn't seem to work right

2007-02-06 Thread Franz Allan Valencia See
Good day, Graham, See inline comments. On 2/6/07, Graham Leggett <[EMAIL PROTECTED]> wrote: For example, the following profile doesn't match anything on MacosX: activate-mac macosx ${os.arch} Mac OS X

Re: Activating profiles based on OS doesn't seem to work right

2007-02-06 Thread Vincent Massol
I've had this exact same problem yesterday but I thought it was me doing something wrong... It looks like a bug and I think a jira should be opened. Thanks -Vincent On Feb 6, 2007, at 7:58 PM, Graham Leggett wrote: Hi all, I've been trying to use profile activation based on OS to work ar

Activating profiles based on OS doesn't seem to work right

2007-02-06 Thread Graham Leggett
Hi all, I've been trying to use profile activation based on OS to work around maven's lack of support for exposing the OS family (you can test against the current OS family, you just cannot find out what the current OS family is using ${maven.os.family} or some equivalent, or it least it seem