On Tue, 2004-10-26 at 06:08, [EMAIL PROTECTED] wrote: > I think it could be easy to do by adding includes and exclude in the > ant:copy task.
It might be, I just haven't tried yet. > Why not using this king of thing ? > cactus.resources.dirs=logResources,otherResources > cactus.resources.logResources=src/main/resources/log > cactus.resources.logResources.includes=**.xml,**.dtd > cactus.resources.logResources.excludes=**old.* Hmm, I don't like this kind of 'XML linearization', but I think we don't have other option (as this is a POM limitation). We just need to make sure we can define the corner cases (like, what's the default, everything?). > If you want i can take a look at this and send you the result ... For me it's fine - if you provide a new patch with these changes and the proper test cases and documentation (on properties.xml), I will be glad to apply it. > Of course I am for applying this patch as I really need this > fonctionnality and actully we use a modify plugin.jelly so I need to do > the modification for new release (no one actually :) ) I'm using that modified patch at work too, so I'm eager to fix this bug. But we must be careful when we include such new features. > > PS: another improvement that could be made would be not relying on > > maven.build.dest and including the resources directly from inside > > the <cactifywar> tag. > Good approach. But is this fonctionnality could be use with <cactifyear> > too ? Guess so. -- Felipe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
