I have to upgrade dependencies for a module and I use pitest version 1.7.4.
When I update the mockito-core version to 4.5.0 all my tests from pitest fail with message "did not pass wihout mutation". With mockito-core 4.0.0 everything works fine.
Also, if I try to update to 4.1.0 still the same. The logging from pitest is not really helping me, I looked up to release notes for mockito-core (https://github.com/mockito/mockito/releases?page=2) but I dont have any ideas.
Did someone encounter this too?
The problem was the following: https://github.com/powermock/powermock/issues/1112
I resolved this by replacing testImplementation("org.powermock:powermock-api-mockito2:2.0.9") with testImplementation("org.powermock:powermock-api-support:2.0.9")
Related
I need to update old dependencies because of security reasons in a project, that uses Yarn and I would like to know the best way to do this. I have used yarn add package-name#latest and yarn upgrade package-name#latest with the same result. The old version package definition remains. Is that acceptable? Since I have to update the old version for security, I think the old version should be removed. Is there a command that updates a package to a specific version and removes the old package definition?
The situation you are describing should only arise if you also have transitive dependencies that come from other dependencies.
So you may have another package that depends on acorn in a lower version.
If this is not the case I would try:
yarn upgrade package-name --latest
To update all packages to the latest versions, I recommend:
yarn upgrade-interactive --latest
I tried something (readme.md, blog etc).But I don't turn 'standalone server distribution'.
I can give an example. What I want to say:
The following is a 'standalone server distribution' files. This is ready for running.
Picture-1
I need to run old version keycloak (version 4.1.0). This package seem like this :
Picture-2
According to Picture-2, this packages don't ready for running.
How can I ready for running ? Like to Picture-1.
I need your suggestions and suggestions. Can you help me?
Greetings,
That's the source code.
You have to build it by executing the following command from parent directory (you need Java JDK and Maven installed and configured):
mvn -Pdistribution -pl distribution/server-dist -am -Dmaven.test.skip clean install
Resulting release distribution will be in ./distribution/server-dist/target/keycloak-4.1.0.Final.zip archive.
Compiling the sources is described here: https://github.com/keycloak/keycloak/blob/master/docs/building.md
You can download the latest release version 4.X from archive: https://www.keycloak.org/archive/downloads-4.8.3.html
I installed mysql-5.6.42 on a Gentoo system. There's a newer version 5.7.24, but I don't want to upgrade for that version. So I masked the package under /etc/portage/package.mask
=dev-db/mysql-5.6.42
When I want to upgrade for example php portage wants to upgrade mysql to 5.7.24.
Why does package.mask not work?
I tried <=dev-db/mysql-5.7.0 the result is the same.
Please check your versions again
=dev-db/mysql-5.6.24 vs. >dev-db/mysql-5.6.42.
echo ">dev-db/mysql-5.6.42" > /etc/portage/package.mask/mysql
I think there is a typo in your question. Perhaps it is also in your config.
See also: https://wiki.gentoo.org/wiki/Knowledge_Base:Masking_a_package
In my composer I've the following version definition of a module:
"my-module": "1.*"
Everything was working fine until I've changed the module tag version to 1.0.10.
The strange thing is that composer is always loading 1.0.9.
I could change the pattern to "1.0.*", but I can't find any info why "1.*" is not working.
btw. I'm using Composer version 1.4.1
To find out why a particular version is not updated, you can run composer why-not package/name version, and Composer will list all dependencies that prevent the installation of that particular version.
I have a feeling that in your case you will detect another package that you did not consider yet.
I'm maintaining an open source project, that defines following dependency (using a version range)
<dependency>
<groupId>org.eclipse.xtend</groupId>
<artifactId>org.eclipse.xtend.lib</artifactId>
<version>[2.6.0, 2.8.0)</version>
</dependency>
Issuing mvn clean install works perfectly, using the latest version of the org.eclipse.xtend.lib allowed by the range. But I would like to also make sure, that my product works with other versions from the range, say with 2.6.0.
My question is: How can I force Maven to use some specified version of a dependency without changing my pom.xml?
I though, it could be something like this:
for version in 2.6.0 2.6.1 2.7.0 2.7.1 ; do
# NOT WORKING!!!
mvn clean install -Denforce_version_org.eclipse.xtend_org.eclipse.xtend.lib=$version
done