On 23 Jan 2012, at 11:01 PM, Steve Ebersole wrote:
> Ok, so it does do some filtering. However...
>
> task copyBundleResources (type: Copy) {
> ext.bundlesTargetDir = file( "${buildDir}/bundles" )
> from file('src/test/bundles')
> into bundlesTargetDir
> filter(ReplaceTokens, tokens
Ok, so it does do some filtering. However...
task copyBundleResources (type: Copy) {
ext.bundlesTargetDir = file( "${buildDir}/bundles" )
from file('src/test/bundles')
into bundlesTargetDir
filter(ReplaceTokens, tokens: [
buildDirName: buildDir.absolutePath,
Not in the one I looked at. But good point, I'll look at the others.
On Thu 16 Aug 2012 03:18:30 AM CDT, Hardy Ferentschik wrote:
> Does it not do some filtering as well when the copy occurs. That's the only
> thing I can think which would prevent us to use the src/test bundles.
>
> --hardy
>
>
Does it not do some filtering as well when the copy occurs. That's the only
thing I can think which would prevent us to use the src/test bundles.
--hardy
On 15 Aug 2012, at 19:50, Steve Ebersole wrote:
> Forgot to mention, the reason I am asking is that the current set up
> makes it more d
Forgot to mention, the reason I am asking is that the current set up
makes it more difficult to test in IDE. If you change one of these
src/test/bundles files, you have to switch to command line, run gradle
compilation (because it is a custom gradle task that copies the files
over) before I ca
org.hibernate.jpa.test.packaging.PackagingTestCase uses ShrinkWrap to
facilitate "packaged" JPA tests. It uses metadata from
src/test/bundles, BUT it gets the copies moved over to target/bundles.
I am curious why it uses the target/bundles copy rather than the
src/test/bundles original?
--
