[Jakarta Wiki] Update of "SpecificationRepository" by HenriYandell
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification. The following page has been changed by HenriYandell: http://wiki.apache.org/jakarta/SpecificationRepository -- * To accept that one day a TLP may be preferable * To offer advice (when asked) on the creation of clean room API implementations + == Thoughts == + + Hen: Might want to consider an m2 style repository for specs as the foundation for the above. + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Update of "SpecificationRepository" by RobertBurrellDonkin
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification. The following page has been changed by RobertBurrellDonkin: http://wiki.apache.org/jakarta/SpecificationRepository -- = API Specification Repository = + + == Status == + + Very rough and ready first draft. Please feel free to dive in and edit. == Rationale == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Trivial Update of "SpecificationRepository" by MartinCooper
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification. The following page has been changed by MartinCooper: http://wiki.apache.org/jakarta/SpecificationRepository The comment on the change is: Fix word-o's. -- == Rationale == - Apache has many codebases scattered throughout various projects that containing clean room implementations of specification APIs. + Apache has many codebases scattered throughout various projects that contain clean room implementations of specification APIs. Though these are extremely useful, there is no central location where users, developers or committers can find which specifications Apache has clean room API implementations for. @@ -21, +21 @@ * existing Apache committers to collaborate on clean room specification API implementations in Java * existing Apache clean room specification API implementations in Java to be maintained * new specification API implementations in Java to be homed at Apache after vetting and approval by the incubator - * To documentation the legal difficulties around clean room implementations + * To document the legal difficulties around clean room implementations * To accept that some projects may prefer to maintain their own APIs - * To accept that one day a TLP may be preferrable + * To accept that one day a TLP may be preferable * To offer advice (when asked) on the creation of clean room API implementations - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Specification API Repository [WAS Re: [Jakarta Wiki] Update of "SpecificationRepository" by RobertBurrellDonkin]
i've thrown together something speculative based on comments in http://mail-archives.apache.org/mod_mbox/incubator-general/200606.mbox/% [EMAIL PROTECTED] i think that jakarta might be a good home for a central point for specification API implementations in Java and is definitely less work than creating a new API. if anyone has strong objections to jakarta hosting this, please post them here. otherwise, it's probably better to join the thread over in the incubator. - robert On Wed, 2006-06-07 at 20:15 +, Apache Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for > change notification. > > The following page has been changed by RobertBurrellDonkin: > http://wiki.apache.org/jakarta/SpecificationRepository > > The comment on the change is: > First draft for a proposal to host an API specification [EMAIL PROTECTED] > > New page: > = API Specification Repository = > > == Rationale == > > Apache has many codebases scattered throughout various projects that > containing clean room implementations of specification APIs. > > Though these are extremely useful, there is no central location where users, > developers or committers can find which specifications Apache has clean room > API implementations for. > > In addition, there is no space where existing committers from different > projects can collaborate on clean room API implementations of mutual benefit. > > There are various legal issues which arise from clean room API > implementations. A central point of contact should make it easier to manage > these issues. > > Jakarta seems an ideal candidate for hosting a central specification > repository. Jakarta is well known amongst Java users. Jakarta is also neutral > development ground. > > == Manifesto == > > * To maintain a central index of Specification API's with clean room Apache > implementations in Java whether hosted in a repository @ Jakarta or elsewhere > * To host a repository allowing: >* existing Apache committers to collaborate on clean room specification > API implementations in Java >* existing Apache clean room specification API implementations in Java to > be maintained >* new specification API implementations in Java to be homed at Apache > after vetting and approval by the incubator > * To documentation the legal difficulties around clean room implementations > * To accept that some projects may prefer to maintain their own APIs > * To accept that one day a TLP may be preferrable > * To offer advice (when asked) on the creation of clean room API > implementations > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > signature.asc Description: This is a digitally signed message part
[Jakarta Wiki] Update of "SpecificationRepository" by RobertBurrellDonkin
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification. The following page has been changed by RobertBurrellDonkin: http://wiki.apache.org/jakarta/SpecificationRepository The comment on the change is: First draft for a proposal to host an API specification [EMAIL PROTECTED] New page: = API Specification Repository = == Rationale == Apache has many codebases scattered throughout various projects that containing clean room implementations of specification APIs. Though these are extremely useful, there is no central location where users, developers or committers can find which specifications Apache has clean room API implementations for. In addition, there is no space where existing committers from different projects can collaborate on clean room API implementations of mutual benefit. There are various legal issues which arise from clean room API implementations. A central point of contact should make it easier to manage these issues. Jakarta seems an ideal candidate for hosting a central specification repository. Jakarta is well known amongst Java users. Jakarta is also neutral development ground. == Manifesto == * To maintain a central index of Specification API's with clean room Apache implementations in Java whether hosted in a repository @ Jakarta or elsewhere * To host a repository allowing: * existing Apache committers to collaborate on clean room specification API implementations in Java * existing Apache clean room specification API implementations in Java to be maintained * new specification API implementations in Java to be homed at Apache after vetting and approval by the incubator * To documentation the legal difficulties around clean room implementations * To accept that some projects may prefer to maintain their own APIs * To accept that one day a TLP may be preferrable * To offer advice (when asked) on the creation of clean room API implementations - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Update of "GroupingProposals" by RobertBurrellDonkin
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification. The following page has been changed by RobertBurrellDonkin: http://wiki.apache.org/jakarta/GroupingProposals New page: = Grouping Proposals = Proposals for groupings of interested communities * SpecificationRepository - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Update of "FrontPage" by RobertBurrellDonkin
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification. The following page has been changed by RobertBurrellDonkin: http://wiki.apache.org/jakarta/FrontPage The comment on the change is: New way of organising Jakarta -- * ["OneCommunityProposals"] * ["SubProjectProposals"] + * ["GroupingProposals"] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project jakarta-site2 (in module jakarta-site2) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jakarta-site2 has an issue affecting its community integration. This issue affects 2 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-regexp-package : Java Regular Expression package - jakarta-site2 : The Jakarta site Full details are available at: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/gump_work/build_jakarta-site2_jakarta-site2.html Work Name: build_jakarta-site2_jakarta-site2 (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only '-Dversion.projectfile=$Revision: 411418 $' -Dgump.run=true '-Ddate.projectfile=$Date: 2006-06-03 03:39:13 -0700 (Sat, 03 Jun 2006) $' [Working Directory: /usr/local/gump/public/workspace/jakarta-site2] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] Version $Revision: 412202 $ Last updated: $Date: 2006-06-06 12:56:37 -0700 (Tue, 06 Jun 2006) $ CheckXSL: [xslt] Processing /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/site.xsl to /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp [xslt] Loading stylesheet /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/sitechk.xsl [delete] Deleting: /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp [xslt] Processing /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/news2content.xsl to /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp [xslt] Loading stylesheet /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/sitechk.xsl [delete] Deleting: /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp news-gen: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-site2/target/news-gen [xslt] Processing /x1/gump/public/workspace/jakarta-site2/news.xml to /x1/gump/public/workspace/jakarta-site2/docs/site/rss.xml [xslt] Loading stylesheet /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/news2content.xsl [xslt] /x1/gump/public/workspace/jakarta-site2/news2content.xsl:28:36: Error! Had IO Exception with stylesheet file: common.xsl Cause: java.io.FileNotFoundException: /x1/gump/public/workspace/jakarta-site2/common.xsl (No such file or directory) [xslt] : Fatal Error! javax.xml.transform.TransformerException: ElemTemplateElement error: output-date Cause: javax.xml.transform.TransformerException: ElemTemplateElement error: output-date [xslt] Failed to process /x1/gump/public/workspace/jakarta-site2/news.xml BUILD FAILED /x1/gump/public/workspace/jakarta-site2/build.xml:45: Fatal error during transformation Total time: 1 second - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2607062006, vmgump.apache.org:vmgump-public:2607062006 Gump E-mail Identifier (unique within run) #37. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project jakarta-site2 (in module jakarta-site2) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project jakarta-site2 has an issue affecting its community integration. This issue affects 2 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-regexp-package : Java Regular Expression package - jakarta-site2 : The Jakarta site Full details are available at: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/gump_work/build_jakarta-site2_jakarta-site2.html Work Name: build_jakarta-site2_jakarta-site2 (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only '-Dversion.projectfile=$Revision: 411418 $' -Dgump.run=true '-Ddate.projectfile=$Date: 2006-06-03 03:39:13 -0700 (Sat, 03 Jun 2006) $' [Working Directory: /usr/local/gump/public/workspace/jakarta-site2] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] Version $Revision: 412202 $ Last updated: $Date: 2006-06-06 12:56:37 -0700 (Tue, 06 Jun 2006) $ CheckXSL: [xslt] Processing /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/site.xsl to /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp [xslt] Loading stylesheet /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/sitechk.xsl [delete] Deleting: /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp [xslt] Processing /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/news2content.xsl to /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp [xslt] Loading stylesheet /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/sitechk.xsl [delete] Deleting: /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/dummy.tmp news-gen: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-site2/target/news-gen [xslt] Processing /x1/gump/public/workspace/jakarta-site2/news.xml to /x1/gump/public/workspace/jakarta-site2/docs/site/rss.xml [xslt] Loading stylesheet /x1/gump/public/workspace/jakarta-site2/xdocs/stylesheets/news2content.xsl [xslt] /x1/gump/public/workspace/jakarta-site2/news2content.xsl:28:36: Error! Had IO Exception with stylesheet file: common.xsl Cause: java.io.FileNotFoundException: /x1/gump/public/workspace/jakarta-site2/common.xsl (No such file or directory) [xslt] : Fatal Error! javax.xml.transform.TransformerException: ElemTemplateElement error: output-date Cause: javax.xml.transform.TransformerException: ElemTemplateElement error: output-date [xslt] Failed to process /x1/gump/public/workspace/jakarta-site2/news.xml BUILD FAILED /x1/gump/public/workspace/jakarta-site2/build.xml:45: Fatal error during transformation Total time: 1 second - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-site2/jakarta-site2/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2607062006, vmgump.apache.org:vmgump-public:2607062006 Gump E-mail Identifier (unique within run) #37. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
