Seam 3

, ALWAYS prefix the id with your module name. For example, > or

id="security-getting-started">. As all of the chapters for all modules > are combined when building the bundled documentation, all IDs must be > unique. This is a particularly time consuming problem to fix because > the error output from the Maven docbook plugin doesn't tell you which > files are the problem ones. > > 3) When adding, renaming or deleting a chapter of your documentation, > please notify me of the changes so that I can update > bundled_master.xml. This file must be manually kept up to date whenever > any documentation changes are made. > > Thanks, > Shane > > > > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> > > > > > Seam 3 > Bundled Reference Guide > > > > > > Forge > > > > > > > > Seam Solder > > > > > > > > > > > > > > > > > > > Seam Configuration > > > > > > Seam Persistence > > > > > Seam Transaction > > > > > Seam Servlet > > > > > > > > > > Seam Security > > > > > > > > > Seam International > > > > > > > > > Seam Faces > > > > > > > > > > > Seam Catch > > > > > > > > > > Seam Reports > > > > > > > Seam Remoting > > > > > > > Seam REST > > > > > > > > > > > Seam JCR > > > > > > > > > Seam JMS > > > > > > > > > > Seam Validation > > > > > > > > Seam Wicket > > > > > > > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev From gegastaldi at gmail.com Thu Sep 1 19:31:25 2011 From: gegastaldi at gmail.com (George Gastaldi) Date: Thu, 1 Sep 2011 20:31:25 -0300 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: <4E6011FA.7010607@redhat.com> References: <4E5DB50C.3030409@redhat.com> <4E6011FA.7010607@redhat.com> Message-ID: <-7880943549841437954@unknownmsgid> Hi Shane, I still couldn't review the docs on Seam Reports, so I guess thats a nay for me. Regards, George Em 01/09/2011, ?s 20:15, Shane Bryzak escreveu: > Guys, I need a yea or nay on this for your module. > > On 31/08/11 14:14, Shane Bryzak wrote: >> Module leads, >> >> Can you please review the list below and confirm that the documentation >> chapters are correct for your module. Also, I would like everyone to >> take a moment to review the module documentation guidelines, as there >> were a number of breakages in the bundled documentation build because >> the guidelines weren't adhered to, particularly in the new modules for >> Seam 3.1: >> >> 1) Always prefix the filenames of your documentation chapters with the >> name of your module. E.g. security-authentication.xml, >> security-authorization.xml, etc. >> >> 2) Whenever you assign an ID to a docbook element, such as a >> or

, ALWAYS prefix the id with your module name. For example, >> or

> id="security-getting-started">. As all of the chapters for all modules >> are combined when building the bundled documentation, all IDs must be >> unique. This is a particularly time consuming problem to fix because >> the error output from the Maven docbook plugin doesn't tell you which >> files are the problem ones. >> >> 3) When adding, renaming or deleting a chapter of your documentation, >> please notify me of the changes so that I can update >> bundled_master.xml. This file must be manually kept up to date whenever >> any documentation changes are made. >> >> Thanks, >> Shane >> >> >> >> > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> >> >> >> >> >> Seam 3 >> Bundled Reference Guide >> >> >> >> >> >> Forge >> >> >> >> >> >> >> >> Seam Solder >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Seam Configuration >> >> >> >> >> >> Seam Persistence >> >> >> >> >> Seam Transaction >> >> >> >> >> Seam Servlet >> >> >> >> >> >> >> >> >> >> Seam Security >> >> >> >> >> >> >> >> >> Seam International >> >> >> >> >> >> >> >> >> Seam Faces >> >> >> >> >> >> >> >> >> >> >> Seam Catch >> >> >> >> >> >> >> >> >> >> Seam Reports >> >> >> >> >> >> >> Seam Remoting >> >> >> >> >> >> >> Seam REST >> >> >> >> >> >> >> >> >> >> >> Seam JCR >> >> >> >> >> >> >> >> >> Seam JMS >> >> >> >> >> >> >> >> >> >> Seam Validation >> >> >> >> >> >> >> >> Seam Wicket >> >> >> >> >> >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev From lightguard.jp at gmail.com Thu Sep 1 19:32:36 2011 From: lightguard.jp at gmail.com (Jason Porter) Date: Thu, 1 Sep 2011 17:32:36 -0600 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: <-7880943549841437954@unknownmsgid> References: <4E5DB50C.3030409@redhat.com> <4E6011FA.7010607@redhat.com> <-7880943549841437954@unknownmsgid> Message-ID: Catch should be fine. On Thu, Sep 1, 2011 at 17:31, George Gastaldi wrote: > Hi Shane, > > I still couldn't review the docs on Seam Reports, so I guess thats a nay > for me. > > Regards, > > George > > Em 01/09/2011, ?s 20:15, Shane Bryzak escreveu: > > > Guys, I need a yea or nay on this for your module. > > > > On 31/08/11 14:14, Shane Bryzak wrote: > >> Module leads, > >> > >> Can you please review the list below and confirm that the documentation > >> chapters are correct for your module. Also, I would like everyone to > >> take a moment to review the module documentation guidelines, as there > >> were a number of breakages in the bundled documentation build because > >> the guidelines weren't adhered to, particularly in the new modules for > >> Seam 3.1: > >> > >> 1) Always prefix the filenames of your documentation chapters with the > >> name of your module. E.g. security-authentication.xml, > >> security-authorization.xml, etc. > >> > >> 2) Whenever you assign an ID to a docbook element, such as a > >> or

, ALWAYS prefix the id with your module name. For example, > >> or

>> id="security-getting-started">. As all of the chapters for all modules > >> are combined when building the bundled documentation, all IDs must be > >> unique. This is a particularly time consuming problem to fix because > >> the error output from the Maven docbook plugin doesn't tell you which > >> files are the problem ones. > >> > >> 3) When adding, renaming or deleting a chapter of your documentation, > >> please notify me of the changes so that I can update > >> bundled_master.xml. This file must be manually kept up to date whenever > >> any documentation changes are made. > >> > >> Thanks, > >> Shane > >> > >> > >> > >> >> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> > >> > >> > >> > >> > >> Seam 3 > >> Bundled Reference Guide > >> > >> > >> > >> > >> > >> Forge > >> > >> > >> > >> > >> > >> > >> > >> Seam Solder > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Configuration > >> > >> > >> > >> > >> > >> Seam Persistence > >> > >> > >> > >> > >> Seam Transaction > >> > >> > >> > >> > >> Seam Servlet > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Security > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam International > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Faces > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Catch > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Reports > >> > >> > >> > >> > >> > >> > >> Seam Remoting > >> > >> > >> > >> > >> > >> > >> Seam REST > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam JCR > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam JMS > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Validation > >> > >> > >> > >> > >> > >> > >> > >> Seam Wicket > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> seam-dev mailing list > >> seam-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/seam-dev > > > > _______________________________________________ > > seam-dev mailing list > > seam-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110901/f40a7cbd/attachment-0001.html From ken at kenfinnigan.me Thu Sep 1 19:46:35 2011 From: ken at kenfinnigan.me (Ken Finnigan) Date: Thu, 1 Sep 2011 19:46:35 -0400 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: References: <4E5DB50C.3030409@redhat.com> <4E6011FA.7010607@redhat.com> <-7880943549841437954@unknownmsgid> Message-ID: International should be good Sent from my iPhone On Sep 1, 2011, at 19:32, Jason Porter wrote: > Catch should be fine. > > On Thu, Sep 1, 2011 at 17:31, George Gastaldi wrote: > Hi Shane, > > I still couldn't review the docs on Seam Reports, so I guess thats a nay for me. > > Regards, > > George > > Em 01/09/2011, ?s 20:15, Shane Bryzak escreveu: > > > Guys, I need a yea or nay on this for your module. > > > > On 31/08/11 14:14, Shane Bryzak wrote: > >> Module leads, > >> > >> Can you please review the list below and confirm that the documentation > >> chapters are correct for your module. Also, I would like everyone to > >> take a moment to review the module documentation guidelines, as there > >> were a number of breakages in the bundled documentation build because > >> the guidelines weren't adhered to, particularly in the new modules for > >> Seam 3.1: > >> > >> 1) Always prefix the filenames of your documentation chapters with the > >> name of your module. E.g. security-authentication.xml, > >> security-authorization.xml, etc. > >> > >> 2) Whenever you assign an ID to a docbook element, such as a > >> or

, ALWAYS prefix the id with your module name. For example, > >> or

