[Jakarta-jmeter Wiki] Update of "FutureReleases" by OlegKalnichevski

[Apache Wiki <wi...@apache.org>]

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 OlegKalnichevski:
http://wiki.apache.org/jakarta-jmeter/FutureReleases

------------------------------------------------------------------------------
    * 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. It may be worthwhile to ensure both projects use the same logging framework / compatible logging frameworks.   
   * Move development to the "trunk" of the Subversion repository
   * Upgrade to httpclient4 ? httpclient4 is still only in Alpha. Should / could we have one sampler class using httpclient3 and one httpclient4 ?
   * Remove some code in HTTPSampler, which is there fore workaround for httpclient3.0 bug, which has been fixed in httpclient3.1
@@ -173, +174 @@

    * there are various table implementations, could they be combined?
    * perhaps the table models could also be combined?
   * Add SVN revision number to version? - or at least to Manifests.
- 
+  * Consider migration to Maven2 as a build tool for JMeter. This should help simply dependency management and facilitate the use of JMeter for automatic load testing / integration into tools like [http://maven.apache.org/continuum/ Continuum]   
  
  = Release strategy =
  

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org