Knute Snortum wrote:It means the integrity of the downloaded file is in question.
Stephan van Hulst wrote:As it says, run the Maven command you were using, but include the -e switch and copy and paste the entire exception stack trace.
Stephan van Hulst wrote:Well, what error did you get?
Stephan van Hulst wrote:I'm not convinced about the mirror. First try adding only the plugin repository.
Did you clean up your other settings? Did you remove the plugin groups and removed proxies and repositories that you don't need?
Stephan van Hulst wrote:Good to hear. Does it also work when you re-add the jtest-maven-plugin?
Why do you want this?
Knute Snortum wrote:M Ridhwan Kamil: It is not necessary to quote the entire text of a previous message. Only quote as much as is needed to provide context, or none at all.
Stephan van Hulst wrote:Yeah, the problem is that you're using a new version of Maven but an old version of Java.
Are you required to use Java 7? If not, you want to upgrade to at least Java 8, but I recommend Java 11.
Alternatively, whenever you run a Maven command you first have to specify the TLS version to use. Java 7 defaults to TLS 1.1 but Maven 3.6 requires TLS 1.2:
Stephan van Hulst wrote:Can you share the output of
Stephan van Hulst wrote:Again, your settings.xml file is not valid. Please run it through an XML syntax checker.
Why have you declared plugin groups in your settings.xml? It's much better to specify groupIds explicitly in your project POM.
Did you censor the user names/passwords/keys from the settings.xml? If not, and those are your real settings, then why are you using example settings, such as the <server> elements?
Why have you declared the maven central repository in your settings.xml? Put it in your project POM, but ONLY if you declared other repositories as well, and you want the central repository to take precedence.
You still need to add the HandChina RDC repo to the repositories in your project POM, as I've shown you earlier. It seems that right now, you're pulling a local copy of the ojdbc7 artifact, making your build unreproducible to anybody on a different machine. The groupId is still wrong. It should be com.oracle, not oracle. Where did you get this dependency?
Again, why are you using two different Spring versions?
I cleaned up your POM. See if this works:
If it doesn't, it's definitely a problem with your build environment. That means your Maven settings are still not right, or maybe something is wrong with your Maven or Java installations.
Stephan van Hulst wrote:Please post your settings.xml too.
Stephan van Hulst wrote:Your <proxy> element is not enclosed in a <proxies> element.
The file paths you use for your plugin repository and your mirror are not valid URLs. You must specify them as URLs using the file protocol.
For the OJDBC driver, you need to add an extra repository to your project POM. Here's what it could look like:
Stephan van Hulst wrote:It looks like your Maven settings are bad.
Please post the .m2/settings.xml from your user folder, but make sure you censor sensitive data (such as names and passwords) first.
Stephan van Hulst wrote:Does the problem persist when you remove the jtest-maven-plugin? If the problem goes away, you have to take it up with Parasoft. I can't reproduce the issue because I don't have a licence to use their software. You have other issues though. Why are you using two different versions of Spring? You also seem to be using the wrong groupId for the OJDBC dependency. And why haven't you configured the repositories in your POM?