On Aug 26, 2005, at 10:21 AM, Kenney Westerhof wrote:
It could be described as a bug: what the task does is
create an ant FileSet object. Since you defined no dependencies,
it's the same as <fileset id="runtime.fileset" dir="$
{localRepository}"/>
(where ${localRepository} = ~/.m2/repository).
I guess the default ant implementation for FileSet has an include
filter of **/* and no exclude filter.
As soon as you specify 1 dependency it will override the default
include
and put the referenced jar in there.
Ah. I tested that assertion and I believe you're right.
Could you file a JIRA issue for this please?
You got it! Thanks!
At least now I can be confident that I'm pulling in the right .jars,
and not getting multiple .jars of different versions.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
