Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <25961596.40411274358717092.JavaMail.jira@thor>
Date: Thu, 20 May 2010 08:31:57 -0400 (EDT)
From: "Joerg Schaible (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Issue Comment Edited: (JEXL-102) Add "jexl2" as a supported
 name
In-Reply-To: <21572574.39771274353733812.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JEXL-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869569#action_12869569 ] 

Joerg Schaible edited comment on JEXL-102 at 5/20/10 8:31 AM:
--------------------------------------------------------------

Well, it does not really solve the problem with BSF compatibility. ScripeEngine seach by extension will still fail and from user's point of view you should not not have to take a different name, because you already have chosen Jexl2 with the dependencies.


      was (Author: joehni):
    Wel, it does not really solve the problem with BSF compatibility. ScripeEngine seach by extension will still fail and from user's point of view you should not not have to take a different name, because you already have chosen Jexl2 with the dependencies.

  
> Add "jexl2" as a supported name
> -------------------------------
>
>                 Key: JEXL-102
>                 URL: https://issues.apache.org/jira/browse/JEXL-102
>             Project: Commons JEXL
>          Issue Type: New Feature
>    Affects Versions: 2.0.1
>            Reporter: Sebb
>
> Might be useful to add "jexl2" (and possibly other variants) as a supported script engine name to make it easier to select JEXL 2 when both JEXL1 and JEXL2 are available.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.