Any review comments or updates wanted to this candidate distro? If not then tomorrow I'll make an RC2 to include the recent axiom e4x changes and call a vote on releasing that RC2.
...ant On 10/27/07, ant elder <[EMAIL PROTECTED]> wrote: > > Ok I've taken the liberty of starting this off and created an RC1 for a > beta2 release. > > There's an SVN branch for the release at: > https://svn.apache.org/repos/asf/jakarta/bsf/branches/bsf-3.0-beta2/ > > A tag for the beta2-rc1 is at: > https://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.0-beta2-rc1/ > > I've built the release and uploaded the binary and source distribution > artifacts, maven repository, and RAT reports to: > http://people.apache.org/~antelder/bsf/beta2-rc1/ > <http://people.apache.org/%7Eantelder/bsf/beta2-rc1/> > > Release notes are: > https://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.0-beta2-rc1/distribution/src/bin/RELEASE_NOTES > > > There hasn't been much notice on this release so this RC is just for > review, we can wait a while to see if there are other things people want to > include in a beta2 release and then re-spin more RC's as required. In the > meantime, please review and provide feedback on these release artifacts. > > Thanks! > > ...ant > > On 10/26/07, ant elder <[EMAIL PROTECTED]> wrote: > > > > The Apache Synapse guys have hit a problem with using the BSF3 beta1 > > release with the latest Groovy release (see [1]) so a new BSF release that > > fixes that sounds good to me. Synapse are looking to do a 1.1 release > > within a couple of weeks so could we get a new BSF beta2 release out in > > time for them to use in that? > > > > ...ant > > > > [1] http://marc.info/?t=119339377300004&r=1&w=2 > > > > On 10/15/07, Rony G. Flatscher <[EMAIL PROTECTED]> wrote: > > > > > > Hi Sanka, > > > > > > *great* patch! > > > > > > Did look over it and saw that you have tackled also all other > > > signature > > > deviations such that now BSF3 should be fully JSR-223/1.6 compliant! > > > > > > After you check in the changes, we should start to contemplate to > > > create > > > a beta 2 version of BSF3, what do you (and others on this list) think? > > > > > > > > > Regards, > > > > > > ---rony > > > > > > > > > > > > > > > Sanka Samaranayake (JIRA) wrote: > > > > [ > > > > https://issues.apache.org/jira/browse/BSF-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > > ] > > > > > > > > Sanka Samaranayake updated BSF-3: > > > > --------------------------------- > > > > > > > > Attachment: BSF-3_patch.txt > > > > > > > > This patch contains a fix for the described issue. Will apply the > > > patch shortly. > > > > > > > > > > > >> ScriptEngineManager.getFactories() NOT compliant with JSR223 API > > > >> ---------------------------------------------------------------- > > > >> > > > >> Key: BSF-3 > > > >> URL: https://issues.apache.org/jira/browse/BSF-3 > > > >> Project: BSF > > > >> Issue Type: Bug > > > >> Affects Versions: BSF-3.0 > > > >> Environment: Windows XP, Java 6 > > > >> Reporter: Ivan Martinez-Ortiz > > > >> Priority: Blocker > > > >> Attachments: BSF-3_patch.txt > > > >> > > > >> > > > >> Method ScriptEngineManager.getFactories() (trunk code and tags/bsf- > > > 3.0-beta1/ code) returns an array of ScriptEngineFactory. However JSR > > > 223 Scripting for the Java™ Platform Final Draft Specification version > > > 1.0 (section SCR.4.3.8.1 Discovery Mechanism, page 168) says that > > > should return List<ScriptEngineFactory>. > > > >> Particularly this issue makes impossible develop client code using > > > bsf3.0-beta1 maintaining the compatibility with Java 6 Scripting API > > > reference implementation > > > >> > > > > > > > > > > > > > > > > >
