roxspring 2002/12/03 04:45:56
Modified: xdocs/site/news index.xml
Added: xdocs/site/news 200211.xml
Log:
Added draft1 of the November newsletter
Revision Changes Path
1.7 +1 -0 jakarta-site/xdocs/site/news/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-site/xdocs/site/news/index.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.xml 6 Nov 2002 12:02:05 -0000 1.6
+++ index.xml 3 Dec 2002 12:45:56 -0000 1.7
@@ -31,6 +31,7 @@
</section>
<section name="Archive">
<ul>
+ <li><a href="./200211.html">November 2002</a></li>
<li><a href="./200210.html">October 2002</a></li>
<li><a href="./200208.html">August 2002</a></li>
<li><a href="./200207.html">July 2002</a></li>
1.1 jakarta-site/xdocs/site/news/200211.xml
Index: 200211.xml
===================================================================
<?xml version="1.0"?>
<!--
Contributors This month:
Rob Oxspring <[EMAIL PROTECTED]>
James Strachan <[EMAIL PROTECTED]>
Henri Yandell <[EMAIL PROTECTED]>
Otis Gospodnetic <[EMAIL PROTECTED]>
Ted Husted [[EMAIL PROTECTED]]
Suribada [[EMAIL PROTECTED]]
Leo Simons <[EMAIL PROTECTED]>
Ceki Gülcü <[EMAIL PROTECTED]>
-->
<document>
<properties>
<author email="[EMAIL PROTECTED]">Rob Oxspring</author>
<title>Jakarta Newsletter - November 2002 - #5</title>
</properties>
<body>
<section name="Jakarta Newsletter">
<p>
<b>Issue:</b> 5
<br/>
<b>Date:</b> November 2002
<br/>
<b>Url:</b> <a
href="http://jakarta.apache.org/site/news/200211.html";>http://jakarta.apache.org/site/news/200211.html</a>
</p>
<p>It has been a quiet month. Commons has killed on old component and
welcomed a new one, while other components have kept up fixes, features and releases.
Elsewhere there has been more discussion about the infrastructure and community at
Apache, and an attempt to be helpful to those developers using IDEs</p>
<p>As always, I want to thank those who contributed and hope that you
enjoy the read. If you would like to comment further on any of the highlighted
discussions then please do so on the <a
href="http://jakarta.apache.org/site/mail.html";>appropriate list</a>, if you want to
comment on the newsletter itself then please point your comments to <a
href="mailto:[EMAIL PROTECTED]?subject=[Newsletter]";>[EMAIL PROTECTED]</a>.</p>
<p>Rob Oxspring</p>
<subsection name="Contents">
<li><a href="#General">General</a></li>
<li><a href="#Commons">Commons</a></li>
</subsection>
</section>
<section name="General">
<p><i>"Ideas, suggestions, and comments on the overall Jakarta
project"</i></p>
<p><b>Editor:</b> Rob Oxspring</p>
<p>Andrew Oliver decided to do something about the Java developers who
"cut their teeth" on IDEs and don't understand the intricacies of the command line
tools that are used under the hood. The page [<a href="#General1">1</a>] was welcomed
by many and was rapidly expanded [<a href="#General2">2</a>] and should hopefully be a
resource useful to a wide range of developers.</p>
<p>
Duplicated or pointless import statements appear over time in most Java
code. This is an issue that Tom Copeland wanted to tackle, and sparked a few
iterations [<a href="#General3">3</a>] of the "bad imports" report [<a
href="#General4">4</a>].
</p>
<p>
<li><a name="General1">[1] - <a
href="http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&from=281536&to=281536&count=39&by=thread&paged=false";>http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&from=281536&to=281536&count=39&by=thread&paged=false</a></a></li>
<li><a name="General2">[2] - <a
href="http://jakarta.apache.org/site/idedevelopers.html
">http://jakarta.apache.org/site/idedevelopers.html </a></a></li>
<li><a name="General3">[3] - <a
href="http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&by=thread&from=271386";>http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&by=thread&from=271386</a></a></li>
<li><a name="General4">[4] - <a
href="http://cvs.apache.org/~tcopeland/jakarta_bad_imports.htm";>http://cvs.apache.org/~tcopeland/jakarta_bad_imports.htm</a></a></li>
</p>
</section>
<section name="Commons">
<p><i>"creating and maintaining reusable Java
components"</i></p>
<p><b>Editor:</b> Henri Yandell</p>
<subsection name="Releases">
<p>November saw the release of two new projects from Jakarta
Commons, and the release of a bugfix for another project.</p>
<p>Commons Validator 1.0 was mentioned in the previous newsletter.
It was released on November 1st and is a validation framework from the Struts
people.</p>
<p>Commons CLI 1.0 was released on the 6th of November and is an API
for parsing command line arguments. It is the direct descendant of 3 older argument
parsing APIs and other APIs have affected it over mail list discussions. This gives it
a very high pedigree and makes it a great choice for handling the command line.</p>
<p>Commons Lang 1.0.1 is the first bugfix release for the Lang
project. There are no new APIs or deprecated functionality, so all Commons Lang users
are advised to upgrade, although the bugfixes are not earth-shattering.</p>
<p>
<li><a name="CommonsRelease1">[1] - <a
href="http://jakarta.apache.org/builds/jakarta-commons/release/commons-validator/v1.0/RELEASE-NOTES.txt";>http://jakarta.apache.org/builds/jakarta-commons/release/commons-validator/v1.0/RELEASE-NOTES.txt</a></a></li>
<li><a name="CommonsRelease2">[2] - <a
href="http://jakarta.apache.org/builds/jakarta-commons/release/commons-cli/v1.0/RELEASE-NOTES.txt";>http://jakarta.apache.org/builds/jakarta-commons/release/commons-cli/v1.0/RELEASE-NOTES.txt</a></a></li>
<li><a name="CommonsRelease3">[3] - <a
href="http://jakarta.apache.org/builds/jakarta-commons/release/commons-lang/v1.0.1/RELEASE-NOTES.txt";>http://jakarta.apache.org/builds/jakarta-commons/release/commons-lang/v1.0.1/RELEASE-NOTES.txt</a></a></li>
</p>
</subsection>
<subsection name="Gossip">
<p>November was quiet for Commons, as it was for all of Apache.
Indeed, the Commons mail list dropped by 35%.</p>
<p>The Patterns project in the Sandbox has been mothballed as its
code is to go into Commons Lang and Commons Util. Work has begun on moving the
BeanUtils reflection code over to Commons Lang and various BeanUtils bugs were dealt
with.</p>
<p>A new database utility project has been proposed with generic
JDBC(tm) utilities and lives under the name of 'DbUtils' in the sandbox and a project
named 'attributes' has been proposed to handle runtime metadata attributes.</p>
<p>
<li><a name="CommonsRelease1">[1] - <a
href="http://jakarta.apache.org/commons/sandbox/attributes/";>http://jakarta.apache.org/commons/sandbox/attributes/</a></a></li>
</p>
</subsection>
<subsection name="Jelly">
<p><b>Editor:</b> James Strachan</p>
<p>Here are the main changes that have happened recently on the
Jelly project...</p>
<p>
<li>XPath sorting now added to the XML library</li>
<li><j:useBean> can now construct beans with constructor
parameters</li>
<li>better reporting of JellyUnit failures, line numbers,
expressions etc.</li>
<li>XMLUnit library added for unit testing of XML inside
JellyUnit</li>
</p>
<p>So now JellyUnit can support the following XML unit testing
constructs</p>
<p>
<li>XPath based assertions via <test:assert
xpath="..."/></li>
<li>schema validation via the jelly:validate library, testing XML
against DTDs, XML Schema, RelaxNG etc</li>
<li>comparing 2 documents for equality using the new XMLUnit
library</li>
<li>performing XSLT on some XML and then then performing any of the
above</li>
<li>parsing HTML via the Neko parser and treating it as XML in any
of the above</li>
</p>
<p>As well as Jexl based assertions, assertEquals and a new
<assertThrown> tag to test for exceptions being thrown in Jelly scripts.</p>
</subsection>
</section>
<!--
<section name="Avalon">
<p><i>"The Avalon project is an effort to create, design, develop
and maintain a common framework and set of components for applications written using
the Java language"</i></p>
<p><b>Editor:</b> Leo Simons</p>
<p>Things have been so active, I can only provide a small sampling of
what's been going on :)</p>
<p>Like many projects at apache, avalon has been busy discussing how to
fit into the new structure that is currently in the works. Being one of the projects
that has suffered most from 'scope creep', there is a lot to think about [<a
href="#Avalon1">1</a>,<a href="#Avalon2">2</a>,<a href="#Avalon3">3</a>]. With avalon
committers on the Incubator and Commons PMCs, there's definately a promising
perspective.</p>
<p>There have also been quite a few bug fixes and enhancements in
various places (like Avalon Phoenix now providing good support for using log4j [<a
href="#Avalon4">4</a>] and allowing customizable classloader trees [<a
href="#Avalon5">5</a>]). There's been work integrating catalina and jo! [<a
href="#Avalon6">6</a>] with phoenix.</p>
<p>Following extended discussion [<a href="#Avalon7">7</a>,<a
href="#Avalon8">8</a>,<a href="#Avalon9">9</a>], avalon also gained an implementation
of the delegate design pattern.</p>
<p>
<li><a name="Avalon1">[1] - <a
href="http://marc.theaimsgroup.com/?t=103578734000006&r=1&w=2";>http://marc.theaimsgroup.com/?t=103578734000006&r=1&w=2</a></a></li>
<li><a name="Avalon2">[2] - <a
href="http://marc.theaimsgroup.com/?t=103597891500005&r=1&w=2";>http://marc.theaimsgroup.com/?t=103597891500005&r=1&w=2</a></a></li>
<li><a name="Avalon3">[3] - <a
href="http://marc.theaimsgroup.com/?t=103545268100001&r=1&w=2";>http://marc.theaimsgroup.com/?t=103545268100001&r=1&w=2</a></a></li>
<li><a name="Avalon4">[4] - <a
href="http://marc.theaimsgroup.com/?t=103546933700004&r=1&w=2";>http://marc.theaimsgroup.com/?t=103546933700004&r=1&w=2</a></a></li>
<li><a name="Avalon5">[5] - <a
href="http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&by=thread&from=268738";>http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&by=thread&from=268738</a></a></li>
<li><a name="Avalon6">[6] - <a
href="http://jakarta.apache.org/avalon/apps/apps/sevak/";>http://jakarta.apache.org/avalon/apps/apps/sevak/</a></a></li>
<li><a name="Avalon7">[7] - <a
href="http://marc.theaimsgroup.com/?t=103364295500007&r=1&w=2";>http://marc.theaimsgroup.com/?t=103364295500007&r=1&w=2</a></a></li>
<li><a name="Avalon8">[8] - <a
href="http://marc.theaimsgroup.com/?t=103362114600002&r=1&w=2";>http://marc.theaimsgroup.com/?t=103362114600002&r=1&w=2</a></a></li>
<li><a name="Avalon9">[9] - <a
href="http://marc.theaimsgroup.com/?t=103370102300001&r=1&w=2";>http://marc.theaimsgroup.com/?t=103370102300001&r=1&w=2</a></a></li>
</p>
</section>
<section name="Korean Jakarta">
<p><i>"Jakarta Site in Korean"</i></p>
<p><b>Editor:</b> Jaechun Noh</p>
<p>Java developers in Korea have more interests in jakarta project than
all the time. But many of them have trouble directly reading original English site.
Most problems we are encounterd during development using jakarta projects can be
solved only if we search for site manuals. We want many people directly searching
informations by their convenient languages.</p>
<p>Currently about 35 people participate in the project, and Hangul
translation of 13 subprojects is in progress. Tomcat, Struts, Ant Among those have
many volunteers more than three since interests in those subprojects are higher than
any others in Korea. At the end of this year, we plan to finish all documents in
Tomcat 4.X, Struts 1.0.2, POI, JMeter, Ant etc. We are all working with pure purpose
without any support from commercial corporation and without any reward.</p>
<p>
<li><a name="Korean Jakarta1">[1] - <a
href="http://www.apache-korea.org/";>http://www.apache-korea.org/</a></a></li>
</p>
</section>
<section name="Log4j">
<p><i>"allows developers to control which log statements are output
with arbitrary granularity"</i></p>
<p><b>Editor:</b> Ceki Gülcü</p>
<p>The main branch of the CVS repository is now in quasi-sync with the
1.2 branch [<a href="#Log4j1">1</a>]. Work on log4j version 1.3 has begun in
earnest.</p>
<p>The committers have voted to require JDK 1.2 and drop support for JDK
1.1 [<a href="#Log4j2">2</a>].</p>
<p>The DOMConfigurator is now able to parse configuration files that
contains component specific elements [<a href="#Log4j3">3</a>]. This significantly
improves on existing capabilities. Many thanks to James Strachan for enhacing jelly
to deal with dynamic properties [<a href="#Log4j4">4</a>]. The idea to use jelly in
log4j has been shelved for the moment [<a href="#Log4j5">5</a>].</p>
<p>Chris Nokes [<a href="#Log4j6">6</a>] has proposed significant
architectural changes to improve memory usage.</p>
<p>
<li><a name="Log4j1">[1] - <a
href="http://marc.theaimsgroup.com/?l=log4j-dev&m=103420386032223&w=2";>http://marc.theaimsgroup.com/?l=log4j-dev&m=103420386032223&w=2</a></a></li>
<li><a name="Log4j2">[2] - <a
href="http://marc.theaimsgroup.com/?l=log4j-dev&m=103366188809758&w=2";>http://marc.theaimsgroup.com/?l=log4j-dev&m=103366188809758&w=2</a></a></li>
<li><a name="Log4j3">[3] - <a
href="http://marc.theaimsgroup.com/?l=log4j-dev&m=103477613024786&w=2";>http://marc.theaimsgroup.com/?l=log4j-dev&m=103477613024786&w=2</a></a></li>
<li><a name="Log4j4">[4] - <a
href="http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103479230214745&w=2";>http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103479230214745&w=2</a></a></li>
<li><a name="Log4j5">[5] - <a
href="http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103479543318721&w=2";>http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=103479543318721&w=2</a></a></li>
<li><a name="Log4j6">[6] - <a
href="http://marc.theaimsgroup.com/?t=103471060500008&r=1&w=2";>http://marc.theaimsgroup.com/?t=103471060500008&r=1&w=2</a></a></li>
</p>
</section>
<section name="Lucene">
<p><i>"a high-performance, full-featured text search
engine"</i></p>
<p><b>Editor:</b> Otis Gospodnetic</p>
<p>The biggest change to Lucene since Auguest was the addition of a
mechanism that allows Document and Field boosting [<a href="#Lucene1">1</a>]. This
change allows one to give additional boost to certain documents and/or fields, which
results in those documents getting a higher ranking when they match a query.</p>
<p>A new method, setPositionIncrement() in Token class was added. This
permits, for the purpose of phrase searching, placing multiple terms in a single
position. This is useful with stemmers that produce multiple possible stems for a
word. This also permits the introduction of gaps between terms, so that terms which
are adjacent in a token stream will not be matched by and exact phrase query. This
makes it possible, e.g., to build an analyzer where phrases are not matched over stop
words which have been removed. Finally, repeating a token with an increment of zero
can also be used to boost scores of matches on that token.</p>
<p>Boris Okner [<a href="#Lucene2">2</a>] made a big contribution with
his Russian Analyzer.</p>
<p>There was some smaller bug fixes, new classes (QueryFilter),
IndexWriter class got getAnalyzer() method, etc.</p>
<p>
<li><a name="Lucene1">[1] - <a
href="http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgId=417758";>http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgId=417758</a></a></li>
<li><a name="Lucene2">[2] - <a
href="http://nagoya.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&by=author&from=10162&to=10162&first=1&count=5";>http://nagoya.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&by=author&from=10162&to=10162&first=1&count=5</a></a></li>
</p>
</section>
<section name="POI">
<p><i>"APIs for manipulating various file formats based upon
Microsoft's OLE 2 Compound Document format"</i></p>
<p><b>Editor:</b> Andrew C Oliver</p>
<p>POI put out a new development release that includes Macro support</p>
<p>Shawn Laubach was voted a committer</p>
<p>There was renewed interest in HDF our word port and several new folks
expressed an interest in volunteering</p>
<p>Andy discovered the default encoding on Redhat 8 is now UTF-8 and not
8859-1, hence finally we have a machine to test POI with a different default encoding
and can fix that bug.</p>
</section>
<section name="Struts">
<p><b>Editor:</b>Ted Husted</p>
<p>The Struts team is proud to welcome 4 new Committers this month,
David Karr, Eddie Bush, David Graham, and James Mitchell [<a
href="#Struts1">1</a>].</p>
<p>Everyone is working steadily toward the release of Struts 1.1 beta 3.
To help keep everyone on track, the team added a Development Roadmap [<a
href="#Struts2">2</a>].</p>
<p>There are a number of "nice to haves" that won't make Struts 1.1
which are now slated for Struts 1.2. Farther down the road, Struts 2.0 will rely upon
the new standards, like JavaServer Faces and JSTL. </p>
<p>The platform for Struts 1.1 will remain Servlet 2.2 and JSP 1.1.
However, a Struts JSTL taglib is available in the nightly build contrib directory and
will be released with Struts 1.1 as a separate download. </p>
<p>Solid Struts support for the other new standard, Struts JavaServer
Faces, is under development, but cannot be released quite yet [<a
href="#Struts1">3</a>].</p>
<p>Meanwhile, the Struts User list will continue to enjoy its "casual
Friday" policy. Off-topic messages are tolerated on Fridays so long as the message is
prefixed with the token [FRIDAY]. Posting [FRIDAY] articles on any other weekday is
strongly discouraged. </p>
<p>
<li><a name="Struts1">[1] - <a
href="http://jakarta.apache.org/struts/volunteers.html";>http://jakarta.apache.org/struts/volunteers.html</a></a></li>
<li><a name="Struts2">[2] - <a
href="http://jakarta.apache.org/struts/status.html";>http://jakarta.apache.org/struts/status.html</a></a></li>
<li><a name="Struts3">[3] - <a
href="http://jakarta.apache.org/struts/proposals/struts-faces.html";>http://jakarta.apache.org/struts/proposals/struts-faces.html</a></a></li>
</p>
</section>
-->
</body>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
