<html><body bgcolor="#FFFFFF"><div>Is it possible to add a source directory or test directory?<br><br>Sent from my iPhone</div><div><br>On Aug 20, 2011, at 15:36, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
Unfortunately that doesn't work - the issue occurs when the
artifacts being unpacked are in the same reactor. See <a href="http://jira.codehaus.org/browse/MDEP-98"><a href="http://jira.codehaus.org/browse/MDEP-98">http://jira.codehaus.org/browse/MDEP-98</a></a><br>
<br>
On 21/08/11 01:11, Ken Finnigan wrote:
<blockquote cite="mid:5348BD29-A3D4-4521-BAF9-796B267FB637@kenfinnigan.me" type="cite">
<div>If I'm not mistaken, that error is resolved by installing the
artifacts.</div>
<div><br>
</div>
<div>The problem is that it doesn't know how to unpack a
directory, so the jar with the test classes needs to be
installed for it to work</div>
<div><br>
</div>
<div>Ken<br>
<br>
Sent from my iPhone</div>
<div><br>
On Aug 20, 2011, at 11:02, Shane Bryzak <<a moz-do-not-send="true" href="mailto:sbryzak@redhat.com"><a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a></a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div> I've made some progress in this area, so far I've created
a few of the container boms in seam-parent and also started
converting the Solder tests to use the new structure.<br>
<br>
I have run into one issue though - when running the tests I'm
encountering the error below. The reason it hasn't manifested
in the International module is because there was a version
mismatch between some of the test 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 [0.013s]<br>
[INFO] Seam International Test Suite: Internals Integration
Tests Base SUCCESS [0.743s]<br>
[INFO] Seam International Test Suite: Internals Integration
Tests for JBoss AS FAILURE [2.529s]<br>
[INFO] Seam International Test Suite: Internals Integration
Tests for Weld EE Embedded SKIPPED<br>
[INFO]
------------------------------------------------------------------------<br>
[INFO] BUILD FAILURE<br>
[INFO]
------------------------------------------------------------------------<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>
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack
(unpack-base-tests) on project
seam-international-testsuite-integration-internals-jbossas:
Error unpacking file:
/home/shane/project/seam/international/testsuite/internals/base/target/classes
to:
/home/shane/project/seam/international/testsuite/internals/jbossas/target/test-classes<br>
[ERROR] org.codehaus.plexus.archiver.ArchiverException: The
source must not 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 has been a known bug in Maven for at least 4
years. If anyone wants to take a look at this and try to
figure out a workaround in the meantime please be my guest.<br>
<br>
Shane<br>
<br>
<br>
On 30/07/11 12:16, Ken Finnigan wrote:
<blockquote cite="mid:CAKeeVe4bmcC6rTeOk7oU+A1gxTQANJMBS8Z5KFBZeSaTZDRy2A@mail.gmail.com" type="cite">All,<br>
<br>
I've committed the work on the Arquillian testsuite
infrastructure on the i18n module which can be found here: <a moz-do-not-send="true" href="https://github.com/seam/international/tree/develop/testsuite"><a href="https://github.com/seam/international/tree/develop/testsuite">https://github.com/seam/international/tree/develop/testsuite</a></a><br>
<br>
Here are some notes on how it's structured and what needs to
be done:<br>
<br>
<ul>
<li>API and Impl modules still retain unit tests that
don't require container testing</li>
<li>testsuite/common includes Deployment and Library
helpers and anything that would be common to multiple
types of testsuites, such as internals, smoke, etc</li>
<ul>
<li>The helpers from this module could potentially be
pulled up into a common module for all, but that may
introduce complexity in trying to use it in each
module so may be best to leave it there for the moment
and see how it goes</li>
</ul>
<li>testsuite/container-boms contains the container
definition for weld ee embedded and AS7. Others can be
found at <a moz-do-not-send="true" href="https://github.com/mojavelinux/arquillian-showcase/tree/master/container-boms"><a href="https://github.com/mojavelinux/arquillian-showcase/tree/master/container-boms">https://github.com/mojavelinux/arquillian-showcase/tree/master/container-boms</a></a></li>
<ul>
<li>One of the first things that needs to happen is
these container-boms need to be created in a seam
parent module of some kind such that each module can
utilize them without having to replicate the content
directly</li>
</ul>
<li>testsuite/internals/base contains the test classes
that used to be within impl. For i18n I was able to
leave the entirety of the test classes in the bases
module and simply explode it into the
target/test-classes directory of the
testsuite/internals/${container} modules as part of the
integration-test phase.</li>
<ul>
<li>To make it easier to then explode the jar built from
this module into sub modules, the test classes and
resources actually need to be in src/main. As we
don't plan using the jar built from this for anything
other than testing it's not an issue.<br>
</li>
</ul>
<li>container tests are only activated on the
integration-test phase and skipped on the basic test
phase</li>
<li><a moz-do-not-send="true" href="https://github.com/seam/international/blob/develop/testsuite/README.md"><a href="https://github.com/seam/international/blob/develop/testsuite/README.md">https://github.com/seam/international/blob/develop/testsuite/README.md</a></a>
outlines all the proposed types of suites that testsuite
can contain. I believe an initial first step should be
to move the existing container tests, or create some,
for the internals module. Over time we can then look to
flesh out the testsuite with additional types such as
smoke, cluster, api, etc</li>
<li>One area that I haven't looked at yet is code coverage
given that the tests are further spread than
previously. I'm hoping that it will be relatively easy
to amalgamate all the coverage data to produce a single
report.</li>
</ul>
Any questions about this please let me know.<br>
<br>
Ken<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
seam-dev mailing list
<a moz-do-not-send="true" href="mailto:seam-dev@lists.jboss.org"><a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a></a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/seam-dev"><a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a></a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>seam-dev mailing list</span><br><span><a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a></span><br></div></blockquote></body></html>