I am Ivan and I am contributing to the JBoss Forge project. Right now I am
working on a task to build tool's javadoc (and sources as well) and
aggregate them in a couple of archives.
I did some experiments, but at the end the build used to create too much
garbage in the project directories. So I was advised by one of our core
committers (George Gastaldi) to look at the Seam 3 build.
I checked it and found that the following projects have some javadoc
dist / seam
I merely copied the configurations from the respective pom.xml files. And
when ran the Forge build, I got the javadocs (and sources) built for each
of our modules, but didn't find any big aggregate archive anywhere.
Could you please tell me, do I miss anything? Which are actually the seam
modules and projects that I should look at?
Tnks Jason and Daniel.
That was exactly what i was hopping to hear it.
I think that it's a huge step to help the developers to migrate their
So, the natural step from Seam 2.x user's would be:
1 - Seam 2.3, with JSF2, JPA2, Richfaces 4.x or Primefaces 3.x
2 - The next step would be moving to CDI.
3 - Then, on the near future, add Apache DeltaSpike
Do you guys agree?
On Fri, Sep 28, 2012 at 2:56 PM, Daniel Hinojosa <
> I personally can't see Seam 3.x modules being used in Seam 2.3 unless you
> instantiate all the relevant classes in your components.xml and wire them
> that way. I am not aware of any bridge and maybe Marek can address some
> more specifics to that, or maybe correct my statement.
> On Fri, Sep 28, 2012 at 11:29 AM, Raphael Lacerda <lacerdaph(a)gmail.com>wrote:
>> Ok.. Great news about Seam 2.3! i'm looking for to try it!
>> But i've a dummy question..
>> Seam 3 is about modules that provide support for JSF2 and CDI. It
>> suffered a lot out criticism/misunderstanding (
>> http://in.relation.to/Bloggers/SeamNextAnnouncement) because the seam
>> developers were used to a fully integrated framework, not pluggable modules.
>> So, did Seam 2.3 come to provide a fully integrated framework instead of
>> How it's gonna be?
>> Will I be able to use Seam 2.3 with some Seam 3.x's modules? Or all
>> Seam3.x's features will be already available in Seam 2.3?
>> Raphael Lacerda
>> On Wed, Sep 19, 2012 at 11:50 AM, Gunvaldson, John <jgunvaldson(a)ucsd.edu>wrote:
>>> By far the largest chunk is going to be migrating to JSF 2
>>> And by far, the greatest opportunity for advancing your Seam 2.2
>>> applications into the future. Finally, a migration path to JSF 2 is
>>> available without a huge rewrite. IE 9 problems relating to old Richfaces
>>> libraries can be attended to (instead of just patched). I am so looking
>>> forward to moving out of Richfaces 3.3 into 4+, as well as leveraging the
>>> JSF 2 enhanced templating features, so much more. The opportunity to move
>>> our Jboss application server version forward to 7, in itself, is hugely
>>> Thank You Marek!
>>> John Gunvaldson
>>> San Diego, CA
>>> seam-dev mailing list
>> seam-dev mailing list
> Daniel Hinojosa
> Programmer, Instructor, and Consultant