I've put together the definitive list of contributor names to go in the
bundled Seam documentation. Could you please review this list
thoroughly and let me know if I've missed anyone. The last thing I
would want to get wrong for the final release is to not give a
* Gavin King (Project Founder)
* Shane Bryzak (Project Lead)
* Pete Muir (former Project Lead)
* Dan Allen (Community Liaison)
* John Ament
* Max Rydahl Andersen
* Jay Balunas
* Christian Bauer
* Lincoln Baxter III
* Emmanuel Bernard
* Mike Brock
* Stuart Douglas
* Matt Drees
* Ken Finnigan
* Denis Forveille
* José Freitas
* Jordan Ganoff
* George Gastaldi
* Martin Gencur
* Jozef Hartinger
* Peter Hilton
* Ales Justin
* Nicklas Karlsson
* Marcel Kolsteren
* Brian Leathem
* Cody Lerum
* Gunnar Morling
* Marek Novotny
* Jacob Orshalick
* James Perkins
* Clint Popetz
* Jason Porter
* Karel Piwko
* Ove Ranheim
* Norman Richards
* Daniel Roth
* Antoine Sabot-Durand
* Sebastian Sachtleben
* Amir Sadrinia
* Ondr(ej Skutka
* Mark Struberg
* Tihomir Surdilovic
* Mike Youngstrom
* Michael Yuan
Hi Shane / others!
As the Seam 3 Final release is closing in, I'm starting to be a bit concerned about the release process. Currently, CRs are first tagged, released and afterwards go through the testing process. This is not ideal since we can end up having the final release buggy. I can see two possibilities to overcome this.
a) first tag the release, then test it and then release it
b) do CRs until we are satisfied with it and then switch the latest CR to Final *without* any commits
I'm in favor of (b), having the advantage of community testing. WDYT?
I'm trying to deploy the seam-booking example in WebSphere v8 beta without succes now
One of the problem is that the class "org.jboss.logging.JBossLogManagerLogger" (In seam-solder.jar) needs org.jboss.logmanager.Logger
I can not find this class in the CR2 distribution
Has this class been forgotten or is it a hard dependency on some JBoss-AS lib?
I've released all of the Maven artifacts and uploaded the bundled
distribution to sourceforge. I'll write the release announcement
tomorrow, and tie up all the other loose ends (version releases in JIRA,
individual module distributions, etc) however the testing can now get
started on CR3.
For reference, we're up to version 3.0.0.CR9 now for the seam-bom:
I'll start the discussions going over what's still remaining for the
final release in the next day or so.
Thanks everyone for all the hard work that went into CR3, we're almost
Hi Seam Developers,
Just to let you know my interest on Seam and JBPM5.
I couldn't find anything regarding jBPM5 + Seam but I'd like to try it
somehow, as an user, not as a developer.
Thanks a lot :)
JQuantLib is a library for Quantitative Finance written in Java.
Before I can do the CR3 release for seam-bom (and the bundled release),
I need to know which modules are ready for final release, and which ones
are going to have a CR2 release. The following list contains all of the
modules, along with the *assumed* version. If any of my version
assumptions are wrong, can you please correct me ASAP (or vice-versa, if
the assumptions are correct then please confirm that also).
After much deliberation we've decided to do a CR3 release this weekend
and postpone the final release for one more week. This is due to a
number of reasons, mainly being significant code changes that we've made
recently (such as refactoring the transactions API and improvements to
logging) and work done to address compatibility issues with Glassfish.
I believe these changes are substantial enough to warrant another CR
release to allow for additional testing, to ensure that we will be
releasing a quality product in Seam 3.0 Final.
For most of the modules this decision won't have any significant impact,
we can proceed to release final versions of them as planned. For the
modules that are affected (off the top of my head - Solder,
International, Persistence, Servlet, Security) we will do one more CR
release to include in CR3, then if everything looks ok we'll then go to
Please let me know if you have any questions.
That's great to hear. To contribute to Seam, you need to follow the
instructions in the following guide:
I've cc'd the seam-dev mailing list so that everyone is aware that
you'll be translating documentation. After you submit the pull request
in github, the module lead for each respective module will be able to
merge your documentation into the master Seam repository.
On 14/03/11 18:58, 光子 wrote:
> Hi Shane Bryzak !
> Here is my plan:
> 1. *Forge(Seam tools)*
> 2. *Config Modules*
> 3. *Persistence Modules*
> 4. *Servlet Modules*
> 5. *Security Modules*
> 6. Pending...
> 2011/3/11 Shane Bryzak <sbryzak(a)redhat.com <mailto:email@example.com>>
> Hi Kuuyee,
> Thank you for your offer to contribute to Seam by providing
> translations. Are there any particular Seam 3 modules that you
> would like to work on translations for?
> On 11/03/11 19:20, 光子 wrote:
>> Hi Shane Bryzak !
>> I am a fan of Seam/Weld ,I already send eamil to Pete Muir for
>> Seam/Weld document translation.and has applied to the Contributor
>> License Agreements. so I want to request commit access to the
>> Seam/Weld repository.
>> My jboss.org <http://jboss.org> username: kuuyee760726
>> My github username: kuuyee(a)gmail.com <mailto:firstname.lastname@example.org>
>> Awaiting your reply！Thanks！！！