<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 23/08/2011, at 8:52 PM, Marek Schmidt wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Shane,<br><br>I have managed to run (more or less, with 1 failure and 4 errors) the <br>new Solder testsuite on AS7 (the jbossas-managed-7 profile)<br><br>with the following changes:<br><br>1. removing the <forkMode>always</forkMode> from <br>testsuite/internals/jbossas/pom.xml as it breaks the MavenArtifactResolver.<br><br>The other option for this issue is to hack the MavenArtifactResolver to <br>deal with the way surefirebooter works with forking, see the commented <br>out parts in MavenArtifactResolver.java in<br><br><a href="https://github.com/maschmid/solder/compare/develop">https://github.com/maschmid/solder/compare/develop</a>…testsuitecleanup<br></div></blockquote><div><br></div><div>Arquillian / Shrinkwrap have a proper non-hacky artefact resolver now (called MavenDependencyResolver), I am not really sure how to use it though, you would have to ask Aslak or ALR. </div><div><br></div><div>Stuart</div><br><blockquote type="cite"><div><br>2. add the "Dependencies: org.jboss.logging,org.jboss.logmanager" to the <br>seam-logger jar manifest, as no solder test archive gets deployed on AS7 <br>without it.<br><br>3. Upgrade arquillian.version and arquillian.jboss7.version to <br>1.0.0.CR4, as I get<br></div></blockquote><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>java.lang.NoClassDefFoundError: <br>org/jboss/arquillian/container/spi/client/protocol/metadata/JMXContext<br><br>exception with CR1 for some strange reason.<br><br><br></div></blockquote><div><br></div>The transitive dependencies have probably changed. I think that class is in arquillian-container-spi.</div><div><br></div><div>Stuart<br><div><br></div><br><blockquote type="cite"><div><br>(org.jboss.seam.solder.test.el.ElTest and <br>org.jboss.seam.solder.test.resourceLoader.ResourceLoaderTest are broken <br>because the "targetContainerAdapterClass" hack doesn't work anymore.<br><br><br>Cheers,<br><br>Marek Schmidt<br><br><br>On 08/22/2011 11:48 AM, Shane Bryzak wrote:<br><blockquote type="cite">Guys and girls,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">In the interest of moving things forward, I'm going to shortly start<br></blockquote><blockquote type="cite">working on the beta 2 release. There are still some issues that we're<br></blockquote><blockquote type="cite">working through with the multi-container testsuite configuration,<br></blockquote><blockquote type="cite">however with some help I've been able to resurrect the existing tests in<br></blockquote><blockquote type="cite">Solder to run in the latest version of Arquillian and I'm confident that<br></blockquote><blockquote type="cite">I can get the tests in the other modules passing successfully without<br></blockquote><blockquote type="cite">too much trouble. I would still like us to press on with the test suite<br></blockquote><blockquote type="cite">work, however I don't want it to hold up the release schedule.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Since the Beta1 release there have been a couple of important changes,<br></blockquote><blockquote type="cite">which I'll quickly summarise here:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">1) seam-parent is now at the top of the food chain and no longer<br></blockquote><blockquote type="cite">inherits its configuration from weld-parent. This change is good for a<br></blockquote><blockquote type="cite">couple of reasons, first of all the disassociation from the Weld project<br></blockquote><blockquote type="cite">will help to reinforce that Seam is CDI implementation-independent.<br></blockquote><blockquote type="cite">Secondly it gives us total control over configuration for the Maven<br></blockquote><blockquote type="cite">plugins that we use, allowing us to update the plugin versions (which<br></blockquote><blockquote type="cite">I've already done, to the latest version of each plugin) and fine tune<br></blockquote><blockquote type="cite">the plugin configuration parameters for Seam.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2) I've decided against moving the logging feature out of Solder and<br></blockquote><blockquote type="cite">into its own module for now, as I discovered that it was too tightly<br></blockquote><blockquote type="cite">coupled to Solder to "de-tangle" it easily. I have however refactored<br></blockquote><blockquote type="cite">the logging API classes into their own package, org.jboss.seam.logging<br></blockquote><blockquote type="cite">which I think will be more intuitive for our users. I believe that the<br></blockquote><blockquote type="cite">Solder reference documentation still needs to be updated in response to<br></blockquote><blockquote type="cite">the changes made for SOLDER-102<br></blockquote><blockquote type="cite">(<a href="http://issues.jboss.org/browse/SOLDER-102">http://issues.jboss.org/browse/SOLDER-102</a>) - Ken, could you please<br></blockquote><blockquote type="cite">confirm? If so, would you be willing to update the reference docs to<br></blockquote><blockquote type="cite">reflect the logging changes?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I am aiming for the Beta2 release this coming weekend, which means with<br></blockquote><blockquote type="cite">our 20+ modules now I need to get started pretty soon. If anyone has<br></blockquote><blockquote type="cite">any spare cycles and is able to help out with this, it would be greatly<br></blockquote><blockquote type="cite">appreciated. Each module needs to have its tests fixed, logging<br></blockquote><blockquote type="cite">refactored to use the new logging API package, and its distribution<br></blockquote><blockquote type="cite">thoroughly checked for correctness/completeness. If you'd like to<br></blockquote><blockquote type="cite">volunteer for a module or two, please catch me on IRC and we can work it<br></blockquote><blockquote type="cite">out there.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite">Shane<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">seam-dev mailing list<br></blockquote><blockquote type="cite"><a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br></blockquote><blockquote type="cite"><a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br></blockquote><br>_______________________________________________<br>seam-dev mailing list<br><a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/seam-dev<br></div></blockquote></div><br></body></html>