RE: reverse glob mapper pattern?

[Jacob Kjome]

Hi Bruce,

Well, I stand corrected.  What you are saying is right.  However, you had 
it right before.  I *don't* want to delete the sample.* files.  They are 
the templates for the generated files.  I must have been doing something 
weird.  I swear that I tried the glob mapper in pretty much the same way 
you describe and, for some reason, it was deleting all files in the 
${src.dir} and all directories underneath.  I must have had something 
something a bit off.  I really don't know how that happened???   It made me 
run off on a wild goose chase and end up with the verbose result that I 
posted as an attachment earlier.

Anyway, the following works

 
 
 
 
 
 
 
 

Thanks for making me look at that again.  Man, I really can't figure out 
what I did wrong before?

Jake

At 06:12 PM 9/23/2002 -0700, you wrote:
>At 11:33 AM 9/23/2002 -0700, Diane Holt wrote:
>
>>No, it selects it says it does -- namely, it selects only those files that
>>have an equivalent, as specified. It doesn't say it'll return *both* the
>>files that have an equivalent *and* the equivalent file(s) as well.
>
>Ok, perhaps I misunderstood the original request. I thought he wanted to 
>keep the sample files, since those were the ones that generated the others.
>
>If the problem is getting both sets of files, it should be doable with a 
>single fileset.
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>This appears to get around the "file already deleted" problem you 
>mentioned, Diane. In my tests, the  task did not prematurely 
>delete the individual files before the whole fileset had been processed by 
>DirectoryScanner. I don't know if that is true for all tasks which might 
>change the contents of the fileset, though.
>
>
>
>--
>To unsubscribe, e-mail:   
>For additional commands, e-mail: 

RE: reverse glob mapper pattern?

[Diane Holt]

Oh right -- I forgot you can do and's and or's and all that with the
selectors stuff... just been away too long :(  Jacob, you should give that
a try -- if it works, it'll streamline things considerably (sorry I didn't
think of it sooner... oh well, at least you know more Ant now, right? :)

Diane

=
([EMAIL PROTECTED])



__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: reverse glob mapper pattern?

[Jacob Kjome]

Hi Bruce,

You should probably go back and check out this whole thread.  I had already 
tried what you suggest below.  All that will do is select all files to 
delete.  See Diane's responses to see why that can't work.  Also see the 
solution I just posted.  It really is the only way to do this, currently.

Jake

At 05:52 PM 9/23/2002 -0700, you wrote:
>At 05:05 AM 9/21/2002 -0500, Jacob Kjome wrote:
>
>>Now what I'd like to do is set up a way to delete the files generated by 
>>this copy.  So, I need to find all files that have a corresponding 
>>"sample.*" file and delete those.
>>
>>If I just use the following, it deletes the sample.* file, not the * file 
>>which is the opposite of what I want...
>>
>> 
>> > dir="${src.dir}" >
>> 
>> 
>> 
>> 
>> 
>>
>>So, my question is, how do I set up a pattern where the fileset will get 
>>a list of the "*" files rather than the sample.* files to delete?
>
>Reverse the mapper "from" and "to" attributes.
>
>What you are asking  for in your fileset is all of the files in the 
>${src.dir} that are named "sample.*" and that have a matching "*" file. 
>What you want to be asking for is all the files named "*" for which there 
>is a matching "sample.*". Change the mapper to:
>
> checking for the existence of "sample.sample.my.properties" or similar. 
>Not necessary, but cleaner in understanding what the task is doing and a 
>trifle more efficient. It would also have been clearer for debugging, as 
>then your task wouldn't have done anything at all.
>
>
>
>--
>To unsubscribe, e-mail:   
>For additional commands, e-mail: 

RE: reverse glob mapper pattern?

[Bruce Atherton]

At 11:33 AM 9/23/2002 -0700, Diane Holt wrote:

>No, it selects it says it does -- namely, it selects only those files that
>have an equivalent, as specified. It doesn't say it'll return *both* the
>files that have an equivalent *and* the equivalent file(s) as well.

Ok, perhaps I misunderstood the original request. I thought he wanted to 
keep the sample files, since those were the ones that generated the others.

If the problem is getting both sets of files, it should be doable with a 
single fileset.

 
 
 
 
 
 
 
 
 
 
 
 

This appears to get around the "file already deleted" problem you 
mentioned, Diane. In my tests, the  task did not prematurely delete 
the individual files before the whole fileset had been processed by 
DirectoryScanner. I don't know if that is true for all tasks which might 
change the contents of the fileset, though.



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: reverse glob mapper pattern?

