Since API-M needs to proceed with only the JS support, it ok to have this
fix. But please note that we won't accept this fix for synapse trunk, hence
once we are done with the current release, please do the needful to get
this sorted out in the API-M on trunk.


On Mon, May 19, 2014 at 9:08 PM, Kasun Indrasiri <[email protected]> wrote:

> In r202968, introduced a direct dependency from synapse to Rhino and
> dropped the bsf dependency. Rather we need to upgrade the bsf versioning
> such that it matches the required Rhino version. If we cannot find the bsf
> with the required Rhino version, then the orbit bundle needs to change such
> that it include the required rhino version.
>
> Modified: carbon/platform/branches/turing/dependencies/synapse/2.
> 1.2-wso2v5/modules/extensions/pom.xml
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/branches/turing/dependencies/synapse/2.1.2-wso2v5/modules/extensions/pom.xml?rev=202968&r1=202967&r2=202968&view=diff
> ============================================================
> ==================
> --- carbon/platform/branches/turing/dependencies/synapse/2.
> 1.2-wso2v5/modules/extensions/pom.xml        (original)
> +++ carbon/platform/branches/turing/dependencies/synapse/2.
> 1.2-wso2v5/modules/extensions/pom.xml        Sat May 17 10:24:27 2014
> @@ -89,7 +89,11 @@
>              <groupId>org.apache.synapse</groupId>
>              <artifactId>synapse-core</artifactId>
>          </dependency>
> -
> +       <dependency>
> +            <groupId>rhino.wso2</groupId>
> +            <artifactId>js</artifactId>
> +            <version>1.7.0.R4.wso2v1</version>
> +        </dependency>
>          <dependency>
>              <groupId>org.apache.synapse</groupId>
>              <artifactId>synapse-core</artifactId>
> @@ -118,11 +122,6 @@
>              <artifactId>xbean</artifactId>
>              <version>${xbean.version}</version>
>          </dependency>
> -        <dependency>
> -            <groupId>org.apache.bsf</groupId>
> -            <artifactId>bsf-all</artifactId>
> -            <version>${bsf.version}</version>
> -        </dependency>
>         <dependency>
>             <groupId>org.jruby</groupId>
>             <artifactId>jruby-complete</artifactId>
> @@ -175,10 +174,6 @@
>                      <artifactId>cglib-nodep</artifactId>
>                  </exclusion>
>                  <exclusion>
> -                    <groupId>bsf</groupId>
> -                    <artifactId>bsf</artifactId>
> -                </exclusion>
> -                <exclusion>
>                      <groupId>mx4j</groupId>
>                      <artifactId>mx4j</artifactId>
>                  </exclusion>
>
>
>  On Mon, May 19, 2014 at 6:42 PM, Isuru Udana <[email protected]> wrote:
>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 3:04.742s
>> [INFO] Finished at: Mon May 19 18:36:59 IST 2014
>> [INFO] Final Memory: 133M/543M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.2:test (default-test) on
>> project synapse-extensions: There are test failures. -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn <goals> -rf :synapse-extensions
>>
>>
>> -------------------------------------------------------
>>  T E S T S
>> -------------------------------------------------------
>> Running org.apache.synapse.mediators.bsf.GroovyScriptMediatorTest
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.039 sec
>> <<< FAILURE!
>> Running org.apache.synapse.mediators.bsf.ScriptMediatorTest
>> Tests run: 100, Failures: 100, Errors: 0, Skipped: 0, Time elapsed: 2.16
>> sec <<< FAILURE!
>> Running org.apache.synapse.mediators.xquery.XQueryMediatorTest
>>
>>
>> It seems like r202968 causing this.
>> What's the reason for this change ?
>>
>>
>> --
>> *Isuru Udana*
>>  Senior
>> * Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: [email protected] cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>> twitter: http://twitter.com/isudana
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to