[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jmeter-dev
Subject:    [BSF3] [VOTE] [RESULT] Drop bsf-engines.jar from release
From:       sebb <sebbaz () gmail ! com>
Date:       2010-05-25 16:03:08
Message-ID: AANLkTilln66cgzy3M0NpXj-HNty2I6yfi8-mK5XBQRka () mail ! gmail ! com
[Download RAW message or body]

Thanks very much to all who voted.

The votes were as follows:

+1 (* = Jakarta PMC => binding)
Sanjiva Weerawarana (*)
Rony G. Flatscher (*)
Sebastian Bazley (*)
Sanka Samaranayake

No other votes were received

Therefore the vote passes.

Note: I will create an SVN tag of the current BSF3 code before
removing the bsf engine build etc.

---------- Forwarded message ----------
From: sebb <sebbaz@gmail.com>
Date: 22 May 2010 12:17
Subject: [BSF3] [VOTE] Drop bsf-engines.jar from release
To: dev@jakarta.apache.org


I'd like to call a formal vote on dropping the bsf-engines.jar from
 BSF3 releases.

 The reasons for this are:
 - it's not possible to selectively include just the factories one
 wants. This can cause a clash with other factories that may be
 required.
 - the jar is just a repackaging of factories from a 3rd party. It does
 not add any code.
 - the user must still download the engine separately.
 - some of the factories require additional classes to be present
 otherwise Java 1.6 fails to register *any* factories.
 - many engines now come with their own factories (and that is the way forward)

 [Note that previous releases of bsf-engines.jar will of course
 continue to be available from the archives.]

 Please vote:

 [ ] +1, OK, drop bsf-engines.jar from future releases
 [ ] -1, No, keep the engines (must provide a reason)

 Vote will remain open for at least 72 hours.

 Thanks for your attention.


 S///

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

[prev in list] [next in list] [prev in thread] [next in thread]