Need help in executing openboxes on intelliJ ide

Paritosh_Sengar · October 19, 2023, 1:02pm

I am trying to compile and run openboxes version v0.8.x the version on openboxes develop branch, and using these Java 7 (must install Java 7), MySQL 5.7, Grails 1.3.9, NPM 6.14.6, Node 14+. And i am trying this on windows 10, all seems going fine but i am getting this dependencies errors over and over again-
Errors-

::::::::::::::::::::::::::::::::::::::::::::::

:: org.slf4j#slf4j-api;1.7.33: not found

:: org.codehaus.gpars#gpars;0.12: not found

:: org.jboss.tattletale#tattletale-ant;1.2.0.Beta2: not found

jmiranda · October 19, 2023, 7:02pm

Ok, in case it’s not clear the plugins and dependencies defined in BuildConfig.groovy are resolved using Maven repositories also defined in BuildConfig.groovy.

github.com

openboxes/openboxes/blob/develop/grails-app/conf/BuildConfig.groovy#L45


      
                      "commons-logging",  // use jcl-over-slf4j instead
                      "core-renderer", // use flying-saucer-core instead
                      "itext",  // use flying-saucer-pdf-openpdf instead
                      "log4j",  // use reload4j instead
                      "slf4j-log4j12",  // use slf4j-reload4j instead
                      "xml-apis",  // looks like this conflicts with Grails's internal SAXParserImpl
                      "xmlbeans"  // conflicts with Grails: see https://stackoverflow.com/a/6410955
              )
          }
          log "warn" // log level of Ivy resolver, either 'error', 'warn', 'info', 'debug' or 'verbose'
          repositories {
              inherit false  // some old plugins refer to repos that no longer exist
              mavenRepo "https://repo1.maven.org/maven2/"
              mavenRepo "https://repo.grails.org/grails/plugins-releases/"
          }
          
          dependencies {
              /*
               * Unfortunately, grails 1.3.9 doesn't play nicely with log4j 2's bridge
               * library (https://logging.apache.org/log4j/2.x/manual/migration.html);
               * it instantiates org.apache.log4j.PatternLayout in a non-compliant way.

If we look at each repository, we can reconstruct the expected URL to see whether those dependencies exist. In the case of the first repository, all of the dependencies exist

It looks like they each exist on the second repository as well.

Tattletale JFrog
GPars JFrog
SLF4J JFrog

So the dependencies exist in those two repositories.

So there must be something else going on. Perhaps you’re using a proxy or there’s an issue with HTTPS. Can you send me the entire Tomcat log so we can troubleshoot?

jmiranda · October 19, 2023, 7:12pm

This is going to sound dumb, but try to run grails run-app or grails upgrade a few more times.

jmiranda · October 19, 2023, 7:15pm

And if that doesn’t work, it’s possible that this is an issue with HTTPS. If so, you might be able to work around the issue by adding an insecure Maven repository.

repositories { 
    ...
    mavenRepo "http://insecure.repo1.maven.org/maven2"
}

As of January 2020, the Central Maven repository deprecated insecure traffic over HTTP, so all requests must occur over HTTPS.

Our configuration uses the HTTPS link to the Maven repositories, so we are in compliance with this change, but it’s possible that your development environment has a gremlin preventing you from completing some HTTPS requests.

jmiranda · October 26, 2023, 3:44am

Since I hadn’t heard back from the original poster (OP) I realized that his post was likely generated from an email message. This has happened a few times in the past, so I’m guessing responses posted directly to the forum don’t automatically get sent to the OP. I checked our email inbox for the original email and noticed that his email body included more information than was posted.

::::::::::::::::::::::::::::::::::::::::::::::
  
:: org.slf4j#slf4j-api;1.7.33: not found
  
:: org.codehaus.gpars#gpars;0.12: not found
  
:: org.jboss.tattletale#tattletale-ant;1.2.0.Beta2: not found
-----------------------------------------------------------------------------------------------------------------------------------
Server access Error: Received fatal alert: protocol_version url=https://repo1.maven.org/maven2/org/slf4j/slf4j-reload4j/1.7.33/slf4j-reload4j-1.7.33.pom
  
Server access Error: Received fatal alert: protocol_version url=https://repo1.maven.org/maven2/org/slf4j/slf4j-reload4j/1.7.33/slf4j-reload4j-1.7.33.jar
-----------------------------------------------------------------------------------------------------------------------------------

This error confirms the issue is related to HTTPS

Server access Error: Received fatal alert: protocol_version url=https://repo1.maven.org/maven2/org/slf4j/slf4j-reload4j/1.7.33/slf4j-reload4j-1.7.33.pom

The easiest workaround at the moment is to use the insecure repository as mentioned in my latest response.

repositories { 
    ...
    mavenRepo "http://insecure.repo1.maven.org/maven2"
}

A more secure solution would be to tell Java to use TLSv1.2 whenever it sends requests over HTTPS.

-Dhttps.protocols=TLSv1.2

As a developer, I set an environment variable that I believe Grails picks up when being executed.

JAVA_TOOL_OPTIONS=-Dhttps.protocols=TLSv1.2

In fact, I know it does … because it tells me so whenever I run a Grails command.

[jmiranda@jmiranda-ThinkPad-W540 openboxes (develop)]$ grails run-app
Picked up JAVA_TOOL_OPTIONS: -Dhttps.protocols=TLSv1.2
Welcome to Grails 1.3.9 - http://grails.org/
Licensed under Apache Standard License 2.0
Grails home is set to: /home/jmiranda/.sdkman/candidates/grails/current

Base Directory: /home/jmiranda/git/openboxes