<p>I am willing to convert seam JCR to this to see how it runs.</p>
<p>John</p>
<div class="gmail_quote">On Aug 20, 2011 7:17 PM, "George Gastaldi" <<a href="mailto:gegastaldi@gmail.com">gegastaldi@gmail.com</a>> wrote:<br type="attribution">> +1 to the multiple sources idea<br>> <br>
> Em 20/08/2011, ās 20:01, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> escreveu:<br>> <br>> We could possibly do it by specifying additional source directories for each<br>> profile.<br>
> <br>> <a href="http://chadthedeveloper.blogspot.com/2008/02/maven2-multiple-source-directories-and.html">http://chadthedeveloper.blogspot.com/2008/02/maven2-multiple-source-directories-and.html</a><br>> <br>> On 21/08/11 08:59, Jason Porter wrote:<br>
> <br>> Can we add additional tests with this though for each container?<br>> <br>> Sent from my iPhone<br>> <br>> On Aug 20, 2011, at 16:35, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br>
> <br>> That might be one way we can do it - Ken, what do you think about<br>> structuring the test suite like this?<br>> <br>> <a href="https://gist.github.com/1155271">https://gist.github.com/1155271</a><br>
> <br>> <br>> On 21/08/11 08:27, Jason Porter wrote:<br>> <br>> Maybe something in surefire, or what aslak said on twitter may be helpful.<br>> <br>> Sent from my iPhone<br>> <br>> On Aug 20, 2011, at 16:21, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br>
> <br>> I'm currently looking into it.<br>> <br>> On 21/08/11 08:04, Jason Porter wrote:<br>> <br>> Is it possible to add a source directory or test directory?<br>> <br>> Sent from my iPhone<br>
> <br>> On Aug 20, 2011, at 15:36, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br>> <br>> Unfortunately that doesn't work - the issue occurs when the artifacts<br>
> being unpacked are in the same reactor. See<br>> <a href="http://jira.codehaus.org/browse/MDEP-98">http://jira.codehaus.org/browse/MDEP-98</a><br>> <br>> On 21/08/11 01:11, Ken Finnigan wrote:<br>> <br>> If I'm not mistaken, that error is resolved by installing the artifacts.<br>
> <br>> The problem is that it doesn't know how to unpack a directory, so the jar<br>> with the test classes needs to be installed for it to work<br>> <br>> Ken<br>> <br>> Sent from my iPhone<br>
> <br>> On Aug 20, 2011, at 11:02, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br>> <br>> I've made some progress in this area, so far I've created a few of the<br>
> container boms in seam-parent and also started converting the Solder tests<br>> to use the new structure.<br>> <br>> I have run into one issue though - when running the tests I'm encountering<br>> the error below. The reason it hasn't manifested in the International<br>
> module is because there was a version mismatch between some of the test<br>> suite artifacts, however if you synchronize them all you get the same error.<br>> <br>> [INFO] Reactor Summary:<br>> [INFO]<br>
> [INFO] Seam International Test Suite: Aggregator ......... SUCCESS [1.224s]<br>> [INFO] Seam Container BOMs Aggregator .................... SUCCESS [0.025s]<br>> [INFO] Weld EE Embedded 1.1 Container .................... SUCCESS [0.899s]<br>
> [INFO] JBoss AS7 Managed Container ....................... SUCCESS [2.722s]<br>> [INFO] Seam International Test Suite Common .............. SUCCESS [0.376s]<br>> [INFO] Seam International Test Suite: Internals Integration Tests SUCCESS<br>
> [0.013s]<br>> [INFO] Seam International Test Suite: Internals Integration Tests Base<br>> SUCCESS [0.743s]<br>> [INFO] Seam International Test Suite: Internals Integration Tests for JBoss<br>> AS FAILURE [2.529s]<br>
> [INFO] Seam International Test Suite: Internals Integration Tests for Weld<br>> EE Embedded SKIPPED<br>> [INFO]<br>> ------------------------------------------------------------------------<br>> [INFO] BUILD FAILURE<br>
> [INFO]<br>> ------------------------------------------------------------------------<br>> [INFO] Total time: 9.393s<br>> [INFO] Finished at: Sun Aug 21 00:55:38 EST 2011<br>> [INFO] Final Memory: 25M/348M<br>
> [INFO]<br>> ------------------------------------------------------------------------<br>> [ERROR] Failed to execute goal<br>> org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack<br>> (unpack-base-tests) on project<br>
> seam-international-testsuite-integration-internals-jbossas: Error unpacking<br>> file:<br>> /home/shane/project/seam/international/testsuite/internals/base/target/classes<br>> to:<br>> /home/shane/project/seam/international/testsuite/internals/jbossas/target/test-classes<br>
> [ERROR] org.codehaus.plexus.archiver.ArchiverException: The source must not<br>> be a directory.<br>> [ERROR] -> [Help 1]<br>> <br>> <br>> I've spent a little time trying to find a workaround but it seems that this<br>
> has been a known bug in Maven for at least 4 years. If anyone wants to take<br>> a look at this and try to figure out a workaround in the meantime please be<br>> my guest.<br>> <br>> Shane<br>> <br>> <br>
> On 30/07/11 12:16, Ken Finnigan wrote:<br>> <br>> All,<br>> <br>> I've committed the work on the Arquillian testsuite infrastructure on the<br>> i18n module which can be found here:<br>> <a href="https://github.com/seam/international/tree/develop/testsuite">https://github.com/seam/international/tree/develop/testsuite</a><br>
> <br>> Here are some notes on how it's structured and what needs to be done:<br>> <br>> <br>> - API and Impl modules still retain unit tests that don't require<br>> container testing<br>> - testsuite/common includes Deployment and Library helpers and anything<br>
> that would be common to multiple types of testsuites, such as internals,<br>> smoke, etc<br>> - The helpers from this module could potentially be pulled up into a<br>> common module for all, but that may introduce complexity in<br>
> trying to use it<br>> in each module so may be best to leave it there for the moment<br>> and see how<br>> it goes<br>> - testsuite/container-boms contains the container definition for weld ee<br>
> embedded and AS7. Others can be found at<br>> <a href="https://github.com/mojavelinux/arquillian-showcase/tree/master/container-boms">https://github.com/mojavelinux/arquillian-showcase/tree/master/container-boms</a><br>
> - One of the first things that needs to happen is these container-boms<br>> need to be created in a seam parent module of some kind such that each<br>> module can utilize them without having to replicate the content directly<br>
> - testsuite/internals/base contains the test classes that used to be<br>> within impl. For i18n I was able to leave the entirety of the test classes<br>> in the bases module and simply explode it into the target/test-classes<br>
> directory of the testsuite/internals/${container} modules as part of the<br>> integration-test phase.<br>> - To make it easier to then explode the jar built from this module<br>> into sub modules, the test classes and resources actually need to be in<br>
> src/main. As we don't plan using the jar built from this for<br>> anything other<br>> than testing it's not an issue.<br>> - container tests are only activated on the integration-test phase<br>
> and skipped on the basic test phase<br>> - <a href="https://github.com/seam/international/blob/develop/testsuite/README.mdoutlines">https://github.com/seam/international/blob/develop/testsuite/README.mdoutlines</a><br>
> all the proposed types of suites that testsuite can contain. I<br>> believe an initial first step should be to move the existing container<br>> tests, or create some, for the internals module. Over time we can then look<br>
> to flesh out the testsuite with additional types such as smoke, cluster,<br>> api, etc<br>> - One area that I haven't looked at yet is code coverage given that the<br>> tests are further spread than previously. I'm hoping that it will be<br>
> relatively easy to amalgamate all the coverage data to produce a single<br>> report.<br>> <br>> Any questions about this please let me know.<br>> <br>> Ken<br>> <br>> <br>> _______________________________________________<br>
> seam-dev mailing<br>> listseam-dev@lists.jboss.orghttps://<a href="http://lists.jboss.org/mailman/listinfo/seam-dev">lists.jboss.org/mailman/listinfo/seam-dev</a><br>> <br>> <br>> <br>> _______________________________________________<br>
> seam-dev mailing list<br>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
> <br>> <br>> <br>> <br>> _______________________________________________<br>> seam-dev mailing list<br>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div>