DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=11270>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=11270 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2007-01-29 09:06 ------- (In reply to comment #16) > I don't see how that can be used in a jar task to handle the situation that > the > original post was about. > > I have something like: > > <jar jarfile="my.jar"> > <fileset dir="${basedir}/conf/properties" includes="*.properties"/> > <fileset dir="${basedir}/classes" includes="**/*.classes"/> > </jar> > > If there is a conf/properties directory, I want all the properties files to be > in the jar with no path. If the directory, doesn't exist, I want it to go on > to > the next patternset. I don't see how the <files> approach be used to do this. > > The failonerror attribute would have been so simple. > Actually, it does seem that using <files> does not constitute a complete solution, due to the fact that files included by this collection would not have any leading path information; any archive created this way would be flat! :o There is still talk about supporting this behavior, so I will reopen this report. > -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
