[weld-dev] ref guide (re)draft ready

[Emmanuel Bernard]

You mean for example taking NumberGuess and enhance it? That's what  
Pete proposed as well.

On 2 nov. 09, at 18:09, Dan Allen wrote:

> Jason,
>
> Simply check out that branch of the SVN tree and type:
>
>  mvn
>
> Then, you can choose from either a PDF or HTML. The PDF ends up in  
> the current directory, the HTML in target/docbook/publish/en-US/html
>
> -Dan
>
> p.s. I tried to attach the PDF to the mailinglist, but it got  
> moderated because of its size
>
> p.p.s. Probably not a bad tip to point in either the ref guide or  
> the wiki.
>
> On Mon, Nov 2, 2009 at 11:47 AM, Jason Porter  
> <lightguard.jp at gmail.com> wrote:
> On Sun, Nov 1, 2009 at 21:33, Dan Allen <dan.j.allen at gmail.com> wrote:
> > I've made it all the way through the ref guide with revisions that  
> reflect
> > that changes to the RI and spec names and the latest nomenclature  
> and
> > semantics from the spec. It's now ready for a technical review and
> > proofreading (in trunk)
> >
> > https://svn.jboss.org/repos/weld/doc/trunk/reference
> > http://anonsvn.jboss.org/repos/weld/doc/trunk/reference
> >
> > Since there was so much to change, I'm sure there are places where  
> the
> > semantics didn't get properly updated or an explanation is still  
> out of
> > date. Also, there were some areas of the ref guide that were thin,  
> and I
> > didn't have time to fill it all in. If you feel comfortable  
> explaining a
> > topic, please don't be shy to revise or suggest revisions.
> >
> > Here are some notes to consider:
> >
> > - Java SE sections need review for accuracy, relevance
> > - Extending CDI (extend.xml) is extremely thin, to the point of  
> being
> > marginally useful compared to the spec
> > - Weld extensions (extensions.xml) is underwhelming; do we have  
> more to say
> > than just about logging?
> > - The chapter on producer fields (producerfields.xml) is missing,  
> though
> > producer fields are explained in intro.xml
> > - The Weld SPI needs to be reviewed for accuracy, relevance (ri- 
> spi.xml);
> > this was a *long* chapter and I just don't know the Weld SPI yet
> >
> > I did add a lot of content while revising, but the ref guide can  
> always be
> > improved.
> >
> > -Dan
> >
> > --
> > Dan Allen
> > Senior Software Engineer, Red Hat | Author of Seam in Action
> > Registered Linux User #231597
> >
> > http://mojavelinux.com
> > http://mojavelinux.com/seaminaction
> > http://www.google.com/profiles/dan.j.allen
> >
> > _______________________________________________
> > weld-dev mailing list
> > weld-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/weld-dev
> >
>
> I'd love to take a look through it (currently reading the spec), but
> I'd rather not read the XML files.  Is there a simple way to generate
> the PDF or the HTML files, or do I need to check everything out and
> build from there?
>
> --
> Jason Porter
> Real Programmers think better when playing Adventure or Rogue.
>
> PGP key id: 926CCFF5
> PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5
> PGP key available at: keyserver.net, pgp.mit.edu
>
>
>
> -- 
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20091102/5e8aa502/attachment.html