>> id="security-getting-started">. As all of the chapters for all modules > >> are combined when building the bundled documentation, all IDs must be > >> unique. This is a particularly time consuming problem to fix because > >> the error output from the Maven docbook plugin doesn't tell you which > >> files are the problem ones. > >> > >> 3) When adding, renaming or deleting a chapter of your documentation, > >> please notify me of the changes so that I can update > >> bundled_master.xml. This file must be manually kept up to date whenever > >> any documentation changes are made. > >> > >> Thanks, > >> Shane > >> > >> > >> > >> >> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> > >> > >> > >> > >> > >> Seam 3 > >> Bundled Reference Guide > >> > >> > >> > >> > >> > >> Forge > >> > >> > >> > >> > >> > >> > >> > >> Seam Solder > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Configuration > >> > >> > >> > >> > >> > >> Seam Persistence > >> > >> > >> > >> > >> Seam Transaction > >> > >> > >> > >> > >> Seam Servlet > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Security > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam International > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Faces > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Catch > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Reports > >> > >> > >> > >> > >> > >> > >> Seam Remoting > >> > >> > >> > >> > >> > >> > >> Seam REST > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam JCR > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam JMS > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Seam Validation > >> > >> > >> > >> > >> > >> > >> > >> Seam Wicket > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> seam-dev mailing list > >> seam-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/seam-dev > > > > _______________________________________________ > > seam-dev mailing list > > seam-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > > > -- > Jason Porter > http://lightguard-jp.blogspot.com > http://twitter.com/lightguardjp > > Software Engineer > Open Source Advocate > Author of Seam Catch - Next Generation Java Exception Handling > > PGP key id: 926CCFF5 > PGP key available at: keyserver.net, pgp.mit.edu > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110901/5f9d116d/attachment.html From lincolnbaxter at gmail.com Thu Sep 1 23:48:41 2011 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Thu, 1 Sep 2011 23:48:41 -0400 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com> Message-ID: Actually, maybe the best thing to do is just to add a new section to the Seam umbrella doc, with an HTML link to the forge confluence space? On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III wrote: > Ok. If you include beta1, the artifact for dist is: > > org.jboss.forge:forge-modules:1.0.0.Beta1 > > -- > Lincoln Baxter's Droid > http://ocpsoft.com > "Keep it Simple" > On Sep 1, 2011 7:52 PM, "Shane Bryzak" wrote: > > Yep, I planned on extracting it in the forge folder. > > > > On 02/09/11 09:43, Lincoln Baxter, III wrote: > >> > >> Also, if forge is unzipped. It should be done so in its own subfolder. > >> > >> Ill try to catch you online tonight and make sure you've got the right > >> artifact. (it moved temporarily during the jboss modules transition. > >> > >> -- > >> Lincoln Baxter's Droid > >> http://ocpsoft.com > >> "Keep it Simple" > >> > >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" >> > wrote: > >> > Well. The forge distribution doesn't contain docs either. They are > >> purely > >> > online at this point. So I think just don't worry about it. This > >> confluence > >> > thing is a bit of a pain in that regard. > >> > > >> > -- > >> > Lincoln Baxter's Droid > >> > http://ocpsoft.com > >> > "Keep it Simple" > >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" >> > wrote: > >> >> Unless an export could be automated as part of the build process, I > >> >> don't think that's a good idea. How about we just include the Forge > >> >> distribution extracted inside the Seam distribution? The > documentation > >> >> won't be combined with the main Seam docs, but as long as it's in the > >> >> Forge distribution then a user should be able to find it without too > >> >> much effort. > >> >> > >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: > >> >>> > >> >>> I'm not really sure how to do this, then. There are no sources since > >> >>> the docs are in confluence. > >> >>> > >> >>> I suppose an export could work? > >> >>> > >> >>> -- > >> >>> Lincoln Baxter's Droid > >> >>> http://ocpsoft.com > >> >>> "Keep it Simple" > >> >>> > >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" >> > >> >>> >> wrote: > >> >>> > The source artifact for the Forge docs were being pulled in like > >> this: > >> >>> > > >> >>> > > >> >>> > org.jboss.seam.forge > >> >>> > forge-reference-guide > >> >>> > 1.0.0-SNAPSHOT > >> >>> > sources > >> >>> > jar > >> >>> > > >> >>> > > >> >>> > When I update the version to 1.0.0.Beta1, it can't find the source > - > >> >>> was > >> >>> > the Beta1 source artifact published to Maven? > >> >>> > > >> >>> > > >> >>> > > >> >>> > On 01/09/11 03:02, Lincoln Baxter, III wrote: > >> >>> >> https://docs.jboss.org/author/display/SEAMFORGE/Home > >> >>> >> > >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln Baxter, III > >> >>> >> > >> > > >> >>> > >> >>> > wrote: > >> >>> >> > >> >>> >> Just checking - the Forge docs are no longer in SVN / are in > >> >>> >> Confluence; have you taken this into account? > >> >>> >> > >> >>> >> Also, the which distribution are you including? You could choose > >> >>> >> either Beta1 or the latest SNAPSHOT (which is actually in a new > >> >>> >> location - moved back to the original > >> >>> >> org.jboss.forge:forge-distribution - though it looks like the > >> >>> >> build hasn't deployed artifacts in a little while - looking in to > >> >>> >> that) > >> >>> >> > >> >>> >> ~Lincoln > >> >>> >> > >> >>> >> > >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane Bryzak > >> > >> >>> > > >> >>> >> > >> >>> wrote: > >> >>> >> > >> >>> >> Module leads, > >> >>> >> > >> >>> >> Can you please review the list below and confirm that the > >> >>> >> documentation > >> >>> >> chapters are correct for your module. Also, I would like > >> >>> >> everyone to > >> >>> >> take a moment to review the module documentation guidelines, > >> >>> >> as there > >> >>> >> were a number of breakages in the bundled documentation build > >> >>> >> because > >> >>> >> the guidelines weren't adhered to, particularly in the new > >> >>> >> modules for > >> >>> >> Seam 3.1: > >> >>> >> > >> >>> >> 1) Always prefix the filenames of your documentation chapters > >> >>> >> with the > >> >>> >> name of your module. E.g. security-authentication.xml, > >> >>> >> security-authorization.xml, etc. > >> >>> >> > >> >>> >> 2) Whenever you assign an ID to a docbook element, such as a > >> >>> >> > >> >>> >> or

, ALWAYS prefix the id with your module name. For > >> >>> >> example, > >> >>> >> or

>> >>> >> id="security-getting-started">. As all of the chapters for > >> >>> >> all modules > >> >>> >> are combined when building the bundled documentation, all IDs > >> >>> >> must be > >> >>> >> unique. This is a particularly time consuming problem to fix > >> >>> >> because > >> >>> >> the error output from the Maven docbook plugin doesn't tell > >> >>> >> you which > >> >>> >> files are the problem ones. > >> >>> >> > >> >>> >> 3) When adding, renaming or deleting a chapter of your > >> >>> >> documentation, > >> >>> >> please notify me of the changes so that I can update > >> >>> >> bundled_master.xml. This file must be manually kept up to > >> >>> >> date whenever > >> >>> >> any documentation changes are made. > >> >>> >> > >> >>> >> Thanks, > >> >>> >> Shane > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam 3 > >> >>> >> Bundled Reference Guide > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Forge > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Solder > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Configuration > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Persistence > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Transaction > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Servlet > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Security > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam International > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Faces > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Catch > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Reports > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Remoting > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam REST > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam JCR > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam JMS > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Validation > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Wicket > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> _______________________________________________ > >> >>> >> seam-dev mailing list > >> >>> >> seam-dev at lists.jboss.org > >> > > >> >>> > >> >> > >> >>> >> https://lists.jboss.org/mailman/listinfo/seam-dev > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> -- > >> >>> >> Lincoln Baxter, III > >> >>> >> http://ocpsoft.com > >> >>> >> http://scrumshark.com > >> >>> >> "Keep it Simple" > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> -- > >> >>> >> Lincoln Baxter, III > >> >>> >> http://ocpsoft.com > >> >>> >> http://scrumshark.com > >> >>> >> "Keep it Simple" > >> >>> > > >> >> > > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110901/0a42e775/attachment-0001.html From sbryzak at redhat.com Thu Sep 1 23:51:57 2011 From: sbryzak at redhat.com (Shane Bryzak) Date: Fri, 02 Sep 2011 13:51:57 +1000 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>

Message-ID: <4E6052DD.1090602@redhat.com> Yeah, that's a good idea. Do you have plans to provide documentation as part of the Forge download? I'm thinking of the users who might have no/limited connectivity who won't be able to access the Forge docs online. Also, how does confluence work in conjunction with our documentation team? From my understanding all their tools for translating etc are based on Publican/Docbook. On 02/09/11 13:48, Lincoln Baxter, III wrote: > Actually, maybe the best thing to do is just to add a new section to > the Seam umbrella doc, with an HTML link to the forge confluence space? > > On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III > > wrote: > > Ok. If you include beta1, the artifact for dist is: > > org.jboss.forge:forge-modules:1.0.0.Beta1 > > -- > Lincoln Baxter's Droid > http://ocpsoft.com > "Keep it Simple" > > On Sep 1, 2011 7:52 PM, "Shane Bryzak" > wrote: > > Yep, I planned on extracting it in the forge folder. > > > > On 02/09/11 09:43, Lincoln Baxter, III wrote: > >> > >> Also, if forge is unzipped. It should be done so in its own > subfolder. > >> > >> Ill try to catch you online tonight and make sure you've got > the right > >> artifact. (it moved temporarily during the jboss modules > transition. > >> > >> -- > >> Lincoln Baxter's Droid > >> http://ocpsoft.com > >> "Keep it Simple" > >> > >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" > > >> >> wrote: > >> > Well. The forge distribution doesn't contain docs either. > They are > >> purely > >> > online at this point. So I think just don't worry about it. This > >> confluence > >> > thing is a bit of a pain in that regard. > >> > > >> > -- > >> > Lincoln Baxter's Droid > >> > http://ocpsoft.com > >> > "Keep it Simple" > >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" > >> >> wrote: > >> >> Unless an export could be automated as part of the build > process, I > >> >> don't think that's a good idea. How about we just include > the Forge > >> >> distribution extracted inside the Seam distribution? The > documentation > >> >> won't be combined with the main Seam docs, but as long as > it's in the > >> >> Forge distribution then a user should be able to find it > without too > >> >> much effort. > >> >> > >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: > >> >>> > >> >>> I'm not really sure how to do this, then. There are no > sources since > >> >>> the docs are in confluence. > >> >>> > >> >>> I suppose an export could work? > >> >>> > >> >>> -- > >> >>> Lincoln Baxter's Droid > >> >>> http://ocpsoft.com > >> >>> "Keep it Simple" > >> >>> > >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" > >> > > >> >>> > >>> wrote: > >> >>> > The source artifact for the Forge docs were being pulled > in like > >> this: > >> >>> > > >> >>> > > >> >>> > org.jboss.seam.forge > >> >>> > forge-reference-guide > >> >>> > 1.0.0-SNAPSHOT > >> >>> > sources > >> >>> > jar > >> >>> > > >> >>> > > >> >>> > When I update the version to 1.0.0.Beta1, it can't find > the source - > >> >>> was > >> >>> > the Beta1 source artifact published to Maven? > >> >>> > > >> >>> > > >> >>> > > >> >>> > On 01/09/11 03:02, Lincoln Baxter, III wrote: > >> >>> >> https://docs.jboss.org/author/display/SEAMFORGE/Home > >> >>> >> > >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln Baxter, III > >> >>> >> > > >> >> > >> >>> > > >> >>>> wrote: > >> >>> >> > >> >>> >> Just checking - the Forge docs are no longer in SVN / are in > >> >>> >> Confluence; have you taken this into account? > >> >>> >> > >> >>> >> Also, the which distribution are you including? You > could choose > >> >>> >> either Beta1 or the latest SNAPSHOT (which is actually > in a new > >> >>> >> location - moved back to the original > >> >>> >> org.jboss.forge:forge-distribution - though it looks > like the > >> >>> >> build hasn't deployed artifacts in a little while - > looking in to > >> >>> >> that) > >> >>> >> > >> >>> >> ~Lincoln > >> >>> >> > >> >>> >> > >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane Bryzak > >> > > > >> >>> > >> > >> >>> >> > > > >> > >>>> wrote: > >> >>> >> > >> >>> >> Module leads, > >> >>> >> > >> >>> >> Can you please review the list below and confirm that the > >> >>> >> documentation > >> >>> >> chapters are correct for your module. Also, I would like > >> >>> >> everyone to > >> >>> >> take a moment to review the module documentation guidelines, > >> >>> >> as there > >> >>> >> were a number of breakages in the bundled documentation > build > >> >>> >> because > >> >>> >> the guidelines weren't adhered to, particularly in the new > >> >>> >> modules for > >> >>> >> Seam 3.1: > >> >>> >> > >> >>> >> 1) Always prefix the filenames of your documentation > chapters > >> >>> >> with the > >> >>> >> name of your module. E.g. security-authentication.xml, > >> >>> >> security-authorization.xml, etc. > >> >>> >> > >> >>> >> 2) Whenever you assign an ID to a docbook element, such as a > >> >>> >> > >> >>> >> or

, ALWAYS prefix the id with your module > name. For > >> >>> >> example, > >> >>> >> or

