Return-Path: <hoju@visi.com>
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 10503 invoked from network); 14 May 2003 06:25:06 -0000
Received: from rwcrmhc52.attbi.com (216.148.227.88)
  by daedalus.apache.org with SMTP; 14 May 2003 06:25:06 -0000
Received: from nicki.visi.com
 (c-24-118-17-192.mn.client2.attbi.com[24.118.17.192])
          by attbi.com (rwcrmhc52) with SMTP
          id <2003051406251805200gine1e>; Wed, 14 May 2003 06:25:18 +0000
Message-Id: <5.2.0.9.2.20030514011702.02f2b888@shell.visi.com>
X-Sender: hoju@shell.visi.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 14 May 2003 01:27:04 -0500
To: "Ant Users List" <user@ant.apache.org>
From: Jacob Kjome <hoju@visi.com>
Subject: RE: using wildcards in <map> attributes?
In-Reply-To: <5.2.0.9.2.20030513165038.034c3510@shell.visi.com>
References: <548DBE8D8628D611B2370004762FCCCA033E0BF4@MA-ATL80>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_575947656==.ALT"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--=====================_575947656==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed


Ok, I'm answering my own question.  I got a hint from an old post from 
Dominique Devienne...
http://marc.theaimsgroup.com/?l=ant-user&m=104403278822910&w=2

Instead of trying to get rid of specific drive letters, just do...

<pathconvert targetos="unix" property="somepath.unix">
     <path>
         <pathelement location="${somepath}"/>
     </path>
     <map from="${basedir}${file.separator}" to="" />
</pathconvert>

That creates a file path relative to the current build and is totally 
generic so I don't have to specify  multiple <map> entries to get rid of 
every possible drive letter and there is no need for regular expressions 
either.  Cool!


Jake

At 04:54 PM 5/13/2003 -0500, you wrote:

>Hmm... I think that kind of misses the point.  I need a property 
>containing a path which looks like a unix path even on Windows.  I have 
>the location.  I'm just trying to convert it so it has no drive letters on 
>it.  It works just fine as I have it below.  However, I just don't want to 
>have to <map> each and every drive letter to an empty string.  I'd rather 
>have a single map which says "remove any and all drive letters no matter 
>what actual drive letter is there".
>
>Jake
>
>At 05:43 PM 5/13/2003 -0400, you wrote:
>>I mistook it to be the mapper task
>>but can you use dirSet to get all the directory?
>>thanks,
>>manoj
>>
>>
>>
>>-----Original Message-----
>>From: Jacob Kjome [mailto:hoju@visi.com]
>>Sent: Tuesday, May 13, 2003 5:26 PM
>>To: Ant Users List
>>Subject: RE: using wildcards in <map> attributes?
>>
>>
>>
>>Can you explain what you mean by this?  I know what regular expressions
>>are, but are they useable in a <map>?  I have seen no indication that they
>>are.  Am I missing something?
>>
>>Jake
>>
>>At 02:39 PM 5/13/2003 -0400, you wrote:
>> >did you look for reg expression?
>> >
>> >thanks,
>> >manoj
>> >
>> >
>> >
>> >-----Original Message-----
>> >From: Jacob Kjome [mailto:hoju@visi.com]
>> >Sent: Tuesday, May 13, 2003 2:13 PM
>> >To: user@ant.apache.org
>> >Subject: Fwd: using wildcards in <map> attributes?
>> >
>> >
>> >
>> >I sent this last night and I think it might have gotten lost in the shuffle
>> >of all the posts this morning.  Does anyone know whether what I am asking
>> >below is possible?
>> >
>> >Jake
>> >
>> > >Posted-Date: Tue, 13 May 2003 00:38:40 -0500 (CDT)
>> > >Date: Tue, 13 May 2003 00:40:22 -0500
>> > >To: user@ant.apache.org
>> > >From: Jacob Kjome <hoju@visi.com>
>> > >Subject: using wildcards in <map> attributes?
>> > >
>> > >
>> > >My guess is that this is probably not possible, but I'll throw it out
>> > >there anyway.  I would like to use <pathconvert> to create a property
>> > >containing a path with unix directory separators whether on the Unix or
>> > >Windows.  That's easy.  However, I would also like it, on Windows, to be
>> > >able to fully remove the prefixed drive letter + colon combo.  I don't
>> > >care what drive it is, I just want it gone from the resulting path.  I
>> > >tried this...
>> > >
>> > ><pathconvert targetos="unix" property="src.core.home.unix">
>> > >     <path>
>> > >         <pathelement location="${src.core.home}"/>
>> > >     </path>
>> > >     <map from="*:" to=""/>
>> > ></pathconvert>
>> > >
>> > >However, the wildcard symbol (*) is treated literally rather than being
>> > >treated as a wildcard.  So, I have to resort to something like this....
>> > >
>> > ><pathconvert targetos="unix" property="src.core.home.unix">
>> > >     <path>
>> > >         <pathelement location="${src.core.home}"/>
>> > >     </path>
>> > >     <map from="c:" to=""/>
>> > >     <map from="d:" to=""/>
>> > >     <map from="e:" to=""/>
>> > >     <map from="f:" to=""/>
>> > >     <map from="g:" to=""/>
>> > ></pathconvert>
>> > >
>> > >However, that is both verbose and error prone.  What if the user is on
>>the
>> > >"h:" drive?  Can't I somehow use a wildcard to match against all drive
>> >letters?
>> > >
>> > >Just hoping!
>> > >
>> > >Jake
>> > >
>> > >
>> > >---------------------------------------------------------------------
>> > >To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>> > >For additional commands, e-mail: user-help@ant.apache.org
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>> >For additional commands, e-mail: user-help@ant.apache.org
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>>For additional commands, e-mail: user-help@ant.apache.org

--=====================_575947656==.ALT--