I've done #1.
--On Fri, Jan 21, 2011 at 15:50, Shane Bryzak <email@example.com> wrote:Realistically you probably have a couple more days before we sort out the Solder issues with Glassfish, I need to catch up with Dan first and find out what the current status is. If you could get the API changes done before then, then great, otherwise we'll have to make them between betas.As you are aware, we have to sort out the Solder issues on GlassFish. We want to solve this problem in the most efficient manner as possible, which we believe is by using Arquillian to get the Solder test suite to run on GlassFish (allowing us to work inside the IDE and debugger). We will target GlassFish 3.1-b37 or better. Once it passes, that will be our indication it works (plus some subsequent manual testing just to be sure).However, the remote GlassFish adapter for Arquillian based on JSR-88 was extremely fragile and when we leaned on it, it fell apart. So Jason Porter came through in a major way and implemented a new remote GlassFish adapter for Arquilian based on the admin REST API in GlassFish 3.1. I verified last night that it works and I pushed out a snapshot.What this means is that we can now comfortably debug the Arquillian tests, likely getting us there a heck of a lot faster. Here are the steps that need to be performed:1. Add the arquillian-glassfish-remote-3.1:1.0.0-SNAPSHOT profile to the Solder pom.xml2. Move all sources from api/ into impl/ (we will more gradually move sources to the api/ module once tests are passing on GlassFish)3. Work through the failing tests and figure out which ones are failing and get them fixed4. Merge Ken's logging changes (I think biting this bullet is important for the first Beta1)(anything I may be missing)I'll do #1 shortly and hopefully #2 before the end of the day (or I'll delegate it). #3 is work for the weekend or early next week. #4 should be quick once we solve the GlassFish issue.-DanDan AllenPrincipal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597