You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Edward Ciramella <ec...@archivas.com> on 2005/02/22 22:17:23 UTC
Symlink badness. . .
Hello ant world - I'm attempting to create a symlink regardless if a
directory exists where the symlink is or if the symlink already exists.
What I'm seeing is kind of interesting.
Say I'm creating a symlink from /Users/username/test-link to
/Users/username/someotherdir/test-link
If the "to" is an actual directory, the symlink gets created as a
subdirectory of /Users/username/someotherdir/test-link.
So you wind up with something like:
/Users/username/someotherdir/test-link/test-link
I also noticed that if run twice, with overwrite false, I wind up with
another subdirectory as explained above. We have some branches that
don't have every directory branched (from parent to child) and people
are using symlinks. Is there another way to do this?
I looked around a bit in search of bugs against the symlink target, but
I couldn't find anything that looked like what I'm up against.
Any comments/help would be great.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Symlink badness. . .
Posted by Edward Ciramella <ec...@archivas.com>.
Yes - sigh - I've added all this functionality and a series of
dependencies to test for a symlink and then create them as needed.
I honestly think that branching every folder each time and asking
people to ignore via client spec is a better solution.
<target name="init" description="Sets up all properties and creates
symlinks as needed">
<available file="${basedir}/java" type="dir"
property="dir.java.present"/>
<available file="${basedir}/config" type="dir"
property="dir.config.present"/>
<available file="${basedir}/db" type="dir" property="dir.db.present"/>
<available file="${basedir}/install" type="dir"
property="dir.install.present"/>
<available file="${basedir}/qa" type="dir" property="dir.qa.present"/>
<available file="${basedir}/tools" type="dir"
property="dir.tools.present"/>
<available file="${basedir}/scripts" type="dir"
property="dir.scripts.present"/>
<available file="${basedir}/csrc" type="dir"
property="dir.csrc.present"/>
<property name="dir.main" location="${basedir}/../main"/>
<available file="${dir.main}" type="dir"
property="dir.main.present"/>
<fail message="The main branch is unavailable, please sync it and
try again." unless="dir.main.present"/>
<antcall target="ln-mk-all"/>
<echo message="setup complete"/>
<property file="${basedir}/version.properties"/>
<property name="ver.curr"
value="${ver.main}.${ver.minr}.${ver.bld}.${ver.ptch}"/>
<echo message="here is the current version - ${ver.curr}"/>
</target>
<!-- - - - - - - - - - - - - - -->
<!-- Symlink making targets -->
<target name="ln-mk-all"
depends="mk-java-ln,mk-config-ln,mk-db-ln,mk-install-ln,mk-qa-ln,mk-
tools-ln,mk-scripts-ln,mk-csrc-ln"/>
<target name="ln-rm-all" description="Removes all symlinks">
<symlink action="delete" link="${basedir}/java"
failonerror="false"/>
<symlink action="delete" link="${basedir}/config"
failonerror="false"/>
<symlink action="delete" link="${basedir}/db" failonerror="false"/>
<symlink action="delete" link="${basedir}/install"
failonerror="false"/>
<symlink action="delete" link="${basedir}/qa" failonerror="false"/>
<symlink action="delete" link="${basedir}/tools"
failonerror="false"/>
<symlink action="delete" link="${basedir}/scripts"
failonerror="false"/>
<symlink action="delete" link="${basedir}/csrc"
failonerror="false"/>
</target>
<target name="mk-java-ln" unless="dir.java.present">
<echo message="${basedir}/java does not exist"/>
<symlink link="${basedir}/java" resource="../main/java"
overwrite="true" failonerror="false"/>
</target>
<target name="mk-config-ln" unless="dir.config.present">
<echo message="${basedir}/config does not exist"/>
<symlink link="${basedir}/config" resource="../main/config"
overwrite="true" failonerror="false"/>
</target>
<target name="mk-db-ln" unless="dir.db.present">
<echo message="${basedir}/db does not exist"/>
<symlink link="${basedir}/db" resource="../main/db"
overwrite="true" failonerror="false"/>
</target>
<target name="mk-install-ln" unless="dir.install.present">
<echo message="${basedir}/install does not exist"/>
<symlink link="${basedir}/install" resource="../main/install"
overwrite="true" failonerror="false"/>
</target>
<target name="mk-qa-ln" unless="dir.qa.present">
<echo message="${basedir}/qa does not exist"/>
<symlink link="${basedir}/qa" resource="../main/qa"
overwrite="true" failonerror="false"/>
</target>
<target name="mk-tools-ln" unless="dir.tools.present">
<echo message="${basedir}/tools does not exist"/>
<symlink link="${basedir}/tools" resource="../main/tools"
overwrite="true" failonerror="false"/>
</target>
<target name="mk-scripts-ln" unless="dir.scripts.present">
<echo message="${basedir}/scripts does not exist"/>
<symlink link="${basedir}/scripts" resource="../main/scripts"
overwrite="true" failonerror="false"/>
</target>
<target name="mk-csrc-ln" unless="dir.csrc.present">
<echo message="${basedir}/csrc does not exist"/>
<symlink link="${basedir}/csrc" resource="../main/csrc"
overwrite="true" failonerror="false"/>
</target>
<!-- End Symlink making targets -->
<!-- - - - - - - - - - - - - - -->
On Feb 23, 2005, at 11:18 AM, Matt Benson wrote:
> --- Mark Lundquist <ml...@comcast.net> wrote:
> [SNIP]
>>
>> I'm no Ant guru, but here are some suggestions:
>>
>> you could just punt on <symlink>, and just <exec>
>> an ln -shf...?
>>
>> or, use <available file=""> and the "unless"
>> attribute on something
>> so that you only make the link if the directory
>> doesn't exist...
>
> I think EJ's ultimate solution is going to involve
> that, but there may be some changes to make to the
> symlink task as well regarding directories and so on,
> just to get the task's behavior in line with the
> expectations raised by its documentation.
>
> -Matt
>>
>> ~Mark
>>
>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> user-unsubscribe@ant.apache.org
>> For additional commands, e-mail:
>> user-help@ant.apache.org
>>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> 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
Re: Symlink badness. . .
Posted by Matt Benson <gu...@yahoo.com>.
--- Mark Lundquist <ml...@comcast.net> wrote:
[SNIP]
>
> I'm no Ant guru, but here are some suggestions:
>
> � you could just punt on <symlink>, and just <exec>
> an ln -shf...?
>
> � or, use <available file=""> and the "unless"
> attribute on something
> so that you only make the link if the directory
> doesn't exist...
I think EJ's ultimate solution is going to involve
that, but there may be some changes to make to the
symlink task as well regarding directories and so on,
just to get the task's behavior in line with the
expectations raised by its documentation.
-Matt
>
> ~Mark
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> user-unsubscribe@ant.apache.org
> For additional commands, e-mail:
> user-help@ant.apache.org
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Symlink badness. . .
Posted by Mark Lundquist <ml...@comcast.net>.
On Feb 23, 2005, at 7:54 AM, Edward Ciramella wrote:
> What I'm trying to do is create a symlink to a directory which may/may
> not exist in the current branch.
>
> So if the child branch doesn't have a particular folder, create a
> symlink to it prior to starting the build.
> It's possible for the child branch to contain this folder, but it may
> not always be the case.
>
> On Feb 23, 2005, at 10:47 AM, Matt Benson wrote:
>
>> --- Edward Ciramella <ec...@archivas.com> wrote:
>>
>>> With overwrite set to true and failonerror set to
>>> false, I still get
>>> the link in the sub directory and the second time
>>> it's run, I get the
>>> build failed message.
>>
>> Okay, are all these tests based on the situation that
>> ${basedir}/testing-simlinkdir is already a real
>> directory, and you want it to become a symlink
>> pointing to /Users/eciramella/testing-simlinkdir ?
>> Or, does ${basedir}/testing-simlinkdir not exist in
>> the beginning, but
>> ${basedir}/testing-simlinkdir/testing-simlinkdir is
>> still created on the second invocation with
>> overwrite="true"?
I'm no Ant guru, but here are some suggestions:
— you could just punt on <symlink>, and just <exec> an ln -shf...?
— or, use <available file=""> and the "unless" attribute on something
so that you only make the link if the directory doesn't exist...
~Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Symlink badness. . .
Posted by Edward Ciramella <ec...@archivas.com>.
What I'm trying to do is create a symlink to a directory which may/may
not exist in the current branch.
So if the child branch doesn't have a particular folder, create a
symlink to it prior to starting the build.
It's possible for the child branch to contain this folder, but it may
not always be the case.
On Feb 23, 2005, at 10:47 AM, Matt Benson wrote:
> --- Edward Ciramella <ec...@archivas.com> wrote:
>
>> With overwrite set to true and failonerror set to
>> false, I still get
>> the link in the sub directory and the second time
>> it's run, I get the
>> build failed message.
>
> Okay, are all these tests based on the situation that
> ${basedir}/testing-simlinkdir is already a real
> directory, and you want it to become a symlink
> pointing to /Users/eciramella/testing-simlinkdir ?
> Or, does ${basedir}/testing-simlinkdir not exist in
> the beginning, but
> ${basedir}/testing-simlinkdir/testing-simlinkdir is
> still created on the second invocation with
> overwrite="true"?
>
> -Matt
>>
>> Here is the exact line from the build file:
>>
>> <symlink link="${basedir}/testing-simlinkdir"
>> resource="/Users/eciramella/testing-simlinkdir"
>> overwrite="true"
>> failonerror="false"/>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> 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
Re: Symlink badness. . .
Posted by Matt Benson <gu...@yahoo.com>.
--- Edward Ciramella <ec...@archivas.com> wrote:
> With overwrite set to true and failonerror set to
> false, I still get
> the link in the sub directory and the second time
> it's run, I get the
> build failed message.
Okay, are all these tests based on the situation that
${basedir}/testing-simlinkdir is already a real
directory, and you want it to become a symlink
pointing to /Users/eciramella/testing-simlinkdir ?
Or, does ${basedir}/testing-simlinkdir not exist in
the beginning, but
${basedir}/testing-simlinkdir/testing-simlinkdir is
still created on the second invocation with
overwrite="true"?
-Matt
>
> Here is the exact line from the build file:
>
> <symlink link="${basedir}/testing-simlinkdir"
> resource="/Users/eciramella/testing-simlinkdir"
> overwrite="true"
> failonerror="false"/>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Symlink badness. . .
Posted by Edward Ciramella <ec...@archivas.com>.
With overwrite set to true and failonerror set to false, I still get
the link in the sub directory and the second time it's run, I get the
build failed message.
Here is the exact line from the build file:
<symlink link="${basedir}/testing-simlinkdir"
resource="/Users/eciramella/testing-simlinkdir"
overwrite="true"
failonerror="false"/>
On Feb 22, 2005, at 4:55 PM, Matt Benson wrote:
> --- Edward Ciramella <ec...@archivas.com> wrote:
>
>> Hmmm, doesn't seem to matter. In my example below,
>> if the "test-link"
>> directory exists, and regardless of if it is a
>> symlink, ant creates
>> another symlink dir, one level deeper. The second
>> time this is run
>> with overwrite="true" (and with failonerror="false")
>> I get "BUILD
>> FAILED" and a message about how the lowest one
>> already exists.
>
> You can do the same thing from the command line and
> get the same results, is what I am saying. ln -s
> takes two more arguments, the target and the link
> destination. If the named destination does not exist,
> it is taken to be the desired name for the link and
> all is well. If the destination exists and is a
> directory, it is taken as the directory into which the
> link should be created --with the basename of the
> target (if the named destination is not a directory
> then it is still taken as the name of the actual
> link). Now that the destination is known, if IT
> exists, the "File exists" error is encountered. If
> you simply use overwrite you should avoid all this
> rigmarole.
>
> -Matt
>
>>
>> On Feb 22, 2005, at 4:36 PM, Matt Benson wrote:
>>
>>> EJ, what you are seeing, AFAICT, is the by-design
>>> behavior of the ln executable. We can debate
>> whether
>>> allowing this is a bug in Ant, since the
>> documentation
>>> of the symlink task makes no mention of this
>> alternate
>>> interpretation of the link entity specified as a
>>> parameter to ln, but in the meantime your best
>> course
>>> will probably be to use indiscriminately the
>> overwrite
>>> attribute.
>>>
>>> HTH,
>>> Matt
>>>
>>> --- Edward Ciramella <ec...@archivas.com>
>> wrote:
>>>
>>>> Hello ant world - I'm attempting to create a
>> symlink
>>>> regardless if a
>>>> directory exists where the symlink is or if the
>>>> symlink already exists.
>>>> What I'm seeing is kind of interesting.
>>>>
>>>> Say I'm creating a symlink from
>>>> /Users/username/test-link to
>>>> /Users/username/someotherdir/test-link
>>>>
>>>> If the "to" is an actual directory, the symlink
>> gets
>>>> created as a
>>>> subdirectory of
>>>> /Users/username/someotherdir/test-link.
>>>>
>>>> So you wind up with something like:
>>>> /Users/username/someotherdir/test-link/test-link
>>>>
>>>> I also noticed that if run twice, with overwrite
>>>> false, I wind up with
>>>> another subdirectory as explained above. We have
>>>> some branches that
>>>> don't have every directory branched (from parent
>> to
>>>> child) and people
>>>> are using symlinks. Is there another way to do
>>>> this?
>>>>
>>>> I looked around a bit in search of bugs against
>> the
>>>> symlink target, but
>>>> I couldn't find anything that looked like what
>> I'm
>>>> up against.
>>>>
>>>> Any comments/help would be great.
>>>>
>>>>
>>>>
>>>
>>
> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail:
>>>> user-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail:
>>>> user-help@ant.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> __________________________________
>>> Do you Yahoo!?
>>> Yahoo! Mail - 250MB free storage. Do more. Manage
>> less.
>>> http://info.mail.yahoo.com/mail_250
>>>
>>>
>>
> ---------------------------------------------------------------------
>>> 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
>>
>>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Easier than ever with enhanced search. Learn more.
> http://info.mail.yahoo.com/mail_250
>
> ---------------------------------------------------------------------
> 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
Re: Symlink badness. . .
Posted by Matt Benson <gu...@yahoo.com>.
--- Edward Ciramella <ec...@archivas.com> wrote:
> Hmmm, doesn't seem to matter. In my example below,
> if the "test-link"
> directory exists, and regardless of if it is a
> symlink, ant creates
> another symlink dir, one level deeper. The second
> time this is run
> with overwrite="true" (and with failonerror="false")
> I get "BUILD
> FAILED" and a message about how the lowest one
> already exists.
You can do the same thing from the command line and
get the same results, is what I am saying. ln -s
takes two more arguments, the target and the link
destination. If the named destination does not exist,
it is taken to be the desired name for the link and
all is well. If the destination exists and is a
directory, it is taken as the directory into which the
link should be created --with the basename of the
target (if the named destination is not a directory
then it is still taken as the name of the actual
link). Now that the destination is known, if IT
exists, the "File exists" error is encountered. If
you simply use overwrite you should avoid all this
rigmarole.
-Matt
>
> On Feb 22, 2005, at 4:36 PM, Matt Benson wrote:
>
> > EJ, what you are seeing, AFAICT, is the by-design
> > behavior of the ln executable. We can debate
> whether
> > allowing this is a bug in Ant, since the
> documentation
> > of the symlink task makes no mention of this
> alternate
> > interpretation of the link entity specified as a
> > parameter to ln, but in the meantime your best
> course
> > will probably be to use indiscriminately the
> overwrite
> > attribute.
> >
> > HTH,
> > Matt
> >
> > --- Edward Ciramella <ec...@archivas.com>
> wrote:
> >
> >> Hello ant world - I'm attempting to create a
> symlink
> >> regardless if a
> >> directory exists where the symlink is or if the
> >> symlink already exists.
> >> What I'm seeing is kind of interesting.
> >>
> >> Say I'm creating a symlink from
> >> /Users/username/test-link to
> >> /Users/username/someotherdir/test-link
> >>
> >> If the "to" is an actual directory, the symlink
> gets
> >> created as a
> >> subdirectory of
> >> /Users/username/someotherdir/test-link.
> >>
> >> So you wind up with something like:
> >> /Users/username/someotherdir/test-link/test-link
> >>
> >> I also noticed that if run twice, with overwrite
> >> false, I wind up with
> >> another subdirectory as explained above. We have
> >> some branches that
> >> don't have every directory branched (from parent
> to
> >> child) and people
> >> are using symlinks. Is there another way to do
> >> this?
> >>
> >> I looked around a bit in search of bugs against
> the
> >> symlink target, but
> >> I couldn't find anything that looked like what
> I'm
> >> up against.
> >>
> >> Any comments/help would be great.
> >>
> >>
> >>
> >
>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> >> user-unsubscribe@ant.apache.org
> >> For additional commands, e-mail:
> >> user-help@ant.apache.org
> >>
> >>
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail - 250MB free storage. Do more. Manage
> less.
> > http://info.mail.yahoo.com/mail_250
> >
> >
>
---------------------------------------------------------------------
> > 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
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org
Re: Symlink badness. . .
Posted by Edward Ciramella <ec...@archivas.com>.
Hmmm, doesn't seem to matter. In my example below, if the "test-link"
directory exists, and regardless of if it is a symlink, ant creates
another symlink dir, one level deeper. The second time this is run
with overwrite="true" (and with failonerror="false") I get "BUILD
FAILED" and a message about how the lowest one already exists.
On Feb 22, 2005, at 4:36 PM, Matt Benson wrote:
> EJ, what you are seeing, AFAICT, is the by-design
> behavior of the ln executable. We can debate whether
> allowing this is a bug in Ant, since the documentation
> of the symlink task makes no mention of this alternate
> interpretation of the link entity specified as a
> parameter to ln, but in the meantime your best course
> will probably be to use indiscriminately the overwrite
> attribute.
>
> HTH,
> Matt
>
> --- Edward Ciramella <ec...@archivas.com> wrote:
>
>> Hello ant world - I'm attempting to create a symlink
>> regardless if a
>> directory exists where the symlink is or if the
>> symlink already exists.
>> What I'm seeing is kind of interesting.
>>
>> Say I'm creating a symlink from
>> /Users/username/test-link to
>> /Users/username/someotherdir/test-link
>>
>> If the "to" is an actual directory, the symlink gets
>> created as a
>> subdirectory of
>> /Users/username/someotherdir/test-link.
>>
>> So you wind up with something like:
>> /Users/username/someotherdir/test-link/test-link
>>
>> I also noticed that if run twice, with overwrite
>> false, I wind up with
>> another subdirectory as explained above. We have
>> some branches that
>> don't have every directory branched (from parent to
>> child) and people
>> are using symlinks. Is there another way to do
>> this?
>>
>> I looked around a bit in search of bugs against the
>> symlink target, but
>> I couldn't find anything that looked like what I'm
>> up against.
>>
>> Any comments/help would be great.
>>
>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> user-unsubscribe@ant.apache.org
>> For additional commands, e-mail:
>> user-help@ant.apache.org
>>
>>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - 250MB free storage. Do more. Manage less.
> http://info.mail.yahoo.com/mail_250
>
> ---------------------------------------------------------------------
> 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
Re: Symlink badness. . .
Posted by Matt Benson <gu...@yahoo.com>.
EJ, what you are seeing, AFAICT, is the by-design
behavior of the ln executable. We can debate whether
allowing this is a bug in Ant, since the documentation
of the symlink task makes no mention of this alternate
interpretation of the link entity specified as a
parameter to ln, but in the meantime your best course
will probably be to use indiscriminately the overwrite
attribute.
HTH,
Matt
--- Edward Ciramella <ec...@archivas.com> wrote:
> Hello ant world - I'm attempting to create a symlink
> regardless if a
> directory exists where the symlink is or if the
> symlink already exists.
> What I'm seeing is kind of interesting.
>
> Say I'm creating a symlink from
> /Users/username/test-link to
> /Users/username/someotherdir/test-link
>
> If the "to" is an actual directory, the symlink gets
> created as a
> subdirectory of
> /Users/username/someotherdir/test-link.
>
> So you wind up with something like:
> /Users/username/someotherdir/test-link/test-link
>
> I also noticed that if run twice, with overwrite
> false, I wind up with
> another subdirectory as explained above. We have
> some branches that
> don't have every directory branched (from parent to
> child) and people
> are using symlinks. Is there another way to do
> this?
>
> I looked around a bit in search of bugs against the
> symlink target, but
> I couldn't find anything that looked like what I'm
> up against.
>
> Any comments/help would be great.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> user-unsubscribe@ant.apache.org
> For additional commands, e-mail:
> user-help@ant.apache.org
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org