Another option I've thought of is creating our own Maven plugin that does a similar job to unpack, but allows specifying which src dirs to link to in a project. Then see if the JBossTools guys can write an m2e addition that interprets the plugin correctly in the IDE to link the src dirs that were set in the configuration.


Sent from my iPhone

On Sep 7, 2011, at 18:11, Dan Allen <> wrote:

Thanks for the assessment of the test setup. I'm going to look it over, hopefully sitting down with Aslak at next weeks f2f and really exploring the problem in every way we can. I think we are close to the right solution, but I still want to consider some more options, even if it means modifications to Arquillian to make it work.


On Wed, Sep 7, 2011 at 15:51, Ken Finnigan <> wrote:
Unfortunately I won't be able to make the seam-dev meeting today, I'm blaming it on the newborn! ;-)

To briefly mention the below agenda item regarding the testsuite, we've found out that the best solution is to use the unpack plugin for Maven as part of the build process to take the tests from the base module and add them into the test-classes of a container specific module so that Surefire will pick them up for testing.

The major problem was always the IDE.  I think Jason has discovered a solution for IDEA, and I found one for Eclipse.  The Eclipse solution is within the container specific module for the testsuite to "link source" for that project and link to the src/main/java and src/main/resources of the base project module.  Doing this enables you to execute a single test, or all the tests in the module, against the specific container of that module.  Another added bonus is that editing the test classes that have been linked modifies them within the base module src path, ensuring that changes are not lost and are committed to where they need to be.

The one downside to the above approach for Eclipse is that running Maven -> Update Project Configuration removes the source linkages that have been added within the IDE.  I haven't had a chance to investigate this yet, but I'm hoping it's possible to script the link source commands so that we can provide those scripts with the modules to make it easy to add them back.

Any questions or concerns please drop me a mail.

If there's anything from the meeting that I need to look at please let me know.


On Tue, Sep 6, 2011 at 4:03 PM, Jason Porter <> wrote:
  • Follow-up from the last meeting (10 min)
    • Cloudbees
    • Docs
    • Mail Tests
  • Hack Night: Faces (10 min)
  • Next Seam 3 release (15 min)
    • I believe the next one is CR1
    • Discuss moving to the testing structure (Ken and I believe we have the bugs ironed out)
  • Next week's meeting (5 min)
    • All Seam devs will be having a meeting, may hold off

Jason Porter

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at:,

seam-dev mailing list

seam-dev mailing list

Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597