>> >>> >> id="security-getting-started">. As all of the chapters for > >> >>> >> all modules > >> >>> >> are combined when building the bundled documentation, > all IDs > >> >>> >> must be > >> >>> >> unique. This is a particularly time consuming problem to fix > >> >>> >> because > >> >>> >> the error output from the Maven docbook plugin doesn't tell > >> >>> >> you which > >> >>> >> files are the problem ones. > >> >>> >> > >> >>> >> 3) When adding, renaming or deleting a chapter of your > >> >>> >> documentation, > >> >>> >> please notify me of the changes so that I can update > >> >>> >> bundled_master.xml. This file must be manually kept up to > >> >>> >> date whenever > >> >>> >> any documentation changes are made. > >> >>> >> > >> >>> >> Thanks, > >> >>> >> Shane > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> >> >>> >> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" > [ ]> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam 3 > >> >>> >> Bundled Reference Guide > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Forge > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Solder > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Configuration > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Persistence > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Transaction > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Servlet > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Security > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam International > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Faces > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Catch > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Reports > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Remoting > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam REST > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam JCR > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam JMS > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Validation > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> Seam Wicket > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> _______________________________________________ > >> >>> >> seam-dev mailing list > >> >>> >> seam-dev at lists.jboss.org >

> > >>

>> > >> >>>

> > >>

>>> > >> >>> >> https://lists.jboss.org/mailman/listinfo/seam-dev > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> -- > >> >>> >> Lincoln Baxter, III > >> >>> >> http://ocpsoft.com > >> >>> >> http://scrumshark.com > >> >>> >> "Keep it Simple" > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> -- > >> >>> >> Lincoln Baxter, III > >> >>> >> http://ocpsoft.com > >> >>> >> http://scrumshark.com > >> >>> >> "Keep it Simple" > >> >>> > > >> >> > > > > > > > -- > Lincoln Baxter, III > http://ocpsoft.com > http://scrumshark.com > "Keep it Simple" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110902/e0f1e811/attachment-0001.html From lightguard.jp at gmail.com Thu Sep 1 23:54:02 2011 From: lightguard.jp at gmail.com (Jason Porter) Date: Thu, 1 Sep 2011 21:54:02 -0600 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: <4E6052DD.1090602@redhat.com> References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>

<4E6052DD.1090602@redhat.com> Message-ID: Could we do the same thing for the getting started guide as well? On Thu, Sep 1, 2011 at 21:51, Shane Bryzak wrote: > Yeah, that's a good idea. Do you have plans to provide documentation as > part of the Forge download? I'm thinking of the users who might have > no/limited connectivity who won't be able to access the Forge docs online. > Also, how does confluence work in conjunction with our documentation team? > From my understanding all their tools for translating etc are based on > Publican/Docbook. > > > On 02/09/11 13:48, Lincoln Baxter, III wrote: > > Actually, maybe the best thing to do is just to add a new section to the > Seam umbrella doc, with an HTML link to the forge confluence space? > > On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III < > lincolnbaxter at gmail.com> wrote: > >> Ok. If you include beta1, the artifact for dist is: >> >> org.jboss.forge:forge-modules:1.0.0.Beta1 >> >> -- >> Lincoln Baxter's Droid >> http://ocpsoft.com >> "Keep it Simple" >> On Sep 1, 2011 7:52 PM, "Shane Bryzak" wrote: >> > Yep, I planned on extracting it in the forge folder. >> > >> > On 02/09/11 09:43, Lincoln Baxter, III wrote: >> >> >> >> Also, if forge is unzipped. It should be done so in its own subfolder. >> >> >> >> Ill try to catch you online tonight and make sure you've got the right >> >> artifact. (it moved temporarily during the jboss modules transition. >> >> >> >> -- >> >> Lincoln Baxter's Droid >> >> http://ocpsoft.com >> >> "Keep it Simple" >> >> >> >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" > >> > wrote: >> >> > Well. The forge distribution doesn't contain docs either. They are >> >> purely >> >> > online at this point. So I think just don't worry about it. This >> >> confluence >> >> > thing is a bit of a pain in that regard. >> >> > >> >> > -- >> >> > Lincoln Baxter's Droid >> >> > http://ocpsoft.com >> >> > "Keep it Simple" >> >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" > >> > wrote: >> >> >> Unless an export could be automated as part of the build process, I >> >> >> don't think that's a good idea. How about we just include the Forge >> >> >> distribution extracted inside the Seam distribution? The >> documentation >> >> >> won't be combined with the main Seam docs, but as long as it's in >> the >> >> >> Forge distribution then a user should be able to find it without too >> >> >> much effort. >> >> >> >> >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: >> >> >>> >> >> >>> I'm not really sure how to do this, then. There are no sources >> since >> >> >>> the docs are in confluence. >> >> >>> >> >> >>> I suppose an export could work? >> >> >>> >> >> >>> -- >> >> >>> Lincoln Baxter's Droid >> >> >>> http://ocpsoft.com >> >> >>> "Keep it Simple" >> >> >>> >> >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" > >> >> >> >>> >> wrote: >> >> >>> > The source artifact for the Forge docs were being pulled in >> like >> >> this: >> >> >>> > >> >> >>> > >> >> >>> > org.jboss.seam.forge >> >> >>> > forge-reference-guide >> >> >>> > 1.0.0-SNAPSHOT >> >> >>> > sources >> >> >>> > jar >> >> >>> > >> >> >>> > >> >> >>> > When I update the version to 1.0.0.Beta1, it can't find the >> source - >> >> >>> was >> >> >>> > the Beta1 source artifact published to Maven? >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > On 01/09/11 03:02, Lincoln Baxter, III wrote: >> >> >>> >> https://docs.jboss.org/author/display/SEAMFORGE/Home >> >> >>> >> >> >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln Baxter, III >> >> >>> >> >> >> > >> >> >>> >> >> >>> >> wrote: >> >> >>> >> >> >> >>> >> Just checking - the Forge docs are no longer in SVN / are in >> >> >>> >> Confluence; have you taken this into account? >> >> >>> >> >> >> >>> >> Also, the which distribution are you including? You could choose >> >> >>> >> either Beta1 or the latest SNAPSHOT (which is actually in a new >> >> >>> >> location - moved back to the original >> >> >>> >> org.jboss.forge:forge-distribution - though it looks like the >> >> >>> >> build hasn't deployed artifacts in a little while - looking in >> to >> >> >>> >> that) >> >> >>> >> >> >> >>> >> ~Lincoln >> >> >>> >> >> >> >>> >> >> >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane Bryzak >> >> >> >> >>> > >> >> >>> >> >> >> >>> wrote: >> >> >>> >> >> >> >>> >> Module leads, >> >> >>> >> >> >> >>> >> Can you please review the list below and confirm that the >> >> >>> >> documentation >> >> >>> >> chapters are correct for your module. Also, I would like >> >> >>> >> everyone to >> >> >>> >> take a moment to review the module documentation guidelines, >> >> >>> >> as there >> >> >>> >> were a number of breakages in the bundled documentation build >> >> >>> >> because >> >> >>> >> the guidelines weren't adhered to, particularly in the new >> >> >>> >> modules for >> >> >>> >> Seam 3.1: >> >> >>> >> >> >> >>> >> 1) Always prefix the filenames of your documentation chapters >> >> >>> >> with the >> >> >>> >> name of your module. E.g. security-authentication.xml, >> >> >>> >> security-authorization.xml, etc. >> >> >>> >> >> >> >>> >> 2) Whenever you assign an ID to a docbook element, such as a >> >> >>> >> >> >> >>> >> or

, ALWAYS prefix the id with your module name. For >> >> >>> >> example, >> >> >>> >> or

> >> >>> >> id="security-getting-started">. As all of the chapters for >> >> >>> >> all modules >> >> >>> >> are combined when building the bundled documentation, all IDs >> >> >>> >> must be >> >> >>> >> unique. This is a particularly time consuming problem to fix >> >> >>> >> because >> >> >>> >> the error output from the Maven docbook plugin doesn't tell >> >> >>> >> you which >> >> >>> >> files are the problem ones. >> >> >>> >> >> >> >>> >> 3) When adding, renaming or deleting a chapter of your >> >> >>> >> documentation, >> >> >>> >> please notify me of the changes so that I can update >> >> >>> >> bundled_master.xml. This file must be manually kept up to >> >> >>> >> date whenever >> >> >>> >> any documentation changes are made. >> >> >>> >> >> >> >>> >> Thanks, >> >> >>> >> Shane >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam 3 >> >> >>> >> Bundled Reference Guide >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Forge >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Solder >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Configuration >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Persistence >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Transaction >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Servlet >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Security >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam International >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Faces >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Catch >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Reports >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Remoting >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam REST >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam JCR >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam JMS >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Validation >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Wicket >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> _______________________________________________ >> >> >>> >> seam-dev mailing list >> >> >>> >> seam-dev at lists.jboss.org >> >> > >> >> >>> >> >> >> >> >> >> >>> >> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -- >> >> >>> >> Lincoln Baxter, III >> >> >>> >> http://ocpsoft.com >> >> >>> >> http://scrumshark.com >> >> >>> >> "Keep it Simple" >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -- >> >> >>> >> Lincoln Baxter, III >> >> >>> >> http://ocpsoft.com >> >> >>> >> http://scrumshark.com >> >> >>> >> "Keep it Simple" >> >> >>> > >> >> >> >> > >> > > > > -- > Lincoln Baxter, III > http://ocpsoft.com > http://scrumshark.com > "Keep it Simple" > > > > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > -- Jason Porter http://lightguard-jp.blogspot.com http://twitter.com/lightguardjp Software Engineer Open Source Advocate Author of Seam Catch - Next Generation Java Exception Handling PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110901/b15ccf5e/attachment-0001.html From sbryzak at redhat.com Thu Sep 1 23:55:26 2011 From: sbryzak at redhat.com (Shane Bryzak) Date: Fri, 02 Sep 2011 13:55:26 +1000 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>

