Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-jmeter Wiki" 
for change notification.

The following page has been changed by JMeterAdmin:
http://wiki.apache.org/jakarta-jmeter/FutureReleases

------------------------------------------------------------------------------
  This section is for non-functional changes, e.g. code re-organisation etc.
  
   * Use Java 1.5 for building, but only require 1.4 for running. Is this easy 
to do? Can it be done in Eclipse?
-  * Look into warnings when compiling code, some deprecated code should be 
replaced
   * Currently, Apache Avalon seems to be used for logging. Avalon seems to 
have stalled, should we move to log4j ?
    * I looked into adding a GUI / dialog for "Help->View log" to easily view 
the jmeter log file from the application itself.
     * Seems to be some open source tools available for log4j which does that 
out of the box.
@@ -98, +97 @@

    * Alternatively, move to Commons Logging (as used by Http``Client currently)
    * Or perhaps SL4J - http://www.slf4j.org/
    * What are the risks with continuing to use Avalon, if Avalon is not 
maintained anymore ?
-   * Remark: Http``Components project is considering migrating Http``Client 
4.0 branch off Commons Logging to another logging framework as Commons Logging 
currently appears unmaintained and the prospects of its further development 
remain unclear. [Does it need any development? sebb] It may be worthwhile to 
ensure both projects use the same logging framework / compatible logging 
frameworks. [Agreed: sebb]
+   * Remark: Http``Components project is considering migrating Http``Client 
4.0 branch off Commons Logging to another logging framework as Commons Logging 
currently appears unmaintained and the prospects of its further development 
remain unclear. [There has just been a new release: sebb] It may be worthwhile 
to ensure both projects use the same logging framework / compatible logging 
frameworks. [Agreed: sebb]
   * Upgrade to httpclient4 ? httpclient4 is still only in Alpha. Should / 
could we have one sampler class using httpclient3 and one httpclient4 ? 
HttpClient 4 will require Java 1.5, and won't be available until Q2/Q3 2008.
   * Reorganise documentation
    * component_reference is getting much too big. This will require changes to 
the help system.
@@ -198, +197 @@

   * Hostname is present in the SampleEvent class - can this be saved in the 
log files?
    * easy for CSV: pass SampleEvent instead of SampleResult.
    * harder for XML, as the default output depends on the class, so using 
SampleEvent would change the XML element. This would affect any stylesheets 
etc. However, using SampleEvent as the class would allow the use of a single 
element instead of both sample and httpSample (and any other future 
subclasses). [This was fixed without changing the tags]
+  * Look into warnings when compiling code, some deprecated code should be 
replaced [I think all that remains is OK for now :sebb]
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to