[Bruce Atherton]

At 05:05 AM 9/21/2002 -0500, Jacob Kjome wrote:

>Now what I'd like to do is set up a way to delete the files generated by 
>this copy.  So, I need to find all files that have a corresponding 
>"sample.*" file and delete those.
>
>If I just use the following, it deletes the sample.* file, not the * file 
>which is the opposite of what I want...
>
> 
>  dir="${src.dir}" >
> 
> 
> 
> 
> 
>
>So, my question is, how do I set up a pattern where the fileset will get a 
>list of the "*" files rather than the sample.* files to delete?

Reverse the mapper "from" and "to" attributes.

What you are asking  for in your fileset is all of the files in the 
${src.dir} that are named "sample.*" and that have a matching "*" file. 
What you want to be asking for is all the files named "*" for which there 
is a matching "sample.*". Change the mapper to:

 mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: 

Re[4]: reverse glob mapper pattern? (solution!)

[Jacob Kjome]

For the record, here is how I implemented the whole creation and
deletion of * files which have a corresponding sample.* file (see attached
text file)


Thanks to Diane Holt, Dominique Devienne, and Stefan Bodewig for all
the help!

Jake
















































































--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Re[2]: reverse glob mapper pattern?

[Dominique Devienne]

I agree it's bad, but it's even worse, since as Stefan pointed out,
'includes' is comma *and* space separated, so the current approach can
potentially fail if the relative pathname (stripped of its prefix by
) contains any spaces in it!!!

I'm still surprised the selectors cannot select the files Jacob wants to
delete, but instead of going all this way around (with a flawed method at
that), the easiest thing would be for Jacob to write his own selector.

Something like (not tested):

public class IsSampleCopySelector extends BaseSelector {
  ...
  public boolean isSelected(File basedir, String filename, File file) {
File parent = file.getParent();
String name = file.getName();
File sampleFile = new File(parent, "sample."+name);
return sampleFile.exists() && sampleFile.isFile();
  }

}

As far as campaigning for my weekend hacking to add a nested  to
all Task-deriving tasks: I'm not planning on wasting my breath on a lost
cause... --DD

-Original Message-
From: Diane Holt [mailto:[EMAIL PROTECTED]] 
Sent: Monday, September 23, 2002 2:59 PM
To: Ant Users List; Jacob Kjome
Subject: Re: Re[2]: reverse glob mapper pattern?

--- Jacob Kjome <[EMAIL PROTECTED]> wrote:
> However, now I have a problem that if this is run and
> no * files exist, the "includes" attribute on the filesets inside
>  ends up being empty like includes="".  When that happens, the
> fileset selects *all* files as part of the fileset so the entire
> project is deleted except for the default excludes.  That is extremely
> bad!

You'll need to break out the  into a separate target, have it
depend on the 'ing/'ing target, then 'if' on the
property that you'd be passing to 'includes' so that the target that does
the delete only runs if the property gets set. Of course, if all tasks
supported if/unless, you could just add an 'if' to the  --
unfortunately that's not available just yet (hint,hint to DD to campaign
for his patch :)
 
Diane

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Re[2]: reverse glob mapper pattern?

[Diane Holt]

--- Jacob Kjome <[EMAIL PROTECTED]> wrote:
> However, now I have a problem that if this is run and
> no * files exist, the "includes" attribute on the filesets inside
>  ends up being empty like includes="".  When that happens, the
> fileset selects *all* files as part of the fileset so the entire
> project is deleted except for the default excludes.  That is extremely
> bad!

You'll need to break out the  into a separate target, have it
depend on the 'ing/'ing target, then 'if' on the
property that you'd be passing to 'includes' so that the target that does
the delete only runs if the property gets set. Of course, if all tasks
supported if/unless, you could just add an 'if' to the  --
unfortunately that's not available just yet (hint,hint to DD to campaign
for his patch :)
 
Diane

=
([EMAIL PROTECTED])



__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re[2]: reverse glob mapper pattern?

[Jacob Kjome]

Hello Diane,

I've got things working with one more issue to solve.  Stefan Bodewig pointed out that 
if I set the
properties that have my directory locations using the "location"
attribute rather than "value", Ant will turn it into a nice absolute
path just like the fileset produces.  Now the  works for me.  So,
I currently have this:


























Now this works *if* there are * files that have an equivalent sample.*
also existing.  However, now I have a problem that if this is run and
no * files exist, the "includes" attribute on the filesets inside
 ends up being empty like includes="".  When that happens, the