<4E6052DD.1090602@redhat.com> Message-ID: <4E6053AE.7010007@redhat.com> We definitely want to include the getting started guide in the reference docs. On 02/09/11 13:54, Jason Porter wrote: > Could we do the same thing for the getting started guide as well? > > On Thu, Sep 1, 2011 at 21:51, Shane Bryzak > wrote: > > Yeah, that's a good idea. Do you have plans to provide > documentation as part of the Forge download? I'm thinking of the > users who might have no/limited connectivity who won't be able to > access the Forge docs online. Also, how does confluence work in > conjunction with our documentation team? From my understanding > all their tools for translating etc are based on Publican/Docbook. > > > On 02/09/11 13:48, Lincoln Baxter, III wrote: >> Actually, maybe the best thing to do is just to add a new section >> to the Seam umbrella doc, with an HTML link to the forge >> confluence space? >> >> On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III >> > wrote: >> >> Ok. If you include beta1, the artifact for dist is: >> >> org.jboss.forge:forge-modules:1.0.0.Beta1 >> >> -- >> Lincoln Baxter's Droid >> http://ocpsoft.com >> "Keep it Simple" >> >> On Sep 1, 2011 7:52 PM, "Shane Bryzak" > > wrote: >> > Yep, I planned on extracting it in the forge folder. >> > >> > On 02/09/11 09:43, Lincoln Baxter, III wrote: >> >> >> >> Also, if forge is unzipped. It should be done so in its >> own subfolder. >> >> >> >> Ill try to catch you online tonight and make sure you've >> got the right >> >> artifact. (it moved temporarily during the jboss modules >> transition. >> >> >> >> -- >> >> Lincoln Baxter's Droid >> >> http://ocpsoft.com >> >> "Keep it Simple" >> >> >> >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" >> >> >> > >> wrote: >> >> > Well. The forge distribution doesn't contain docs >> either. They are >> >> purely >> >> > online at this point. So I think just don't worry about >> it. This >> >> confluence >> >> > thing is a bit of a pain in that regard. >> >> > >> >> > -- >> >> > Lincoln Baxter's Droid >> >> > http://ocpsoft.com >> >> > "Keep it Simple" >> >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" >> >> >> >> >> wrote: >> >> >> Unless an export could be automated as part of the >> build process, I >> >> >> don't think that's a good idea. How about we just >> include the Forge >> >> >> distribution extracted inside the Seam distribution? >> The documentation >> >> >> won't be combined with the main Seam docs, but as long >> as it's in the >> >> >> Forge distribution then a user should be able to find >> it without too >> >> >> much effort. >> >> >> >> >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: >> >> >>> >> >> >>> I'm not really sure how to do this, then. There are no >> sources since >> >> >>> the docs are in confluence. >> >> >>> >> >> >>> I suppose an export could work? >> >> >>> >> >> >>> -- >> >> >>> Lincoln Baxter's Droid >> >> >>> http://ocpsoft.com >> >> >>> "Keep it Simple" >> >> >>> >> >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" >> >> >> > >> >> >>> >> >>> wrote: >> >> >>> > The source artifact for the Forge docs were being >> pulled in like >> >> this: >> >> >>> > >> >> >>> > >> >> >>> > org.jboss.seam.forge >> >> >>> > forge-reference-guide >> >> >>> > 1.0.0-SNAPSHOT >> >> >>> > sources >> >> >>> > jar >> >> >>> > >> >> >>> > >> >> >>> > When I update the version to 1.0.0.Beta1, it can't >> find the source - >> >> >>> was >> >> >>> > the Beta1 source artifact published to Maven? >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > On 01/09/11 03:02, Lincoln Baxter, III wrote: >> >> >>> >> https://docs.jboss.org/author/display/SEAMFORGE/Home >> >> >>> >> >> >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln Baxter, III >> >> >>> >> > >> > > >> >> > >> > >> >> >> >>> > >> > > >> >> > >> > >>>> wrote: >> >> >>> >> >> >> >>> >> Just checking - the Forge docs are no longer in SVN >> / are in >> >> >>> >> Confluence; have you taken this into account? >> >> >>> >> >> >> >>> >> Also, the which distribution are you including? You >> could choose >> >> >>> >> either Beta1 or the latest SNAPSHOT (which is >> actually in a new >> >> >>> >> location - moved back to the original >> >> >>> >> org.jboss.forge:forge-distribution - though it >> looks like the >> >> >>> >> build hasn't deployed artifacts in a little while - >> looking in to >> >> >>> >> that) >> >> >>> >> >> >> >>> >> ~Lincoln >> >> >>> >> >> >> >>> >> >> >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane Bryzak >> >> >> > >> >> >>> >> >> >> >> >>> >> > > > >> >> >> >>>> wrote: >> >> >>> >> >> >> >>> >> Module leads, >> >> >>> >> >> >> >>> >> Can you please review the list below and confirm >> that the >> >> >>> >> documentation >> >> >>> >> chapters are correct for your module. Also, I would >> like >> >> >>> >> everyone to >> >> >>> >> take a moment to review the module documentation >> guidelines, >> >> >>> >> as there >> >> >>> >> were a number of breakages in the bundled >> documentation build >> >> >>> >> because >> >> >>> >> the guidelines weren't adhered to, particularly in >> the new >> >> >>> >> modules for >> >> >>> >> Seam 3.1: >> >> >>> >> >> >> >>> >> 1) Always prefix the filenames of your >> documentation chapters >> >> >>> >> with the >> >> >>> >> name of your module. E.g. security-authentication.xml, >> >> >>> >> security-authorization.xml, etc. >> >> >>> >> >> >> >>> >> 2) Whenever you assign an ID to a docbook element, >> such as a >> >> >>> >> >> >> >>> >> or

, ALWAYS prefix the id with your module >> name. For >> >> >>> >> example, >> >> >>> >> or

> >> >>> >> id="security-getting-started">. As all of the >> chapters for >> >> >>> >> all modules >> >> >>> >> are combined when building the bundled >> documentation, all IDs >> >> >>> >> must be >> >> >>> >> unique. This is a particularly time consuming >> problem to fix >> >> >>> >> because >> >> >>> >> the error output from the Maven docbook plugin >> doesn't tell >> >> >>> >> you which >> >> >>> >> files are the problem ones. >> >> >>> >> >> >> >>> >> 3) When adding, renaming or deleting a chapter of your >> >> >>> >> documentation, >> >> >>> >> please notify me of the changes so that I can update >> >> >>> >> bundled_master.xml. This file must be manually kept >> up to >> >> >>> >> date whenever >> >> >>> >> any documentation changes are made. >> >> >>> >> >> >> >>> >> Thanks, >> >> >>> >> Shane >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> > V4.5//EN" >> >> >>> >> >> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> >> >> >>> >> > xmlns:xi="http://www.w3.org/2001/XInclude"> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam 3 >> >> >>> >> Bundled Reference Guide >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Forge >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Solder >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Configuration >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Persistence >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Transaction >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Servlet >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Security >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> > href="security-authentication-external.xml"/> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam International >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Faces >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Catch >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Reports >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Remoting >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam REST >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam JCR >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam JMS >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Validation >> >> >>> >> >> >> >>> >> >> >> >>> >> > href="validation-dependency-injection.xml"/> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Wicket >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> _______________________________________________ >> >> >>> >> seam-dev mailing list >> >> >>> >> seam-dev at lists.jboss.org >> >> > > >> >> > >> > >> >> >> >>> > >> > > >> >> > >> > >>> >> >> >>> >> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -- >> >> >>> >> Lincoln Baxter, III >> >> >>> >> http://ocpsoft.com >> >> >>> >> http://scrumshark.com >> >> >>> >> "Keep it Simple" >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -- >> >> >>> >> Lincoln Baxter, III >> >> >>> >> http://ocpsoft.com >> >> >>> >> http://scrumshark.com >> >> >>> >> "Keep it Simple" >> >> >>> > >> >> >> >> > >> >> >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.com >> http://scrumshark.com >> "Keep it Simple" > > > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > > > > -- > Jason Porter > http://lightguard-jp.blogspot.com > http://twitter.com/lightguardjp > > Software Engineer > Open Source Advocate > Author of Seam Catch - Next Generation Java Exception Handling > > PGP key id: 926CCFF5 > PGP key available at: keyserver.net , > pgp.mit.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110902/25d4e9c8/attachment-0001.html From lincolnbaxter at gmail.com Fri Sep 2 00:15:06 2011 From: lincolnbaxter at gmail.com (Lincoln Baxter, III) Date: Fri, 2 Sep 2011 00:15:06 -0400 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: <4E6052DD.1090602@redhat.com> References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>

