Preparing for 1.0.0.Final

[dan.j.allen]

We're preparing for the first final release of Arquillian, 1.0.0.Final! (Hmm, perhaps I should have warned you to sit down first if that caused you to faint). This release showcases the dedicated work of many people and we want to be sure you're all a part of it.

You can read the details of this mission on the following wiki page - Mission: 1.0.0.Final Release.

Here's the gist of the plan:

1. Double check information (guides, website, documentation) for accuracy - (just pick a few things to focus on)
2. Try out the guides and make sure they led to a green bar
3. Write a blog entry about your take / perspective on the final release
4. Make some NOISE on release day!

Feel free to post your thoughts, ideas and where you want to help out on this thread. We'll keep the wiki page updated as a summary of where we stand.

Thanks for your hard work and dedication to Arquillian. This release is an opportunity to showcase your work. Let's make it count.

[dan.j.allen]

We're also planning to have an after release party. We've been having a lot of fun lately with Google Hangout (and it's open source equivalent BigBlueButton). We need to decide when and where, make sure you have the food or drink you enjoy most in hand and we can have fun chatting about the past, present and future of Arqullian.

[davided80]

Sounds like a great idea.

About the documentation,  I think the reference for JBoss 4.2 Container is missing: https://docs.jboss.org/author/display/ARQ/Complete+Container+Reference

Cheers,

Davide

[aslak]

downside with g+ of course is the 10 participants limitation..

[dan.j.allen]

Yep, that just keeps hitting us. There is possibility of daisy chaining the hangouts...I might give that a few minutes of trail and error this weekend. Another approach is to get the BigBlueButton virtual machine running somewhere we can all connect to. If the VM really does run out of the box, then anyone with a decent network connection should be able to host it for the event. Again, something to play with, but not spend too much time on.

[dan.j.allen]

Thanks for the feedback David. I'll be doing a review of the documentation later today and post a list of things that need to be done. I'll add that to the list.

[dan.j.allen]

Quick update. I have reached out to all the contacts on the media list and heard back. All positive. The ball is now in our court to get them an announcement to post. I'll be working on that with Sarah. They are also interested in links to any and all blogs releated to the release, so start thinking about what you want to write.

[vineet.reynolds]

I think the guide about using Ant+Ivy with Arquillian needs to be fleshed out.

Also, the list of supported containers for Tomcat needs fixing, and the associated Container Reference pages need to be created. What's missing-

• listing Tomcat Managed 5.5 and Tomcat Managed 7.0 as supported containers
• adding a container reference pages for the above two containers.

I'll add these in, but I might need help in the snippets for the "Maven profile setup" sections.

[dan.j.allen]

Vineet Reynolds wrote:

I think the guide about using Ant+Ivy with Arquillian needs to be fleshed out.

That came up during my review of the docs yesterday. Currently the section is just a pointer to somewhere else. I'm inclined to remove the section--perhaps make it an FAQ--until it has worthwhile content (so as not to mislead the reader). I don't think it's a blocker for the release, but something we should have within a week or two after. The first step is to create an issue if there isn't already one, then try to get volunteers to write it up.

Of course, it can build on what I put together in the showcase. But there are also reports in the forums of people getting it working that might want to write it up:

https://community.jboss.org/thread/160986

Also, there is value in having a section on how to use Arquillian w/o a build (such as in a pure Eclipse project). I've been asked about that many times.

http://www.dzone.com/links/r/integration_testing_using_arquillian_without_maven.html

Also, the list of supported containers for Tomcat needs fixing, and the associated Container Reference pages need to be created. What's missing-

• listing Tomcat Managed 5.5 and Tomcat Managed 7.0 as supported containers
• adding a container reference pages for the above two containers.

I'll add these in, but I might need help in the snippets for the "Maven profile setup" sections.

Can you add the Tomcat containers? If not, I can ask Ian to add them since he's been working on them.

+1 to adding links to the container reference pages. I'll make sure to double check all those when revising the docs. At that point I can review the Maven profile entries.

(and yes, I can hear Aslak thinking....we need all the profiles to be hit during a test...that's definitley an asap task after the release).

[dan.j.allen]

As promised, I will state my plan to overhaul the documentation.

My overall goal is to trim, trim, trim. There is a lot of non-normative (background) documentation that is aging, repeated elsewhere and not needed in the reference guide. I plan to save the good bits for the website or a consolidated section, and nuke the rest. The sections that will remain mostly intact are those that begin with "Complete " ...since they are the actual reference.

Here's the outline I'm shooting for:

• Introduction
  • Super brief intro statement
  • Integration testing in Java EE (motivation)
  • How it works?
  • Architecture
• Getting Started
  • One sentence explanation and link to guides on arquillian.org (the menu item is there to draw attention to the existence of the guides)
• Containers
  • Super brief intro of what we mean by containers & the role they play
  • Container selection
  • Container configuration
  • Supported containers

• Additional features (currently "Advance use cases")
  • Method injection (new)
  • Run modes
  • Descriptor deployment
  • ArquillianResource injection
  • Multiple deployments
  • Multiple containers
  • Protocol selection
• Extensions
  • Drone
  • Seam 2
  • Performance
• Appendix
  • Test enrichers (the purpose of this section is just some "important things to know about a few test enrichers)
    • EJB
    • CDI
    • Scopes
  • Containers
    • (current list as is)
  • Protocols
    • (current list as is)
  • Build integration
    • Maven (mostly just a statement that it's the preferred approach)
    • Ant+Ivy <- only if it's ready in time
    • Gradle
    • No dep management <- only if it's ready in time

I don't plan to write much new material...only revise and cut.

The "test execution" section I'm going to remove and turn into a guide for the website. The JSFUnit section just needs to be killed because it's misleading and sends the user on a wild goose chase. When I'm done, it should be much easier to manage and also more clear how we can automate most of it in the not to distant future.

Sound reasonable? I'll begin the edits in a few hours.

[aslak]

IronJacamar use Ant+Ivy.. if 'inspiration' is needed.. http://anonsvn.jboss.org/repos/jbossas/projects/jboss-jca/trunk/ivy.xml

[aslak]

Dan Allen wrote:

(and yes, I can hear Aslak thinking....we need all the profiles to be hit during a test...that's definitley an asap task after the release).

Almost....

This is pure data duplication.. moving data from the pom to doc. We need to get this into our Arq Site Model and generate the docs..

[aslak]

sounds good..

[dan.j.allen]

I need to get an idea of what will be part of the 1.0.0.Final "release train". I'm assuming it's going to be something like this:

• Arquillian Core
• Arquillian Drone
• Containers ready to go
  • JBoss AS (4 - 6)
  • Weld
  • GlassFish
  • Jetty
  • Tomcat
  • OpenWebBeans
  • OpenEJB
  • OSGi
• Forge plugin? At least something we can call stable here since it is used in the guides.

If we decide to hold on containers, I'm fine with that. As long as the containers we use in the first two guides are released, that's really what matters.

Btw, OpenEJB hasn't been released since Alpha5, so technically it's really out of sync. Perhaps a CR of that one over the weekend would be a good idea.

[dan.j.allen]

I've created a Google Doc with the release notes. Let me know if you want to participate in reviewing it. I'm refraining from posting it online so that the media channels don't jump the gun on us