fileset selects *all* files as part of the fileset so the entire
project is deleted except for the default excludes.  That is extremely
bad!  I tried fixing it by providing a "encludes" attribute like
excludes="**/**".  However, now that overrides the "includes"
attribute and won't delete anything even if the "includes" attribute
actually list files to include.

Is there a way to say exclude everything except for a non-empty
"includes" attribute?

Jake

Monday, September 23, 2002, 1:33:09 PM, you wrote:

DH> --- Dominique Devienne <[EMAIL PROTECTED]> wrote:
>> You'll also see that the  selector selects the wrong files,

DH> No, it selects it says it does -- namely, it selects only those files that
DH> have an equivalent, as specified. It doesn't say it'll return *both* the
DH> files that have an equivalent *and* the equivalent file(s) as well.

DH> You could, theoretically, do it with two 's (one to do an
DH> equivalent for sample.* -> *, and one to do it the other way around) --
DH> only when you're doing delete's, by the time you get to evaluating the
DH> second , the equivalents have already been deleted, so the second
DH>  comes up empty, which is why you need to evaluate them
DH> beforehand, and get the files they return into a property, then pass the
DH> value of that property to . And of course, since  won't
DH> take more than one file in the 'file' attribute, you need to pass the list
DH> to 'includes' instead, which is why you need to lop off the leading path
DH> up to the directory specified in 'dir', which is why you need to go
DH> through .

DH> Diane

DH> =
DH> ([EMAIL PROTECTED])



DH> __
DH> Do you Yahoo!?
DH> New DSL Internet Access from SBC & Yahoo!
DH> http://sbc.yahoo.com

DH> --
DH> To unsubscribe, e-mail:   
DH> For additional commands, e-mail: 



-- 
Best regards,
 Jacobmailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: reverse glob mapper pattern?

[Diane Holt]

--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> You'll also see that the  selector selects the wrong files,

No, it selects it says it does -- namely, it selects only those files that
have an equivalent, as specified. It doesn't say it'll return *both* the
files that have an equivalent *and* the equivalent file(s) as well.

You could, theoretically, do it with two 's (one to do an
equivalent for sample.* -> *, and one to do it the other way around) --
only when you're doing delete's, by the time you get to evaluating the
second , the equivalents have already been deleted, so the second
 comes up empty, which is why you need to evaluate them
beforehand, and get the files they return into a property, then pass the
value of that property to . And of course, since  won't
take more than one file in the 'file' attribute, you need to pass the list
to 'includes' instead, which is why you need to lop off the leading path
up to the directory specified in 'dir', which is why you need to go
through .

Diane

=
([EMAIL PROTECTED])



__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re[2]: reverse glob mapper pattern?

[Jacob Kjome]

Hello Stefan,

I think what Dominique means is that there should be a delete
capability equivalent to the copy capability.  for example...

This copy...










Should be equivalent to this delete...










one creates * files from sample.* files and the other deletes * files
that have a corresponding sample.* file.

Does that help make it clearer?

Jake


Monday, September 23, 2002, 9:01:21 AM, you wrote:

SB> On Mon, 23 Sep 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote:

>> Shouldn't delete simply take a , as does 

SB> I don't think so, what would you use it for?  Isn't the 
SB> selector (which accepts a ) all that is needed (sorry, I
SB> haven't followed the thread very closely)?

SB> Stefan

SB> --
SB> To unsubscribe, e-mail:   
SB> For additional commands, e-mail: 



-- 
Best regards,
 Jacobmailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: reverse glob mapper pattern?

[Dominique Devienne]

If you look back at the thread, you'll see that Diane's solution simulates
the use of a nested  in , because  is currently not
supported for this task. You'll also see that the  selector selects
the wrong files, and that it cannot be made to select the right ones
(AFAIK), thus the need for the second  in .

The current turn around of using  with the caveat of pathname
transformation looks like a hack to me.

OTOH, I did just now realize that a  doesn't make sense for a task
that takes a single pathname, as opposed to  which takes two... So it
appears it might be a deficiency of the selectors not being able to select
the right files!?!?

Did we miss something Bruce? Thanks, --DD

-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] 
Sent: Monday, September 23, 2002 9:01 AM
To: [EMAIL PROTECTED]
Subject: Re: reverse glob mapper pattern?

On Mon, 23 Sep 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote:

> Shouldn't delete simply take a , as does 

