I upgraded mule runtime from 4.2.2 to 4.3.0
I installed mule 4.3.0 in anypoint studio 7.4.2 and changed mule-artifact.json to 4.3.0 and in pom file i changed some connector to latest version and mule maven plugin to 3.5.1
Code is getting deployed successfully but munit is failing
Could you please suggest a solution
MUnits will not work the same way in runtime 4.3.0 unless you upgrade Munit dependent artifacts in your project's pom.xml file
The following artifacts need to be updated to latest versions
<artifactId>munit-tools</artifactId> to say 2.3.1
<artifactId>munit-runner</artifactId> to say 2.3.1
<munit.version> to minimum 2.2.1
Also make sure you are using the correct version of the APIKit Router.
Few other observations we noticed when migrating to 4.3 was in some places String "true" was equal to boolean true in runtime 4.2.0 but not same in 4.3.
Please share your final resolution.
Regards
Mahesh Raja Vandyala
Related
Although the build was started using java version: 1.8.0_242, vendor: AdoptOpenJDK, I'm getting the warning -tag option is not supported on Java version < 1.4. When building with javadoc:jar, the build fails because of the custom tags.
This is a quite old build using maven-javadoc-plugin:2.10.4. I cannot just ramp it up to 3+, and 2.10.4 seems to be newest version of 2.10.
Any ideas?
I'm using STS 4.6 and getting below error while using Gradle 6.8.3. I was able to build project using Gradle 4.10 but for JDK 11 I had to upgrade Gradle version. Please assist how to resolve this
Support for clients using a tooling API version older than 3.0 was removed in Gradle 5.0. You are currently using tooling API version 2.2.1. You should upgrade your tooling API client to version 3.0 or later.
I solved this by uninstalling 'Gradle IDE' plugin provided by Pivotal and installing 'Eclipse Buildship plugin for Gradle' - Refer this
Background
I'm trying to build a project which has a dependency on a library xcore 1.10.0 that has a dependency on antlr with restriction [3.2.0, 3.2.1). What exists is a version 3.2.
Problem
The build fails reporting Could not find any version that matches org.antlr:antlr-runtime:[3.2.0, 3.2.1).. When I explicitly ask for version 3.2, it resolves. When I check ava -cp "$MAVEN_HOME/lib/*" org.apache.maven.artifact.versioning.ComparableVersion 3.2 3.2.0 3.2.1, I get the following (which I interpret as 3.2 being within the requested racket):
1. 3.2 == 3.2
3.2 == 3.2.0
2. 3.2.0 == 3.2
3.2.0 < 3.2.1
3. 3.2.1 == 3.2.1
Reporduction
To try this at home, one should be able to check out this example project and try running ./gradlew clean build.
Questions
Is the version bracket wrongly specified (given the versions that actually exist and assuming version 3.2 is required)? Or is Gradle doing something weird with the interpretation of the version bracket?
Is there a way to work around this (other than uploading a "fake" replica with version 3.2.0 to a local repository)?
Currently, we are using Maven 2.2.2 version but we suppose to use 3.x version when i am trying with a different version of Maven its showing error like build is failing
I am trying to use maven in our project and am new to it.
checking this https://maven.apache.org/download.cgi
3.6.0 version is latest version to download.
Someone was saying there is maven 4 is latest. Not sure where to download this from and can we use this for java 8.
Which one is latest version to use?
From https://maven.apache.org/download.cgi
Apache Maven 3.6.0 is the latest release and recommended version for
all users.
Works nicely with Java 8. Note that your IDE may bundle an older version in the unlikely case you run into problems.