[jboss-dev-forums] [JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool

[alesj]

"alesj" wrote : 
  | I guess you now do this explicitly in maven?
  | 
Ah, I see now what you've done.

  |       <plugin>
  |         <groupId>org.apache.maven.plugins</groupId>
  |         <artifactId>maven-antrun-plugin</artifactId>
  |         <version>1.2</version>
  |         <executions>
  |           <execution>
  |             <id>create-test-jars</id>
  |             <goals>
  |               <goal>run</goal>
  |             </goals>
  |             <phase>process-test-classes</phase>
  |             <configuration>
  |               <tasks>
  |                 <property name="test.jar.suffix" value="-test-classpool-"/>
  |                 <property name="archive.dir" value="${project.build.directory}/archives"/>
  |                 <mkdir dir="${archive.dir}"/>
  |                 <jar destfile="${archive.dir}/a1.jar"
  |                   basedir="${project.build.testOutputDirectory}" 
  |                   includes="org/jboss/test/classpool/support/excluded/a/*.class"/>
  | 

Well, this works too, but, as it's shows, it makes harder to test/debug tests. 
I thought you would use VFS's Assembled notion.
Or is there a valid reason you didn't?

To simplify + speed-up things, what you can do,
is to put this created artifacts directly into test's resources.
(they will get copied to the proper location by any env)
Then all you need to do is to add programmatic exclusion of test classes.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268390#4268390

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268390