Grails clean command giving error in Ubuntu docker container - docker

I am trying to run the Grails -clean command on Ubuntu machine running in Docker container but I am getting the below error:
$ grails clean
| Loading Grails 2.4.0
| Configuring classpath
| Error Resolve error obtaining dependencies: Failed to read artifact descriptor for xalan:serializer:jar:2.7.1 (Use --stacktrace to see the full trace)
| Error Required Grails build dependencies were not found. This is normally due to internet connectivity issues (such as a misconfigured proxy) or missing repositories in grails-app/conf/BuildConfig.groovy. Please verify your configuration to continue.
Because of this issue, I am not able to proceed further with the war file deployment using grails. I have checked the "BuildConfig.groovy" and added some repositories as well as mentioned in various portals, but no luck. Getting the same error again and again.
Any help will be highly appreciated.
Thanks,
Akshat

Try using https instead of just http.
mavenRepo "https://repo.grails.org/grails/core"
mavenRepo "https://repo.grails.org/grails/plugins"
Also try running with Java 8 over Java 7 due to Java 8 default to TLS 1.2.

Related

Why Jenkins startup fails on restart of Tomcat?

I was able to setup Jenkins 2.361.1 in Tomcat 9.0.67. It is running perfectly fine in http://localhost:8080/jenkins but if I try to restart tomcat by using shutdown.bat and then startup.bat, I get the following errors:
...
SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more Filters failed to start. Full details will be found in the appropriate container log file
SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/jenkins] startup failed due to previous errors
INFO [main] hudson.lifecycle.Lifecycle.onStatusUpdate Stopping Jenkins
INFO [main] jenkins.model.Jenkins$16.onAttained Started termination
SEVERE [main] jenkins.model.Jenkins$16.onTaskFailed Failed NioChannelSelector.cleanUp
java.lang.IllegalArgumentException: Unable to inject class jenkins.slaves.NioChannelSelector
at hudson.init.TaskMethodFinder.lookUp(TaskMethodFinder.java:130)
...
http://localhost:8080 will still work fine but http://localhost:8080/jenkins displays a 404 page
Why am I getting that error even if I didn't change a thing after Tomcat shutdown? I used the zip file download to install Tomcat not the service installer.
The only workaround that works so far for me is to delete the jenkins folder inside the webapps folder and let tomcat redeploy it again. After doing that, no error occurred and jenkins worked just like before.

Using the Jenkins Plugin installation manager tool for offline plugin download and installation

I downloaded the jar file from https://github.com/jenkinsci/plugin-installation-manager-tool as specified in the docs. We are behind a corporate proxy, so tried both with and without the proxy the following command ..
java -jar jenkins-plugin-manager-*.jar --war C:\PathToJenkins\Jenkins\jenkins.war --available-updates --plugin-file C:\PathToJenkins\Jenkins\plugins.txt
kept running into "Error getting update center json"
Has anyone faced similar issue ? Am I doing anything wrong ?

AspnetPublishHandler with name "Custom" was not found when publishing ASP.NET 5 project to Docker

I am trying to publish a non-modified ASP.NET 5 project to my freshly installed Ubuntu 15.04 server, but I receive the following message:
An error occurred during publish. AspnetPublishHandler with name
"Custom" was not found
I bound the server to the correct port with:
docker daemon -H 0.0.0.0:5555 &
The connection validation is successful. Anyone has an idea what could be wrong?
Have you tried after the latest release? For some configuration combination the publish profile was getting generated incorrectly.

IBM Worklight application builder error

I am using eclipse juno 4.2.1 and IBM worklight 6.0 on my mac mini. since yesterday I am trying to build and deploy my application but its giving me "Worklight application builder" error.
here is the log:
An internal error occurred during: "Worklight application builder".
loader constraint violation: when resolving method "org.apache.commons.io.FileUtils.iterateFiles(Ljava/io/File;Lorg/apache/commons/io/filefilter/IOFileFilter;Lorg/apache/commons/io/filefilter/IOFileFilter;)Ljava/util/Iterator;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, com/worklight/builder/skins/impl/SkinBuilderImpl, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/apache/commons/io/FileUtils, have different Class objects for the type o/filefilter/IOFileFilter;Lorg/apache/commons/io/filefilter/IOFileFilter;)Ljava/util/Iterator; used in the signature
and console shows this message :
[2013-09-25 15:18:46] Starting build process: application 'TestApp', all environments
[2013-09-25 15:18:46] com.worklight.shared.common.messages:tgn309.trigyn.com: tgn309.trigyn.com: nodename nor servname provided, or not known
java.net.InetAddress.getLocalHost(InetAddress.java:1466)
com.worklight.common.util.GeneralUtil.scanIPAddresses(GeneralUtil.java:581)
com.worklight.common.util.GeneralUtil.scanIPAddresses(GeneralUtil.java:549)
com.worklight.common.util.GeneralUtil.getIPscanResults(GeneralUtil.java:642)
com.worklight.studio.plugin.utils.WSTServers.getServerHost(WSTServers.java:174)
com.worklight.studio.plugin.utils.WSTServers.getServerURL(WSTServers.java:661)
com.worklight.studio.plugin.launch.build.apps.WorkspaceApplicationBuilder.buildApplication(WorkspaceApplicationBuilder.java:325)
com.worklight.studio.plugin.launch.build.apps.WorkspaceApplicationBuilder.runInWorkspace(WorkspaceApplicationBuilder.java:158)
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
[2013-09-25 15:18:46] FWLPL0010W: "localhost" was detected from the target server configuration. Using the primary IP address of the host machine, 10.30.1.102, to build the Worklight application(s). Consider using a fully qualified hostname (avoid using "localhost") or a valid IP address instead. The value can be modified by opening the configuration editor of Worklight Development Server from the "Servers" view.
Any help would be appreciated.
Try the suggestion given in the following answer, as it seems somewhat related based on the error in your question: IBM Worklight 6.0 - Migration Issue after importing a project
Copy/paste:
Please try to find if you have apache commons IO installed in your
Eclipse plugin directory. That's the source of the conflict.
If you can, please try to:
stop the Eclipse
move the apache commons IO out of the plugin dir
start Eclipse, then close it
move the commons IO back into the plugin dir
Start Eclipse

Adding .jar to Grails Dependencies of a Project

I have this project having MSSQL 2008 R2 as its database server. The connection between the Services view of IReport and the database is established and running. The problem here is that the project cannot connect to the database server when running it.
These is the error showned on grails console prior to start-up completion:
ERROR hbm2ddl.SchemaUpdate - could not complete schema update
I've seen similar case but the way to resolve it is having the driver sqljdbc4.jar put inside the [Project Name]\classpath\Grails Dependencies (project explorer heirarchy) where the driver is located in the [Project Name]\lib. But the do how has gone missing.
I've also tried to manually install the dependency following the commmand below but grails return that the driver is not found.
grials> install-dependency sqljdbc4
The question is how can I include the driver into the Grails Dependencies?
Assuming you are running Grails 2+, this article should help you. I also had to restart Eclipse before everything actually showed up correctly.

Resources