<4E6052DD.1090602@redhat.com> Message-ID: I don't know. I don't really have plans to include docbook in the dist until we get some better integration there from the .ORG team. I don't see that happening, though, so until then, online docs are the way people will be learning about forge. Our tools don't make this easy. I don't think the connectivity issue will be a problem. People can always print or download the site for later if they have connectivity issues. It might be nice (on confluence) to be able to have a 1-click download, though. ~Lincoln On Thu, Sep 1, 2011 at 11:51 PM, Shane Bryzak wrote: > Yeah, that's a good idea. Do you have plans to provide documentation as > part of the Forge download? I'm thinking of the users who might have > no/limited connectivity who won't be able to access the Forge docs online. > Also, how does confluence work in conjunction with our documentation team? > From my understanding all their tools for translating etc are based on > Publican/Docbook. > > > On 02/09/11 13:48, Lincoln Baxter, III wrote: > > Actually, maybe the best thing to do is just to add a new section to the > Seam umbrella doc, with an HTML link to the forge confluence space? > > On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III < > lincolnbaxter at gmail.com> wrote: > >> Ok. If you include beta1, the artifact for dist is: >> >> org.jboss.forge:forge-modules:1.0.0.Beta1 >> >> -- >> Lincoln Baxter's Droid >> http://ocpsoft.com >> "Keep it Simple" >> On Sep 1, 2011 7:52 PM, "Shane Bryzak" wrote: >> > Yep, I planned on extracting it in the forge folder. >> > >> > On 02/09/11 09:43, Lincoln Baxter, III wrote: >> >> >> >> Also, if forge is unzipped. It should be done so in its own subfolder. >> >> >> >> Ill try to catch you online tonight and make sure you've got the right >> >> artifact. (it moved temporarily during the jboss modules transition. >> >> >> >> -- >> >> Lincoln Baxter's Droid >> >> http://ocpsoft.com >> >> "Keep it Simple" >> >> >> >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" > >> > wrote: >> >> > Well. The forge distribution doesn't contain docs either. They are >> >> purely >> >> > online at this point. So I think just don't worry about it. This >> >> confluence >> >> > thing is a bit of a pain in that regard. >> >> > >> >> > -- >> >> > Lincoln Baxter's Droid >> >> > http://ocpsoft.com >> >> > "Keep it Simple" >> >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" > >> > wrote: >> >> >> Unless an export could be automated as part of the build process, I >> >> >> don't think that's a good idea. How about we just include the Forge >> >> >> distribution extracted inside the Seam distribution? The >> documentation >> >> >> won't be combined with the main Seam docs, but as long as it's in >> the >> >> >> Forge distribution then a user should be able to find it without too >> >> >> much effort. >> >> >> >> >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: >> >> >>> >> >> >>> I'm not really sure how to do this, then. There are no sources >> since >> >> >>> the docs are in confluence. >> >> >>> >> >> >>> I suppose an export could work? >> >> >>> >> >> >>> -- >> >> >>> Lincoln Baxter's Droid >> >> >>> http://ocpsoft.com >> >> >>> "Keep it Simple" >> >> >>> >> >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" > >> >> >> >>> >> wrote: >> >> >>> > The source artifact for the Forge docs were being pulled in >> like >> >> this: >> >> >>> > >> >> >>> > >> >> >>> > org.jboss.seam.forge >> >> >>> > forge-reference-guide >> >> >>> > 1.0.0-SNAPSHOT >> >> >>> > sources >> >> >>> > jar >> >> >>> > >> >> >>> > >> >> >>> > When I update the version to 1.0.0.Beta1, it can't find the >> source - >> >> >>> was >> >> >>> > the Beta1 source artifact published to Maven? >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > On 01/09/11 03:02, Lincoln Baxter, III wrote: >> >> >>> >> https://docs.jboss.org/author/display/SEAMFORGE/Home >> >> >>> >> >> >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln Baxter, III >> >> >>> >> >> >> > >> >> >>> >> >> >>> >> wrote: >> >> >>> >> >> >> >>> >> Just checking - the Forge docs are no longer in SVN / are in >> >> >>> >> Confluence; have you taken this into account? >> >> >>> >> >> >> >>> >> Also, the which distribution are you including? You could choose >> >> >>> >> either Beta1 or the latest SNAPSHOT (which is actually in a new >> >> >>> >> location - moved back to the original >> >> >>> >> org.jboss.forge:forge-distribution - though it looks like the >> >> >>> >> build hasn't deployed artifacts in a little while - looking in >> to >> >> >>> >> that) >> >> >>> >> >> >> >>> >> ~Lincoln >> >> >>> >> >> >> >>> >> >> >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane Bryzak >> >> >> >> >>> > >> >> >>> >> >> >> >>> wrote: >> >> >>> >> >> >> >>> >> Module leads, >> >> >>> >> >> >> >>> >> Can you please review the list below and confirm that the >> >> >>> >> documentation >> >> >>> >> chapters are correct for your module. Also, I would like >> >> >>> >> everyone to >> >> >>> >> take a moment to review the module documentation guidelines, >> >> >>> >> as there >> >> >>> >> were a number of breakages in the bundled documentation build >> >> >>> >> because >> >> >>> >> the guidelines weren't adhered to, particularly in the new >> >> >>> >> modules for >> >> >>> >> Seam 3.1: >> >> >>> >> >> >> >>> >> 1) Always prefix the filenames of your documentation chapters >> >> >>> >> with the >> >> >>> >> name of your module. E.g. security-authentication.xml, >> >> >>> >> security-authorization.xml, etc. >> >> >>> >> >> >> >>> >> 2) Whenever you assign an ID to a docbook element, such as a >> >> >>> >> >> >> >>> >> or

, ALWAYS prefix the id with your module name. For >> >> >>> >> example, >> >> >>> >> or

> >> >>> >> id="security-getting-started">. As all of the chapters for >> >> >>> >> all modules >> >> >>> >> are combined when building the bundled documentation, all IDs >> >> >>> >> must be >> >> >>> >> unique. This is a particularly time consuming problem to fix >> >> >>> >> because >> >> >>> >> the error output from the Maven docbook plugin doesn't tell >> >> >>> >> you which >> >> >>> >> files are the problem ones. >> >> >>> >> >> >> >>> >> 3) When adding, renaming or deleting a chapter of your >> >> >>> >> documentation, >> >> >>> >> please notify me of the changes so that I can update >> >> >>> >> bundled_master.xml. This file must be manually kept up to >> >> >>> >> date whenever >> >> >>> >> any documentation changes are made. >> >> >>> >> >> >> >>> >> Thanks, >> >> >>> >> Shane >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam 3 >> >> >>> >> Bundled Reference Guide >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Forge >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Solder >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Configuration >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Persistence >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Transaction >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Servlet >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Security >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam International >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Faces >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Catch >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Reports >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Remoting >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam REST >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam JCR >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam JMS >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Validation >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> Seam Wicket >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> _______________________________________________ >> >> >>> >> seam-dev mailing list >> >> >>> >> seam-dev at lists.jboss.org >> >> > >> >> >>> >> >> >> >> >> >> >>> >> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -- >> >> >>> >> Lincoln Baxter, III >> >> >>> >> http://ocpsoft.com >> >> >>> >> http://scrumshark.com >> >> >>> >> "Keep it Simple" >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> -- >> >> >>> >> Lincoln Baxter, III >> >> >>> >> http://ocpsoft.com >> >> >>> >> http://scrumshark.com >> >> >>> >> "Keep it Simple" >> >> >>> > >> >> >> >> > >> > > > > -- > Lincoln Baxter, III > http://ocpsoft.com > http://scrumshark.com > "Keep it Simple" > > > -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110902/309024cc/attachment-0001.html From mnovotny at redhat.com Fri Sep 2 05:35:13 2011 From: mnovotny at redhat.com (Marek Novotny) Date: Fri, 02 Sep 2011 11:35:13 +0200 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>

<4E6052DD.1090602@redhat.com> Message-ID: <1314956113.2908.9.camel@localhost.localdomain> What about using feature "Export to docbook" and then just generate standard jdocbook output in release process? https://docs.jboss.org/author/display/AUTHGUIDE/Exporting+content+to +DocBook+XML On Fri, 2011-09-02 at 00:15 -0400, Lincoln Baxter, III wrote: > I don't know. I don't really have plans to include docbook in the dist > until we get some better integration there from the .ORG team. I don't > see that happening, though, so until then, online docs are the way > people will be learning about forge. Our tools don't make this easy. > > I don't think the connectivity issue will be a problem. People can > always print or download the site for later if they have connectivity > issues. It might be nice (on confluence) to be able to have a 1-click > download, though. > > ~Lincoln > > On Thu, Sep 1, 2011 at 11:51 PM, Shane Bryzak > wrote: > Yeah, that's a good idea. Do you have plans to provide > documentation as part of the Forge download? I'm thinking of > the users who might have no/limited connectivity who won't be > able to access the Forge docs online. Also, how does > confluence work in conjunction with our documentation team? > From my understanding all their tools for translating etc are > based on Publican/Docbook. > > > > On 02/09/11 13:48, Lincoln Baxter, III wrote: > > Actually, maybe the best thing to do is just to add a new > > section to the Seam umbrella doc, with an HTML link to the > > forge confluence space? > > > > On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III > > wrote: > > Ok. If you include beta1, the artifact for dist is: > > > > org.jboss.forge:forge-modules:1.0.0.Beta1 > > > > -- > > Lincoln Baxter's Droid > > http://ocpsoft.com > > "Keep it Simple" > > > > > > On Sep 1, 2011 7:52 PM, "Shane Bryzak" > > wrote: > > > Yep, I planned on extracting it in the forge > > folder. > > > > > > On 02/09/11 09:43, Lincoln Baxter, III wrote: > > >> > > >> Also, if forge is unzipped. It should be done so > > in its own subfolder. > > >> > > >> Ill try to catch you online tonight and make sure > > you've got the right > > >> artifact. (it moved temporarily during the jboss > > modules transition. > > >> > > >> -- > > >> Lincoln Baxter's Droid > > >> http://ocpsoft.com > > >> "Keep it Simple" > > >> > > >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" > > > > > >> > wrote: > > > > >> > Well. The forge distribution doesn't contain > > docs either. They are > > >> purely > > >> > online at this point. So I think just don't > > worry about it. This > > >> confluence > > >> > thing is a bit of a pain in that regard. > > >> > > > >> > -- > > >> > Lincoln Baxter's Droid > > >> > http://ocpsoft.com > > >> > "Keep it Simple" > > >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" > > > > > >> > wrote: > > >> >> Unless an export could be automated as part of > > the build process, I > > >> >> don't think that's a good idea. How about we > > just include the Forge > > >> >> distribution extracted inside the Seam > > distribution? The documentation > > >> >> won't be combined with the main Seam docs, but > > as long as it's in the > > >> >> Forge distribution then a user should be able > > to find it without too > > >> >> much effort. > > >> >> > > >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: > > >> >>> > > >> >>> I'm not really sure how to do this, then. > > There are no sources since > > >> >>> the docs are in confluence. > > >> >>> > > >> >>> I suppose an export could work? > > >> >>> > > >> >>> -- > > >> >>> Lincoln Baxter's Droid > > >> >>> http://ocpsoft.com > > >> >>> "Keep it Simple" > > >> >>> > > >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" > > > >> > > > > >> >>> > >> wrote: > > > > >> >>> > The source artifact for the Forge docs were > > being pulled in like > > >> this: > > >> >>> > > > >> >>> > > > >> >>> > org.jboss.seam.forge > > >> >>> > > > forge-reference-guide > > >> >>> > 1.0.0-SNAPSHOT > > >> >>> > sources > > >> >>> > jar > > >> >>> > > > >> >>> > > > >> >>> > When I update the version to 1.0.0.Beta1, > > it can't find the source - > > >> >>> was > > >> >>> > the Beta1 source artifact published to > > Maven? > > >> >>> > > > >> >>> > > > >> >>> > > > >> >>> > On 01/09/11 03:02, Lincoln Baxter, III > > wrote: > > >> >>> >> > > https://docs.jboss.org/author/display/SEAMFORGE/Home > > >> >>> >> > > >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln > > Baxter, III > > >> >>> >> > > > >> > > > > >> >>> > > > >> > >>> wrote: > > >> >>> >> > > >> >>> >> Just checking - the Forge docs are no > > longer in SVN / are in > > >> >>> >> Confluence; have you taken this into > > account? > > >> >>> >> > > >> >>> >> Also, the which distribution are you > > including? You could choose > > >> >>> >> either Beta1 or the latest SNAPSHOT (which > > is actually in a new > > >> >>> >> location - moved back to the original > > >> >>> >> org.jboss.forge:forge-distribution - > > though it looks like the > > >> >>> >> build hasn't deployed artifacts in a > > little while - looking in to > > >> >>> >> that) > > >> >>> >> > > >> >>> >> ~Lincoln > > >> >>> >> > > >> >>> >> > > >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane > > Bryzak > > >> > > >> >>> > > > > >> >>> >> > > > >> > >>> wrote: > > >> >>> >> > > >> >>> >> Module leads, > > >> >>> >> > > >> >>> >> Can you please review the list below and > > confirm that the > > >> >>> >> documentation > > >> >>> >> chapters are correct for your module. > > Also, I would like > > >> >>> >> everyone to > > >> >>> >> take a moment to review the module > > documentation guidelines, > > >> >>> >> as there > > >> >>> >> were a number of breakages in the bundled > > documentation build > > >> >>> >> because > > >> >>> >> the guidelines weren't adhered to, > > particularly in the new > > >> >>> >> modules for > > >> >>> >> Seam 3.1: > > >> >>> >> > > >> >>> >> 1) Always prefix the filenames of your > > documentation chapters > > >> >>> >> with the > > >> >>> >> name of your module. E.g. > > security-authentication.xml, > > >> >>> >> security-authorization.xml, etc. > > >> >>> >> > > >> >>> >> 2) Whenever you assign an ID to a docbook > > element, such as a > > >> >>> >> > > >> >>> >> or

, ALWAYS prefix the id with > > your module name. For > > >> >>> >> example, > > >> >>> >> or > >

> >> >>> >> id="security-getting-started">. As all of > > the chapters for > > >> >>> >> all modules > > >> >>> >> are combined when building the bundled > > documentation, all IDs > > >> >>> >> must be > > >> >>> >> unique. This is a particularly time > > consuming problem to fix > > >> >>> >> because > > >> >>> >> the error output from the Maven docbook > > plugin doesn't tell > > >> >>> >> you which > > >> >>> >> files are the problem ones. > > >> >>> >> > > >> >>> >> 3) When adding, renaming or deleting a > > chapter of your > > >> >>> >> documentation, > > >> >>> >> please notify me of the changes so that I > > can update > > >> >>> >> bundled_master.xml. This file must be > > manually kept up to > > >> >>> >> date whenever > > >> >>> >> any documentation changes are made. > > >> >>> >> > > >> >>> >> Thanks, > > >> >>> >> Shane > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > DocBook XML V4.5//EN" > > >> >>> >> > > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> > > >> >>> >> > xmlns:xi="http://www.w3.org/2001/XInclude"> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam 3 > > >> >>> >> Bundled Reference > > Guide > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Forge > > >> >>> >> > > >> >>> >> > href="forge-installation.xml" /> > > >> >>> >> > href="forge-creating-basic-webapp.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Solder > > >> >>> >> > > >> >>> >> > href="solder-gettingstarted.xml"/> > > >> >>> >> > href="solder-programmingmodel.xml"/> > > >> >>> >> > href="solder-annotationliterals.xml"/> > > >> >>> >> > href="solder-elextensions.xml"/> > > >> >>> >> > href="solder-resourceloading.xml"/> > > >> >>> >> > > >> >>> >> > href="solder-typeutilities.xml"/> > > >> >>> >> > href="solder-beanmanagerprovider.xml"/> > > >> >>> >> > href="solder-beanutilities.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > href="solder-defaultbeans.xml"/> > > >> >>> >> > href="solder-genericbeans.xml"/> > > >> >>> >> > href="solder-servicehandler.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Configuration > > >> >>> >> > href="config-introduction.xml"/> > > >> >>> >> > href="config-xml-provider.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Persistence > > >> >>> >> > href="persistence-general.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Transaction > > >> >>> >> > href="transaction-general.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Servlet > > >> >>> >> > href="servlet-introduction.xml"/> > > >> >>> >> > href="servlet-installation.xml"/> > > >> >>> >> > > >> >>> >> > href="servlet-injectable_refs.xml"/> > > >> >>> >> > href="servlet-exception_handling.xml" /> > > >> >>> >> > href="servlet-beanmanager.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Security > > >> >>> >> > href="security-introduction.xml"/> > > >> >>> >> > href="security-authentication.xml"/> > > >> >>> >> > href="security-identitymanagement.xml"/> > > >> >>> >> > href="security-authentication-external.xml"/> > > >> >>> >> > href="security-authorization.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam International > > >> >>> >> > href="international-preface.xml" /> > > >> >>> >> > href="international-installation.xml" /> > > >> >>> >> > href="international-locales.xml" /> > > >> >>> >> > href="international-timezones.xml" /> > > >> >>> >> > href="international-messages.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Faces > > >> >>> >> > > >> >>> >> > href="faces-installation.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Catch > > >> >>> >> > href="catch-introduction.xml"/> > > >> >>> >> > href="catch-installation.xml"/> > > >> >>> >> > href="catch-client_usage.xml"/> > > >> >>> >> > href="catch-advanced_usage.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Reports > > >> >>> >> > > >> >>> >> > href="reports-installation.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Remoting > > >> >>> >> > > >> >>> >> > > >> >>> >> > href="remoting-validation.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam REST > > >> >>> >> > > >> >>> >> > href="rest-installation.xml" /> > > >> >>> >> > href="rest-exception-mapping.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > href="rest-dependencies.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam JCR > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam JMS > > >> >>> >> > > >> >>> >> > > >> >>> >> > href="jms-resource-injection.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > href="jms-mapping-interfaces.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Validation > > >> >>> >> > href="validation-introduction.xml"/> > > >> >>> >> > href="validation-installation.xml"/> > > >> >>> >> > href="validation-dependency-injection.xml"/> > > >> >>> >> > href="validation-method-validation.xml"/> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> Seam Wicket > > >> >>> >> > > >> >>> >> > href="wicket-installation.xml" /> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > _______________________________________________ > > >> >>> >> seam-dev mailing list > > >> >>> >> seam-dev at lists.jboss.org > > > > >> > > > > >> >>> > > > >> > >> > > >> >>> >> > > https://lists.jboss.org/mailman/listinfo/seam-dev > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> -- > > >> >>> >> Lincoln Baxter, III > > >> >>> >> http://ocpsoft.com > > >> >>> >> http://scrumshark.com > > >> >>> >> "Keep it Simple" > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> > > >> >>> >> -- > > >> >>> >> Lincoln Baxter, III > > >> >>> >> http://ocpsoft.com > > >> >>> >> http://scrumshark.com > > >> >>> >> "Keep it Simple" > > >> >>> > > > >> >> > > > > > > > > > > > > > -- > > Lincoln Baxter, III > > http://ocpsoft.com > > http://scrumshark.com > > "Keep it Simple" > > > > > > -- > Lincoln Baxter, III > http://ocpsoft.com > http://scrumshark.com > "Keep it Simple" > _______________________________________________ > seam-dev mailing list > seam-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev -- Marek Novotny -- Seam and WFK Product Lead Red Hat Czech s.r.o. Purkynova 99 612 45 Brno Email: mnovotny at redhat.com Office phone: +420 532 294 287, ext. 82-62 087 mobile: +420 608 509 230 From sbryzak at redhat.com Fri Sep 2 06:43:38 2011 From: sbryzak at redhat.com (Shane Bryzak) Date: Fri, 02 Sep 2011 20:43:38 +1000 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: <1314956113.2908.9.camel@localhost.localdomain> References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>

<4E6052DD.1090602@redhat.com> <1314956113.2908.9.camel@localhost.localdomain> Message-ID: <4E60B35A.1090504@redhat.com> This would need to be automated for the Seam distribution build though. Currently, all modules have their docbook sources published as Maven artifacts, which is what we use to construct the bundled documentation. On 02/09/11 19:35, Marek Novotny wrote: > What about using feature "Export to docbook" and then just generate > standard jdocbook output in release process? > > https://docs.jboss.org/author/display/AUTHGUIDE/Exporting+content+to > +DocBook+XML > > On Fri, 2011-09-02 at 00:15 -0400, Lincoln Baxter, III wrote: >> I don't know. I don't really have plans to include docbook in the dist >> until we get some better integration there from the .ORG team. I don't >> see that happening, though, so until then, online docs are the way >> people will be learning about forge. Our tools don't make this easy. >> >> I don't think the connectivity issue will be a problem. People can >> always print or download the site for later if they have connectivity >> issues. It might be nice (on confluence) to be able to have a 1-click >> download, though. >> >> ~Lincoln >> >> On Thu, Sep 1, 2011 at 11:51 PM, Shane Bryzak >> wrote: >> Yeah, that's a good idea. Do you have plans to provide >> documentation as part of the Forge download? I'm thinking of >> the users who might have no/limited connectivity who won't be >> able to access the Forge docs online. Also, how does >> confluence work in conjunction with our documentation team? >> From my understanding all their tools for translating etc are >> based on Publican/Docbook. >> >> >> >> On 02/09/11 13:48, Lincoln Baxter, III wrote: >> > Actually, maybe the best thing to do is just to add a new >> > section to the Seam umbrella doc, with an HTML link to the >> > forge confluence space? >> > >> > On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III >> > wrote: >> > Ok. If you include beta1, the artifact for dist is: >> > >> > org.jboss.forge:forge-modules:1.0.0.Beta1 >> > >> > -- >> > Lincoln Baxter's Droid >> > http://ocpsoft.com >> > "Keep it Simple" >> > >> > >> > On Sep 1, 2011 7:52 PM, "Shane Bryzak" >> > wrote: >> > > Yep, I planned on extracting it in the forge >> > folder. >> > > >> > > On 02/09/11 09:43, Lincoln Baxter, III wrote: >> > >> >> > >> Also, if forge is unzipped. It should be done so >> > in its own subfolder. >> > >> >> > >> Ill try to catch you online tonight and make sure >> > you've got the right >> > >> artifact. (it moved temporarily during the jboss >> > modules transition. >> > >> >> > >> -- >> > >> Lincoln Baxter's Droid >> > >> http://ocpsoft.com >> > >> "Keep it Simple" >> > >> >> > >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" >> > > > >> > >> > wrote: >> > >> > >> > Well. The forge distribution doesn't contain >> > docs either. They are >> > >> purely >> > >> > online at this point. So I think just don't >> > worry about it. This >> > >> confluence >> > >> > thing is a bit of a pain in that regard. >> > >> > >> > >> > -- >> > >> > Lincoln Baxter's Droid >> > >> > http://ocpsoft.com >> > >> > "Keep it Simple" >> > >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" >> > > > >> > >> > wrote: >> > >> >> Unless an export could be automated as part of >> > the build process, I >> > >> >> don't think that's a good idea. How about we >> > just include the Forge >> > >> >> distribution extracted inside the Seam >> > distribution? The documentation >> > >> >> won't be combined with the main Seam docs, but >> > as long as it's in the >> > >> >> Forge distribution then a user should be able >> > to find it without too >> > >> >> much effort. >> > >> >> >> > >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: >> > >> >>> >> > >> >>> I'm not really sure how to do this, then. >> > There are no sources since >> > >> >>> the docs are in confluence. >> > >> >>> >> > >> >>> I suppose an export could work? >> > >> >>> >> > >> >>> -- >> > >> >>> Lincoln Baxter's Droid >> > >> >>> http://ocpsoft.com >> > >> >>> "Keep it Simple" >> > >> >>> >> > >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" >> > > > >> >> > >> > >> >>> > > >> wrote: >> > >> > >> >>> > The source artifact for the Forge docs were >> > being pulled in like >> > >> this: >> > >> >>> > >> > >> >>> > >> > >> >>> > org.jboss.seam.forge >> > >> >>> > >> > forge-reference-guide >> > >> >>> > 1.0.0-SNAPSHOT >> > >> >>> > sources >> > >> >>> > jar >> > >> >>> > >> > >> >>> > >> > >> >>> > When I update the version to 1.0.0.Beta1, >> > it can't find the source - >> > >> >>> was >> > >> >>> > the Beta1 source artifact published to >> > Maven? >> > >> >>> > >> > >> >>> > >> > >> >>> > >> > >> >>> > On 01/09/11 03:02, Lincoln Baxter, III >> > wrote: >> > >> >>> >> >> > https://docs.jboss.org/author/display/SEAMFORGE/Home >> > >> >>> >> >> > >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln >> > Baxter, III >> > >> >>> >> > > >> > >> > > > >> > >> >>> > > >> > >> > > >>> wrote: >> > >> >>> >> >> > >> >>> >> Just checking - the Forge docs are no >> > longer in SVN / are in >> > >> >>> >> Confluence; have you taken this into >> > account? >> > >> >>> >> >> > >> >>> >> Also, the which distribution are you >> > including? You could choose >> > >> >>> >> either Beta1 or the latest SNAPSHOT (which >> > is actually in a new >> > >> >>> >> location - moved back to the original >> > >> >>> >> org.jboss.forge:forge-distribution - >> > though it looks like the >> > >> >>> >> build hasn't deployed artifacts in a >> > little while - looking in to >> > >> >>> >> that) >> > >> >>> >> >> > >> >>> >> ~Lincoln >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane >> > Bryzak >> > >> >> > >> >>> > > > >> > >> >>> >> > > >> > >> > > >>> wrote: >> > >> >>> >> >> > >> >>> >> Module leads, >> > >> >>> >> >> > >> >>> >> Can you please review the list below and >> > confirm that the >> > >> >>> >> documentation >> > >> >>> >> chapters are correct for your module. >> > Also, I would like >> > >> >>> >> everyone to >> > >> >>> >> take a moment to review the module >> > documentation guidelines, >> > >> >>> >> as there >> > >> >>> >> were a number of breakages in the bundled >> > documentation build >> > >> >>> >> because >> > >> >>> >> the guidelines weren't adhered to, >> > particularly in the new >> > >> >>> >> modules for >> > >> >>> >> Seam 3.1: >> > >> >>> >> >> > >> >>> >> 1) Always prefix the filenames of your >> > documentation chapters >> > >> >>> >> with the >> > >> >>> >> name of your module. E.g. >> > security-authentication.xml, >> > >> >>> >> security-authorization.xml, etc. >> > >> >>> >> >> > >> >>> >> 2) Whenever you assign an ID to a docbook >> > element, such as a >> > >> >>> >> >> > >> >>> >> or

, ALWAYS prefix the id with >> > your module name. For >> > >> >>> >> example, >> > >> >>> >> or >> >

> > >> >>> >> id="security-getting-started">. As all of >> > the chapters for >> > >> >>> >> all modules >> > >> >>> >> are combined when building the bundled >> > documentation, all IDs >> > >> >>> >> must be >> > >> >>> >> unique. This is a particularly time >> > consuming problem to fix >> > >> >>> >> because >> > >> >>> >> the error output from the Maven docbook >> > plugin doesn't tell >> > >> >>> >> you which >> > >> >>> >> files are the problem ones. >> > >> >>> >> >> > >> >>> >> 3) When adding, renaming or deleting a >> > chapter of your >> > >> >>> >> documentation, >> > >> >>> >> please notify me of the changes so that I >> > can update >> > >> >>> >> bundled_master.xml. This file must be >> > manually kept up to >> > >> >>> >> date whenever >> > >> >>> >> any documentation changes are made. >> > >> >>> >> >> > >> >>> >> Thanks, >> > >> >>> >> Shane >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> > > DocBook XML V4.5//EN" >> > >> >>> >> >> > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> >> > >> >>> >> > > xmlns:xi="http://www.w3.org/2001/XInclude"> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam 3 >> > >> >>> >> Bundled Reference >> > Guide >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Forge >> > >> >>> >> >> > >> >>> >> > > href="forge-installation.xml" /> >> > >> >>> >> > > href="forge-creating-basic-webapp.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Solder >> > >> >>> >> >> > >> >>> >> > > href="solder-gettingstarted.xml"/> >> > >> >>> >> > > href="solder-programmingmodel.xml"/> >> > >> >>> >> > > href="solder-annotationliterals.xml"/> >> > >> >>> >> > > href="solder-elextensions.xml"/> >> > >> >>> >> > > href="solder-resourceloading.xml"/> >> > >> >>> >> >> > >> >>> >> > > href="solder-typeutilities.xml"/> >> > >> >>> >> > > href="solder-beanmanagerprovider.xml"/> >> > >> >>> >> > > href="solder-beanutilities.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> > > href="solder-defaultbeans.xml"/> >> > >> >>> >> > > href="solder-genericbeans.xml"/> >> > >> >>> >> > > href="solder-servicehandler.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Configuration >> > >> >>> >> > > href="config-introduction.xml"/> >> > >> >>> >> > > href="config-xml-provider.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Persistence >> > >> >>> >> > > href="persistence-general.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Transaction >> > >> >>> >> > > href="transaction-general.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Servlet >> > >> >>> >> > > href="servlet-introduction.xml"/> >> > >> >>> >> > > href="servlet-installation.xml"/> >> > >> >>> >> >> > >> >>> >> > > href="servlet-injectable_refs.xml"/> >> > >> >>> >> > > href="servlet-exception_handling.xml" /> >> > >> >>> >> > > href="servlet-beanmanager.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Security >> > >> >>> >> > > href="security-introduction.xml"/> >> > >> >>> >> > > href="security-authentication.xml"/> >> > >> >>> >> > > href="security-identitymanagement.xml"/> >> > >> >>> >> > > href="security-authentication-external.xml"/> >> > >> >>> >> > > href="security-authorization.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam International >> > >> >>> >> > > href="international-preface.xml" /> >> > >> >>> >> > > href="international-installation.xml" /> >> > >> >>> >> > > href="international-locales.xml" /> >> > >> >>> >> > > href="international-timezones.xml" /> >> > >> >>> >> > > href="international-messages.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Faces >> > >> >>> >> >> > >> >>> >> > > href="faces-installation.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Catch >> > >> >>> >> > > href="catch-introduction.xml"/> >> > >> >>> >> > > href="catch-installation.xml"/> >> > >> >>> >> > > href="catch-client_usage.xml"/> >> > >> >>> >> > > href="catch-advanced_usage.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Reports >> > >> >>> >> >> > >> >>> >> > > href="reports-installation.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Remoting >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> > > href="remoting-validation.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam REST >> > >> >>> >> >> > >> >>> >> > > href="rest-installation.xml" /> >> > >> >>> >> > > href="rest-exception-mapping.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> > > href="rest-dependencies.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam JCR >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam JMS >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> > > href="jms-resource-injection.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> > > href="jms-mapping-interfaces.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Validation >> > >> >>> >> > > href="validation-introduction.xml"/> >> > >> >>> >> > > href="validation-installation.xml"/> >> > >> >>> >> > > href="validation-dependency-injection.xml"/> >> > >> >>> >> > > href="validation-method-validation.xml"/> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> Seam Wicket >> > >> >>> >> >> > >> >>> >> > > href="wicket-installation.xml" /> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > _______________________________________________ >> > >> >>> >> seam-dev mailing list >> > >> >>> >> seam-dev at lists.jboss.org >> > >> > >> > > > >> > >> >>> > > >> > >> > > >> >> > >> >>> >> >> > https://lists.jboss.org/mailman/listinfo/seam-dev >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> -- >> > >> >>> >> Lincoln Baxter, III >> > >> >>> >> http://ocpsoft.com >> > >> >>> >> http://scrumshark.com >> > >> >>> >> "Keep it Simple" >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> >> > >> >>> >> -- >> > >> >>> >> Lincoln Baxter, III >> > >> >>> >> http://ocpsoft.com >> > >> >>> >> http://scrumshark.com >> > >> >>> >> "Keep it Simple" >> > >> >>> > >> > >> >> >> > > >> > >> > >> > >> > >> > -- >> > Lincoln Baxter, III >> > http://ocpsoft.com >> > http://scrumshark.com >> > "Keep it Simple" >> >> >> >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.com >> http://scrumshark.com >> "Keep it Simple" >> _______________________________________________ >> seam-dev mailing list >> seam-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev From mnovotny at redhat.com Fri Sep 2 06:52:01 2011 From: mnovotny at redhat.com (Marek Novotny) Date: Fri, 02 Sep 2011 12:52:01 +0200 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: <4E60B35A.1090504@redhat.com> References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>

<4E6052DD.1090602@redhat.com> <1314956113.2908.9.camel@localhost.localdomain> <4E60B35A.1090504@redhat.com> Message-ID: <1314960721.2908.11.camel@localhost.localdomain> I guess, it could be done by scripting a Web service https://issues.jboss.org/browse/ORG-1123 On Fri, 2011-09-02 at 20:43 +1000, Shane Bryzak wrote: > This would need to be automated for the Seam distribution build though. > Currently, all modules have their docbook sources published as Maven > artifacts, which is what we use to construct the bundled documentation. > > On 02/09/11 19:35, Marek Novotny wrote: > > What about using feature "Export to docbook" and then just generate > > standard jdocbook output in release process? > > > > https://docs.jboss.org/author/display/AUTHGUIDE/Exporting+content+to > > +DocBook+XML > > > > On Fri, 2011-09-02 at 00:15 -0400, Lincoln Baxter, III wrote: > >> I don't know. I don't really have plans to include docbook in the dist > >> until we get some better integration there from the .ORG team. I don't > >> see that happening, though, so until then, online docs are the way > >> people will be learning about forge. Our tools don't make this easy. > >> > >> I don't think the connectivity issue will be a problem. People can > >> always print or download the site for later if they have connectivity > >> issues. It might be nice (on confluence) to be able to have a 1-click > >> download, though. > >> > >> ~Lincoln > >> > >> On Thu, Sep 1, 2011 at 11:51 PM, Shane Bryzak > >> wrote: > >> Yeah, that's a good idea. Do you have plans to provide > >> documentation as part of the Forge download? I'm thinking of > >> the users who might have no/limited connectivity who won't be > >> able to access the Forge docs online. Also, how does > >> confluence work in conjunction with our documentation team? > >> From my understanding all their tools for translating etc are > >> based on Publican/Docbook. > >> > >> > >> > >> On 02/09/11 13:48, Lincoln Baxter, III wrote: > >> > Actually, maybe the best thing to do is just to add a new > >> > section to the Seam umbrella doc, with an HTML link to the > >> > forge confluence space? > >> > > >> > On Thu, Sep 1, 2011 at 7:54 PM, Lincoln Baxter, III > >> > wrote: > >> > Ok. If you include beta1, the artifact for dist is: > >> > > >> > org.jboss.forge:forge-modules:1.0.0.Beta1 > >> > > >> > -- > >> > Lincoln Baxter's Droid > >> > http://ocpsoft.com > >> > "Keep it Simple" > >> > > >> > > >> > On Sep 1, 2011 7:52 PM, "Shane Bryzak" > >> > wrote: > >> > > Yep, I planned on extracting it in the forge > >> > folder. > >> > > > >> > > On 02/09/11 09:43, Lincoln Baxter, III wrote: > >> > >> > >> > >> Also, if forge is unzipped. It should be done so > >> > in its own subfolder. > >> > >> > >> > >> Ill try to catch you online tonight and make sure > >> > you've got the right > >> > >> artifact. (it moved temporarily during the jboss > >> > modules transition. > >> > >> > >> > >> -- > >> > >> Lincoln Baxter's Droid > >> > >> http://ocpsoft.com > >> > >> "Keep it Simple" > >> > >> > >> > >> On Sep 1, 2011 7:41 PM, "Lincoln Baxter, III" > >> > >> > > >> > >> > wrote: > >> > > >> > >> > Well. The forge distribution doesn't contain > >> > docs either. They are > >> > >> purely > >> > >> > online at this point. So I think just don't > >> > worry about it. This > >> > >> confluence > >> > >> > thing is a bit of a pain in that regard. > >> > >> > > >> > >> > -- > >> > >> > Lincoln Baxter's Droid > >> > >> > http://ocpsoft.com > >> > >> > "Keep it Simple" > >> > >> > On Sep 1, 2011 6:05 PM, "Shane Bryzak" > >> > >> > > >> > >> > wrote: > >> > >> >> Unless an export could be automated as part of > >> > the build process, I > >> > >> >> don't think that's a good idea. How about we > >> > just include the Forge > >> > >> >> distribution extracted inside the Seam > >> > distribution? The documentation > >> > >> >> won't be combined with the main Seam docs, but > >> > as long as it's in the > >> > >> >> Forge distribution then a user should be able > >> > to find it without too > >> > >> >> much effort. > >> > >> >> > >> > >> >> On 02/09/11 01:22, Lincoln Baxter, III wrote: > >> > >> >>> > >> > >> >>> I'm not really sure how to do this, then. > >> > There are no sources since > >> > >> >>> the docs are in confluence. > >> > >> >>> > >> > >> >>> I suppose an export could work? > >> > >> >>> > >> > >> >>> -- > >> > >> >>> Lincoln Baxter's Droid > >> > >> >>> http://ocpsoft.com > >> > >> >>> "Keep it Simple" > >> > >> >>> > >> > >> >>> On Aug 31, 2011 5:09 PM, "Shane Bryzak" > >> > >> > >> > >> > > >> > >> >>> >> > >> wrote: > >> > > >> > >> >>> > The source artifact for the Forge docs were > >> > being pulled in like > >> > >> this: > >> > >> >>> > > >> > >> >>> > > >> > >> >>> > org.jboss.seam.forge > >> > >> >>> > > >> > forge-reference-guide > >> > >> >>> > 1.0.0-SNAPSHOT > >> > >> >>> > sources > >> > >> >>> > jar > >> > >> >>> > > >> > >> >>> > > >> > >> >>> > When I update the version to 1.0.0.Beta1, > >> > it can't find the source - > >> > >> >>> was > >> > >> >>> > the Beta1 source artifact published to > >> > Maven? > >> > >> >>> > > >> > >> >>> > > >> > >> >>> > > >> > >> >>> > On 01/09/11 03:02, Lincoln Baxter, III > >> > wrote: > >> > >> >>> >> > >> > https://docs.jboss.org/author/display/SEAMFORGE/Home > >> > >> >>> >> > >> > >> >>> >> On Wed, Aug 31, 2011 at 1:02 PM, Lincoln > >> > Baxter, III > >> > >> >>> >> >> > > >> > >> >> > > > >> > >> >>> >> > > >> > >> >> > >>> wrote: > >> > >> >>> >> > >> > >> >>> >> Just checking - the Forge docs are no > >> > longer in SVN / are in > >> > >> >>> >> Confluence; have you taken this into > >> > account? > >> > >> >>> >> > >> > >> >>> >> Also, the which distribution are you > >> > including? You could choose > >> > >> >>> >> either Beta1 or the latest SNAPSHOT (which > >> > is actually in a new > >> > >> >>> >> location - moved back to the original > >> > >> >>> >> org.jboss.forge:forge-distribution - > >> > though it looks like the > >> > >> >>> >> build hasn't deployed artifacts in a > >> > little while - looking in to > >> > >> >>> >> that) > >> > >> >>> >> > >> > >> >>> >> ~Lincoln > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> On Wed, Aug 31, 2011 at 12:14 AM, Shane > >> > Bryzak > >> > >> > >> > >> >>> >> > > > >> > >> >>> >> >> > > >> > >> >> > >>> wrote: > >> > >> >>> >> > >> > >> >>> >> Module leads, > >> > >> >>> >> > >> > >> >>> >> Can you please review the list below and > >> > confirm that the > >> > >> >>> >> documentation > >> > >> >>> >> chapters are correct for your module. > >> > Also, I would like > >> > >> >>> >> everyone to > >> > >> >>> >> take a moment to review the module > >> > documentation guidelines, > >> > >> >>> >> as there > >> > >> >>> >> were a number of breakages in the bundled > >> > documentation build > >> > >> >>> >> because > >> > >> >>> >> the guidelines weren't adhered to, > >> > particularly in the new > >> > >> >>> >> modules for > >> > >> >>> >> Seam 3.1: > >> > >> >>> >> > >> > >> >>> >> 1) Always prefix the filenames of your > >> > documentation chapters > >> > >> >>> >> with the > >> > >> >>> >> name of your module. E.g. > >> > security-authentication.xml, > >> > >> >>> >> security-authorization.xml, etc. > >> > >> >>> >> > >> > >> >>> >> 2) Whenever you assign an ID to a docbook > >> > element, such as a > >> > >> >>> >> > >> > >> >>> >> or

, ALWAYS prefix the id with > >> > your module name. For > >> > >> >>> >> example, > >> > >> >>> >> or > >> >

>> > >> >>> >> id="security-getting-started">. As all of > >> > the chapters for > >> > >> >>> >> all modules > >> > >> >>> >> are combined when building the bundled > >> > documentation, all IDs > >> > >> >>> >> must be > >> > >> >>> >> unique. This is a particularly time > >> > consuming problem to fix > >> > >> >>> >> because > >> > >> >>> >> the error output from the Maven docbook > >> > plugin doesn't tell > >> > >> >>> >> you which > >> > >> >>> >> files are the problem ones. > >> > >> >>> >> > >> > >> >>> >> 3) When adding, renaming or deleting a > >> > chapter of your > >> > >> >>> >> documentation, > >> > >> >>> >> please notify me of the changes so that I > >> > can update > >> > >> >>> >> bundled_master.xml. This file must be > >> > manually kept up to > >> > >> >>> >> date whenever > >> > >> >>> >> any documentation changes are made. > >> > >> >>> >> > >> > >> >>> >> Thanks, > >> > >> >>> >> Shane > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> >> > DocBook XML V4.5//EN" > >> > >> >>> >> > >> > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> > >> > >> >>> >> >> > xmlns:xi="http://www.w3.org/2001/XInclude"> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam 3 > >> > >> >>> >> Bundled Reference > >> > Guide > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Forge > >> > >> >>> >> > >> > >> >>> >> >> > href="forge-installation.xml" /> > >> > >> >>> >> >> > href="forge-creating-basic-webapp.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Solder > >> > >> >>> >> > >> > >> >>> >> >> > href="solder-gettingstarted.xml"/> > >> > >> >>> >> >> > href="solder-programmingmodel.xml"/> > >> > >> >>> >> >> > href="solder-annotationliterals.xml"/> > >> > >> >>> >> >> > href="solder-elextensions.xml"/> > >> > >> >>> >> >> > href="solder-resourceloading.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Configuration > >> > >> >>> >> >> > href="config-introduction.xml"/> > >> > >> >>> >> >> > href="config-xml-provider.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Persistence > >> > >> >>> >> >> > href="persistence-general.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Transaction > >> > >> >>> >> >> > href="transaction-general.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Servlet > >> > >> >>> >> >> > href="servlet-introduction.xml"/> > >> > >> >>> >> >> > href="servlet-installation.xml"/> > >> > >> >>> >> > >> > >> >>> >> >> > href="servlet-injectable_refs.xml"/> > >> > >> >>> >> >> > href="servlet-exception_handling.xml" /> > >> > >> >>> >> >> > href="servlet-beanmanager.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Security > >> > >> >>> >> >> > href="security-introduction.xml"/> > >> > >> >>> >> >> > href="security-authentication.xml"/> > >> > >> >>> >> >> > href="security-identitymanagement.xml"/> > >> > >> >>> >> >> > href="security-authentication-external.xml"/> > >> > >> >>> >> >> > href="security-authorization.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam International > >> > >> >>> >> >> > href="international-preface.xml" /> > >> > >> >>> >> >> > href="international-installation.xml" /> > >> > >> >>> >> >> > href="international-locales.xml" /> > >> > >> >>> >> >> > href="international-timezones.xml" /> > >> > >> >>> >> >> > href="international-messages.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Faces > >> > >> >>> >> > >> > >> >>> >> >> > href="faces-installation.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Catch > >> > >> >>> >> >> > href="catch-introduction.xml"/> > >> > >> >>> >> >> > href="catch-installation.xml"/> > >> > >> >>> >> >> > href="catch-client_usage.xml"/> > >> > >> >>> >> >> > href="catch-advanced_usage.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Reports > >> > >> >>> >> > >> > >> >>> >> >> > href="reports-installation.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Remoting > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> >> > href="remoting-validation.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam REST > >> > >> >>> >> > >> > >> >>> >> >> > href="rest-installation.xml" /> > >> > >> >>> >> >> > href="rest-exception-mapping.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> >> > href="rest-dependencies.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam JCR > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam JMS > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> >> > href="jms-resource-injection.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> >> > href="jms-mapping-interfaces.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Validation > >> > >> >>> >> >> > href="validation-introduction.xml"/> > >> > >> >>> >> >> > href="validation-installation.xml"/> > >> > >> >>> >> >> > href="validation-dependency-injection.xml"/> > >> > >> >>> >> >> > href="validation-method-validation.xml"/> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> Seam Wicket > >> > >> >>> >> > >> > >> >>> >> >> > href="wicket-installation.xml" /> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > _______________________________________________ > >> > >> >>> >> seam-dev mailing list > >> > >> >>> >> seam-dev at lists.jboss.org > >> > > >> > >> >> > > > >> > >> >>> >> > > >> > >> >> > >> > >> > >> >>> >> > >> > https://lists.jboss.org/mailman/listinfo/seam-dev > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> -- > >> > >> >>> >> Lincoln Baxter, III > >> > >> >>> >> http://ocpsoft.com > >> > >> >>> >> http://scrumshark.com > >> > >> >>> >> "Keep it Simple" > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> > >> > >> >>> >> -- > >> > >> >>> >> Lincoln Baxter, III > >> > >> >>> >> http://ocpsoft.com > >> > >> >>> >> http://scrumshark.com > >> > >> >>> >> "Keep it Simple" > >> > >> >>> > > >> > >> >> > >> > > > >> > > >> > > >> > > >> > > >> > -- > >> > Lincoln Baxter, III > >> > http://ocpsoft.com > >> > http://scrumshark.com > >> > "Keep it Simple" > >> > >> > >> > >> > >> > >> -- > >> Lincoln Baxter, III > >> http://ocpsoft.com > >> http://scrumshark.com > >> "Keep it Simple" > >> _______________________________________________ > >> seam-dev mailing list > >> seam-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/seam-dev > -- Marek Novotny -- Seam and WFK Product Lead Red Hat Czech s.r.o. Purkynova 99 612 45 Brno Email: mnovotny at redhat.com Office phone: +420 532 294 287, ext. 82-62 087 mobile: +420 608 509 230 From sbryzak at redhat.com Fri Sep 2 06:57:42 2011 From: sbryzak at redhat.com (Shane Bryzak) Date: Fri, 02 Sep 2011 20:57:42 +1000 Subject: [seam-dev] Bundled distribution documentation In-Reply-To: <1314960721.2908.11.camel@localhost.localdomain> References: <4E5DB50C.3030409@redhat.com>

<4E5EA2EA.2000109@redhat.com> <4E6001BD.4070301@redhat.com> <4E601AA2.7090705@redhat.com>