Re: [discussion/idea] resource scoping

2006-08-02 Thread Brett Porter
Hi David, I see what you mean now. The first thing I'd try is to add excludes to the creation of test-jar for the resources you don't want included. If that isn't satisfactory, then certainly adding an additional classpath might be an option - I've seen recent additions of requests for that

Re: [discussion/idea] resource scoping

2006-08-02 Thread David J. M. Karlsen
Brett Porter wrote: I'm sorry ,maybe its just because I'm pre-coffee, but I don't really understand what you are referring to. Sorry - I'll try to elaborate a little more: process-[test-]resources copies with targetPath to target/[test-]classes, which is added to the classpath. So it should al

Re: [discussion/idea] resource scoping

2006-08-02 Thread Jochen Wiedmann
Brett Porter wrote: I'm sorry ,maybe its just because I'm pre-coffee Hopefully, that's gonna be fixed soon? (SCNR :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [discussion/idea] resource scoping

2006-08-02 Thread Brett Porter
I'm sorry ,maybe its just because I'm pre-coffee, but I don't really understand what you are referring to. process-[test-]resources copies with targetPath to target/[test-]classes, which is added to the classpath. So it should all be correct. I assume you are talking about modifying the mani

[discussion/idea] resource scoping

2006-08-02 Thread David J. M. Karlsen
Hi list! We have resource scoping today with the //build/resources and //build/testresources elements - this is OK for stuff that's supposed to end up in the archived artifact. (yes - I am aware that a different targetPath may be specified - but these directories won't be added to the suref