ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 51602] zip reports "not found" when basedir attribute used with fileset
Date Fri, 05 Aug 2011 15:08:32 GMT

--- Comment #2 from Lothsahn <> 2011-08-05 15:08:32 UTC ---

Tried to subscribe to your mailing list to respond there (as requested), but my
sub request keeps getting bounced by the Apache mailserver as spam:
Sorry, we were unable to deliver your message to the following address.

Remote host said: 552 spam score (6.2) exceeded threshold
) [BODY]

Thank you for looking at this bugreport.  You stated:
basedir and nested filesets are totally unrelated.  With basedir you create an
implicit fileset with its dir attribute set to the value given in basedir. 
I.e. you now have two completely independent filesets.

I don't think this is true.  In the above example, my project basedir is
"C:\build".  When I specify basedir attribute, ant creates the zip based on the
specified basedir.  

For example:
In my above case 2, the project basedir is C:\build and the specified basedir
is C:\zipOutput.  The Zip task creates C:\zipOutput\ from
C:\zipOutput\doc.  If the implicit fileset and explicit fileset were not
related, ant should have zipped the C:\build\doc directory, which it does not

The bug:
Ant is validating that <fileset using project basedir> exists, then begins to
zip <fileset using specified basedir>.

"Don't use it [basedir] for anythig, only use nested filesets (or other
suitable resource collections)."

If we really want people to avoid using the basedir attribute (which I am
totally fine with, as your suggested example does workaround the issue), can we
simply mark basedir as deprecated in the ant Zip target documentation?

I believe:
1) This bug should be fixed OR
2) basedir should be marked as "deprecated, use filesets instead of
basedir/includes" on the ant Zip Task documentation

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message