I don't think so, what would you use it for?  Isn't the 
selector (which accepts a ) all that is needed (sorry, I
haven't followed the thread very closely)?

Stefan

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: reverse glob mapper pattern?

[Stefan Bodewig]

On Mon, 23 Sep 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote:

> Shouldn't delete simply take a , as does 

I don't think so, what would you use it for?  Isn't the 
selector (which accepts a ) all that is needed (sorry, I
haven't followed the thread very closely)?

Stefan

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: reverse glob mapper pattern?

[Dominique Devienne]

Yes, I've had similar problems in an Ant-based unit test, where the expected
path wasn't the same as the actual one, because of the conversion Ant does
automatically. Forcing Ant to convert all paths is indeed the solution.

But back to the original post... Shouldn't delete simply take a , as
does ??? --DD

-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] 
Sent: Monday, September 23, 2002 1:58 AM
To: [EMAIL PROTECTED]
Subject: Re: reverse glob mapper pattern?

On Mon, 23 Sep 2002, Jacob Kjome <[EMAIL PROTECTED]> wrote:

> Turns out that after some more clear thought and debugging that the
> issue lies in the fact that the paths provided by the fileset are
> cleaner than the ones defined by hand.  For instance, here are my
> variables used below:
> 
> 
> 
> 
> 

Take a look at 's location attribute



will be as clean as the settings in .

Stefan

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: reverse glob mapper pattern?

[Stefan Bodewig]

On Mon, 23 Sep 2002, Jacob Kjome <[EMAIL PROTECTED]> wrote:

> Turns out that after some more clear thought and debugging that the
> issue lies in the fact that the paths provided by the fileset are
> cleaner than the ones defined by hand.  For instance, here are my
> variables used below:
> 
> 
> 
> 
> 

Take a look at 's location attribute



will be as clean as the settings in .

Stefan

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: reverse glob mapper pattern?

[Jacob Kjome]

Turns out that after some more clear thought and debugging that the issue 
lies in the fact that the paths provided by the fileset are cleaner than 
the ones defined by hand.  For instance, here are my variables used below:





So the physical result of these paths on my machine are:

src.dir   = D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\src/../src
build.dir = 
D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\src/../WEB-INF

However, the paths coming out of the fileset look like:

D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\src
D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\WEB-INF

So, when I try to map like this:


 


it doesn't match because the path I'm specifying, even though it points to 
the same physical place, is not a string match.

So, now my question is, how do I get around this issue?  I'd like to be 
able to use , but I'm not sure how to apply it to 
the fileset or to each individual path inside ?

Any suggestions?

thanks,

Jake

At 10:37 AM 9/22/2002 -0500, you wrote:

>Hi Diane,
>
>Thanks for the response.  However, I tried you example out and, though it 
>seems like it *should* work the way you have it, there is something 
>wrong.  Here is what I am using:
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>
>  refid="src.sample.fs">
> 
> 
> 
> 
>
>
>In this case, the echo only produces this:
>  [echo] 
> D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\src\sample.build.properties
>
>My expectation was that it should have been "build.properties", not 
>"sample.build.properties" that resulted from the  element.
>
>  refid="build.sample.fs">
> 
> 
>  value="${build.sample.fs.copy}"/>
> 
>
>
>In this case, I have 5 sample.* files.  However, the echo only produces 
>the last 3 of them.  The first two are skipped.  Plus, we have the same 
>problem as the first case with returning sample.* files rather than the 
>expected *.
>
>  [echo] 
> D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\WEB-INF\sample.log4j.xml,
> 
>D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\WEB-INF\sample.objectrepository.xml,
> 
>D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\WEB-INF\sample.web.xml
>
>
>Like I said, it seems to me that the example you provided makes sense and 
>*should* work, but something seems to be a bit off here.
>
>Note:  I am using Ant-1.5.1-beta1.  Is this a bug that I'm running into here?
>
>Jake
>
>At 05:16 PM 9/21/2002 -0700, you wrote:
>>--- Jacob Kjome <[EMAIL PROTECTED]> wrote:
>> > So, I need to find all files that have a corresponding
>> > "sample.*" file and delete those.
>> >
>> > If I just use the following, it deletes the sample.* file, not the *
>> > file which is the opposite of what I want...
>> > [snip]
>> >  
>> >  
>> >  
>>
>>That's because it's returning what  says it will return, which is
>>just those files that do have equivalents -- it doesn't return the
>>equivalents as well.
>>
>> > So, my question is, how do I set up a pattern where the fileset will get
>> > a list of the "*" files rather than the sample.* files to delete?
>>
>>Generate the fileset the way you currently are, only do it outside of the
>>, id it, then use  to get a comma-separated list to
>>pass to 'includes' for the :
>>   
>> 
>>   
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>> 
>>   
>> 
>>   
>>
>>Diane
>>
>>
>>=
>>([EMAIL PROTECTED])
>>
>>
>>
>>__
>>Do you Yahoo!?
>>New DSL Internet Access from SBC & Yahoo!
>>http://sbc.yahoo.com
>>
>>--
>>To unsubscribe, e-mail:   
>>For additional commands, e-mail: 

Re: reverse glob mapper pattern?

[Jacob Kjome]

Hi Diane,

Thanks for the response.  However, I tried you example out and, though it 
seems like it *should* work the way you have it, there is something 
wrong.  Here is what I am using:

 
 
 
 
 
 
 
 
 
 


 
 
 
 
 


In this case, the echo only produces this:
  [echo] 
D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\src\sample.build.properties

My expectation was that it should have been "build.properties", not 
"sample.build.properties" that resulted from the  element.

 
 
 
 
 


In this case, I have 5 sample.* files.  However, the echo only produces the 
last 3 of them.  The first two are skipped.  Plus, we have the same problem 
as the first case with returning sample.* files rather than the expected *.

  [echo] 
D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\WEB-INF\sample.log4j.xml,
 
D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\WEB-INF\sample.objectrepository.xml,
 
D:\myclasses\repository\Barracuda_2002-09-19\Barracuda\WEB-INF\sample.web.xml


Like I said, it seems to me that the example you provided makes sense and 
*should* work, but something seems to be a bit off here.

Note:  I am using Ant-1.5.1-beta1.  Is this a bug that I'm running into here?

Jake

At 05:16 PM 9/21/2002 -0700, you wrote:
>--- Jacob Kjome <[EMAIL PROTECTED]> wrote:
> > So, I need to find all files that have a corresponding
> > "sample.*" file and delete those.
> >
> > If I just use the following, it deletes the sample.* file, not the *
> > file which is the opposite of what I want...
> > [snip]
> >  
> >  
> >  
>
>That's because it's returning what  says it will return, which is
>just those files that do have equivalents -- it doesn't return the
>equivalents as well.
>
> > So, my question is, how do I set up a pattern where the fileset will get
> > a list of the "*" files rather than the sample.* files to delete?
>
>Generate the fileset the way you currently are, only do it outside of the
>, id it, then use  to get a comma-separated list to
>pass to 'includes' for the :
>   
> 
>   
> 
>   
> 
> 
>   
> 
> 
>   
> 
> 
> 
>   
> 
>   
>
>Diane
>
>
>=
>([EMAIL PROTECTED])
>
>
>
>__
>Do you Yahoo!?
>New DSL Internet Access from SBC & Yahoo!
>http://sbc.yahoo.com
>
>--
>To unsubscribe, e-mail:   
>For additional commands, e-mail: 

Re: reverse glob mapper pattern?

[Diane Holt]

--- Jacob Kjome <[EMAIL PROTECTED]> wrote:
> So, I need to find all files that have a corresponding 
> "sample.*" file and delete those.
> 
> If I just use the following, it deletes the sample.* file, not the *
> file which is the opposite of what I want...
> [snip]
>  
>  
>  

That's because it's returning what  says it will return, which is
just those files that do have equivalents -- it doesn't return the
equivalents as well.

> So, my question is, how do I set up a pattern where the fileset will get
> a list of the "*" files rather than the sample.* files to delete?

Generate the fileset the way you currently are, only do it outside of the
, id it, then use  to get a comma-separated list to
pass to 'includes' for the :
  

  

  


  


  



  

  

Diane


=
([EMAIL PROTECTED])



__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

reverse glob mapper pattern?

[Jacob Kjome]

Hi,

I use the following to copy sample.* files to *.  for instance 
"sample.build.properties" would become "build.properties"...

 
 
 
 
 
 
 
 

Now what I'd like to do is set up a way to delete the files generated by 
this copy.  So, I need to find all files that have a corresponding 
"sample.*" file and delete those.

If I just use the following, it deletes the sample.* file, not the * file 
which is the opposite of what I want...

 
 
 
 
 
 
 

So, my question is, how do I set up a pattern where the fileset will get a 
list of the "*" files rather than the sample.* files to delete?


Jake


--
To unsubscribe, e-mail:   
For additional commands, e-mail: