multiple directories for src/spec about jasmine-maven-plugin

[mikesmithson]

+1 for this as well.

[marceloverdijk]

+1 as my 3th party libs are in src/main/webapp/js/lib
and my coffeescript sources are in src/main/coffee

[klieber]

+1
I have an overlay containing scripts I need. Currently this is how I workaround the limitation:

<configuration>
  <jsSrcDir>${project.basedir}</jsSrcDir>
  <sourceIncludes>
    <include>target/overlay/scripts/*.js</include>
    <include>src/main/webapp/resources/scripts/*.js</include>
    <include>src/main/webapp/resources/scripts/*.coffee</include>
  </sourceIncludes>
</configuration>

Seems to work OK. Only downside is that I have to use dependency:unpack to unpack the overlay prior to the test phase so that the target/overlay/scripts directory exists. It'd be neat if the plugin could somehow just take care of that step for me but its not a big deal.

[AGresvig]

+1
We have a module for shared assets, which is unpacked to /target on build.

But @klieber, I was not able to get your workaround working. The entire contents of ${project.basedir} is included on the server, not just what I specify in . Any idea? Are you excluding anything? Does this still work for you with 1.3.1.1?

Thanks

[AGresvig]

I was able to get @klieber 's approach working for this now, but I can't say its optimal, as assets get very clunky paths on the jasmine bdd server.. Example: localhost:8234/src/target/MyApp-1.2-SNAPSHOT/assets/js/app/app.js..

Has anyone gotten a slicker workaround to using multiple source-dirs?

[AGresvig]

This would give us exactly what we need: #162
Is it in the roadmap for next release?