Package copies everything when it only needs the js files about jasmine-maven-plugin

[searls]

Hi @davidpadbury -- apologies for the inconvenience The plugin originally copied everything (even .svn files), then it only copied JS files, then started copying everything (minus some default excludes).

Background: The current rationale for the default is that many JavaScript will try to pull in relative-pathed resources via AJAX, so anything under the $jsSrcDir is copied by default. I'm pretty sure that the operation to move everything is using [FileUtils.copyDirectory](http://commons.apache.org/io/apidocs/org/apache/commons/io/FileUtils.html#copyDirectory(java.io.File,%20java.io.File,%20java.io.FileFilter), which has a sort of clunky API for excluding/filtering.

I like the default where it is, but I think you're right, that an option to filter to only whatever the srcIncludes do (which is */.js by default) makes sense. It's just not trivial because the API being used to copy the directories can't read a normal collection of include/exclude strings.

As a workaround, have you considered limiting your JavaScript to a directory and pointing your $jsSrcDir at that directory, so other resource types aren't included when they don't need to be?

[davidpadbury]

We're using JavaScript in multiple places in the app so unfortunately I can't limit to a single directory.

You're copying the files using a IOFileFilter and it looks like it's possible to add some kind of filename filter fairly easily (WildcardFileFilter).

I may have a bash at implementing a file filter sometime soon.

[searls]

Cool. I just ask for your help in providing unit tests for it. I'd prefer for it to be configurable via a boolean property in AbstractJasmineMojo, because part of the reason for the existing behavior was feedback from teams who needed exactly the behavior you're trying to avoid :)

[klieber]

As of version 1.3.1.0 files are no longer copied to the target directory so this issue is no longer relevant.