This error occurs on my public build project: https://travis-ci.org/byjg/authuser/jobs/211336643
I ran locally using php 7.0 and php 7.1 on my Ubuntu and this problem does not occur.
Travis runs successful on PHP 5.6
Could you help me?
There is a difference between namespace structure between PHPUnit <6 and PHPUnit 6.
You may consider the following solution for backward compatibility:
// backward compatibility
if (!class_exists('\PHPUnit\Framework\TestCase') &&
class_exists('\PHPUnit_Framework_TestCase')) {
class_alias('\PHPUnit_Framework_TestCase', '\PHPUnit\Framework\TestCase');
}
The old PHPUnit versions use \PHPUnit_Framework_TestCase but the new one uses \PHPUnit\Framework\TestCase. With the backward compatibility applied you can use the class name that is compatible with the new version of PHPUnit (i.e. \PHPUnit\Framework\TestCase) and it is going to work also with older versions.
Update
In order to cover support for PHP 5.3 you have to remove a \ character before the alias class, i.e.
class_alias('\PHPUnit_Framework_TestCase', 'PHPUnit\Framework\TestCase');
Related
I have try to install geolocation plugin in october cms
but i am getting errorenter image description here
You posted that your version is PHP 7.0.2 but it supports the array as constant
I guess, PHP version below 5.6 is not supporting this.
may be you are having issue related to version.
reference : https://3v4l.org/T44gG
may be, you did check command line version (CLI version) of php using
php --version
so at there it may be showing you 7.0 but in your apache config you may still using old version.
to confirm that you are also using PHP 7.0 in Apache you can create small php file with below code.
<?php
phpinfo();
then check what version is there.
if its also showing 7.0 then i don't know its something else.
but if its shows 5.x some things then you need to update your apache config
I assume you are on linux machine so, all commands are related to linux op. system
install apache php 7.0 mod (mod = module)
sudo apt-get install libapache2-mod-php7.0
now enable php 7 module before that disable old php5 mod, (sudo a2dismod php5)
sudo a2enmod php7.0
let me know if its works or not.
I'm trying to run a Grails Application from the Grails In Action website. I've imported the 'hubbub' project into the GGTS app and have encountered build errors. The project was originally built with Grails 2.3.7 whereas I have version 2.4.4 on my system. Based on another Stack Overflow question I've changed the 'app.grails.version' in the application.properties file to grails version 2.4.4 which prompted a flurry of downloads in the command prompt terminating in a series of errors regarding problems with plugins. I can't run the app because I'm told that "Project 'hubbub' is missing required source folder: grails-app/utils". If I try to change 'app.grails.version' back to 2.3.7 I'm told that I need to configure a Grails installation of 2.3.7.
Am I doing something wrong here in trying to upgrade this Grails project? Or do I really have to install Grails 2.3.7 in order to get this to work?
(Sorry, I haven't posted the errors regarding plugin downloads but I can't seem to recreate them).
Thanks in advance!
Grails 2.4 is a big change over 2.3, mostly due to the use of the asset pipeline instead of resources.
Also simply changing the version in application.properties isn't enough, you also need to actually run the matching Grails framework.
See here for upgrading an app from 2.3 to 2.4: http://grails.github.io/grails-doc/2.4.x/guide/upgradingFrom23.html . From experience upgrading Grails apps from older versions must be done manually. One reason is that the upgrade command is obsolete and has been removed. Read the docs for breaking changes and address each change individually in the code. Upgrading patch levels are no problem (usually), but upgrading minor and major versions often are a lot of work.
Since you are learning, I would stick to 2.3.7 for your exercise (meaning that you must run 2.3.7, which you aren't doing). What you'll learn will remain valid. Do use 2.4.4 when building your own project from scratch.
If your project only missing grails-app/utils, try just to create it.
Take a look in your Project Properties -> Build Path. There are all the source folder defined. It can be helpful
I have different projects using jHipster (which is an absolutely awesome project!!!).
My problem is that I have already made important changes on some projects created with earlier version and I don't want to upgrade to the latest version.
Is there any way to set the version while using the generator ?
What I'm looking for is something like that :
yo jhispter:entity foo -v 1.2.0
when I want to use the version 1.2.0 to generate the entity.
Does something like that exist ? If no, how to manage different versions of the generator ?
After more research on the subject it looks like you need to install an older version to switch version.
npm install -g generator-jhipster#1.2.0
I need to upgrade my application which is using Cordova 1.8 version to Cordova 2.0 version. I followed the steps mentioned in the http://cordova.apache.org/docs/en/2.8.0/guide_upgrading_ios_index.md.html. My application's running for 1.9 but when am trying to upgrade it to 2.0 version am not able to find 'Preprocessor Macro' in build setting.
Also I am not able to find 'CordovaLib' folder, but in the 10th step they have mentioned related to PreprocessorMacro which am not able to find.
As you main motivation seems to be up to date with the last version of Cordova, I would recommend to create a new clean project with Cordova 2.8 and import your html files in the www folder.
Upgrading version by version is painful and you will not get any benefits from it. However, you might not get any performance improvement but you will get a better support from the community.
I’m trying to upgrade Grails to version 2.2.0. I used gvm and installed Grails 2.2.0. After this I changed my project in GGTS to use Grails version 2.2.0 and Groovy version 2.0.0. But when I finally tried to run the project, I got the following error:
Error occurred during initialization of VMError opening zip file or JAR manifest
missing : null
agent library failed to init: instrument
What is the problem?
We had the same problem.
This is due to eclipse saving old run configuration for the previous grails version.
Just remove old launch configuration and retry.
To remove old launch configuration :
go to Run\RunConfiguration\Grails
select all nodes and remove them.
I had the same problem when I started using Grails 2.2.0 - The solution Ian mentioned works, here is the link to the issue and resolution that occurred in my project
Grails 2.2.0 error
Added on 1/15/2013 Other suggestions based on 2.2.0/ivy cache issues
I am running on windows, a couple of things to try.
Based on your error message seems like the issue might be related to the Ivy cached, I would suggest cleaning that out using the clean command.
I would also go ahead and delete the Icy cache folders on your machine at \ivy-cache(after backing it up just in case)
Read grails documentation at http://grails.org/doc/2.0.0/guide/gettingStarted.html, refer to section 2.3 regarding Ivy cache – there might be issues running 2.x and 1.x grails projects side by side.
When install, I do not have to install groovy explicitly - I just install grails and that take care of the groovy code implicitly. Is that possible for you to do? To rule out dependency issues?
On my version of grails I have the groovy version showing up as 2.0.5 – I assume you meant grails 2.2.0 – can you ensure that you have a groovy version installed with is compatible with grails 2.2.0?
If possible try your code on a fresh device where grails has not been installed before. This is to rule out interference due to other existing issues
It's a known issue to do with the fact that the version of the springloaded reloading agent used by 2.2 (and 2.1.3) has a different name from that used by previous versions of Grails. There's a workaround in the bug report, or you can upgrade to a nightly build of GGTS which knows about the new name (as described in this bug report).
I am using GGTS 3.2 with Groovy compiler 2.1.1 on Windows XP.
Had imported a project from GGTS 3.1, upgraded compiler to 2.1.1 and got in mess, so
deleted the project and removed it from .grails cache, then re-created project from scratch. When it came to running the project I got the ivy error.
Removing the old launch configuration via Run->RunConfiguration...Grails fixed problem without switching to a night build of GGTS.
(BTW Deleting ivy-cache didn't help at all)