Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I'm creating simple plugin using example provided here - simple servlet. As far as I know JIRA Plugins are OSGi Framework based.
During deployment of my plugin (atlas-run command) I recive error message which I'm unable to understand. This is output which I have found on my console:
[INFO] [talledLocalContainer] ********************************************************************************************************************************************************************************************************
[INFO] [talledLocalContainer] ___ FAILED PLUGIN REPORT _____________________
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 1 plugin failed to load during JIRA startup.
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 'com.my.soft.my-work-log-plugin' - 'My Work Log Plugin' failed to load.
[INFO] [talledLocalContainer] Cannot start plugin: com.my.soft.my-work-log-plugin
[INFO] [talledLocalContainer] Unresolved constraint in bundle com.my.soft.my-work-log-plugin [164]: Unable to resolve 164.0: missing requirement [164.0] osgi.wiring.package; (osgi.wiring.package=bsh)
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] It was loaded from C:\Users\pduleba\work\repo\my-jira\my-software-maven-plugins\my-software-jira-plugins\my-work-log-plugin\target\jira\home\plugins\installed-plugins\my-work-log-plugin-1.0.0-SNAPSHOT.jar
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] ********************************************************************************************************************************************************************************************************
Whats the meaning of this:
Unresolved constraint in bundle com.my.soft.my-work-log-plugin [164]: Unable to resolve 164.0: missing requirement [164.0] osgi.wiring.package; (osgi.wiring.package=bsh)
Is there any way to change log level i.e. DEBUG? How to do it?
Where can I found more meaningful logs?
Thank You for any piece of advice!
This is an error from OSGi that says, essentially:
The bundle com.my.soft.my-work-log-plugin imports a package named bsh (which is BeanShell I think?).
There is no package named bsh being exported by any installed bundle.
It seems like you have to install the BeanShell bundle, as this is a dependency of your bundle.
Related
I'm trying to build native images for spring-boot apps in a maven multi-module project.
As soon as I decorate a #Controller method with #PreAuthorize, native image generation fail with the message below.
Following spring-native samples, I tryed both with (as done in security-method-class-proxies) and without (as done in security-method) #AotProxyHint on application class, but this made no difference.
The error:
[INFO] [creator] Error: Error parsing dynamic proxy configuration in file:/workspace/META-INF/native-image/org.springframework.aot/spring-aot/proxy-config.json:
[INFO] [creator] java.lang.IllegalArgumentException: repeated interface: org.springframework.aop.SpringProxy
[INFO] [creator] Verify that the configuration matches the schema described in the -H:PrintFlags=+ output for option DynamicProxyConfigurationResources.
[INFO] [creator] Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception
[INFO] [creator] Error: Image build request failed with exit status 1
[INFO] [creator] unable to invoke layer creator
[INFO] [creator] unable to contribute native-image layer
[INFO] [creator] error running build
[INFO] [creator] exit status 1
[INFO] [creator] ERROR: failed to build: exit status 1
Any clue why?
I figured out two things about this error:
as soon as #PreAuthorize targets a class member (not an interface), configuration must provide an #AotProxyHint(targetClass = ..., proxyFeatures = ProxyBits.IS_STATIC) for this class
there is bug on Windows about that declared in spring-native issues
i am trying to get started with Hippo CMS. According to the docs Get started with Hippo everything worked so far. But at the last step where you have to run
mvn -Pcargo.run (-Drepo.path=storage)
the installation process seems to be frozen and after at least 5 min finishes with this error message. No idea what to do, according to the docs Hippo Prerequisites everything is correct set up so far (Java and Maven Version).
The error message is as follows:
[INFO] --- cargo-maven2-plugin:1.6.5:start (cargo-run) # myhippoproject
--- [INFO] [2.ContainerStartMojo] Resolved container artifact
org.codehaus.cargo:cargo-core-container-tomcat:jar:1.6.5 for container
tomcat8x [INFO] [talledLocalContainer] Tomcat 8.x starting... [INFO]
[stalledLocalDeployer] Deploying
[/Users/Mangrove/Desktop/myhippoproject/cms/target/cms.war] to
[/Users/Mangrove/Desktop/myhippoproject/target/tomcat8x/webapps]...
[INFO] [stalledLocalDeployer] Deploying
[/Users/Mangrove/Desktop/myhippoproject/site/target/site.war] to
[/Users/Mangrove/Desktop/myhippoproject/target/tomcat8x/webapps]...
[WARNING] [stalledLocalDeployer] The WAR contains a context.xml file
which sets the path to [essentials], which means path set it the Cargo
configuration will be ignored by Tomcat [INFO] [stalledLocalDeployer]
Deploying
[/Users/Mangrove/Desktop/myhippoproject/essentials
/target/essentials.war]
to [/Users/Mangrove/Desktop/myhippoproject/target/tomcat8x/webapps]...
[INFO] [yer.DeployerWatchdog] Deployable
[http://localhost:8080/cargocpc/index.html] failed to finish deploying
within the timeout period [600000]. The Deployable state is thus
unknown. [WARNING] [talledLocalContainer]
org.codehaus.cargo.container.ContainerException: Deployable
[http://localhost:8080/cargocpc/index.html] failed to finish deploying
within the timeout period [600000]. The Deployable state is thus
unknown. [ERROR] Starting container
[org.codehaus.cargo.container.tomcat.
Tomcat8xInstalledLocalContainer#40f8f
5a8] failed, now stopping container [INFO] [talledLocalContainer]
Tomcat 8.x is stopping... [INFO] [talledLocalContainer] Tomcat 8.x is
stopped [INFO] -------------------------------------------------------
----------------- [INFO] BUILD FAILURE [INFO] ------------------------
------------------------------------------------ [INFO] Total time:
10:28 min [INFO] Finished at: 2018-05-13T15:57:13+02:00 [INFO] -------
-----------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-
plugin:1.6.5:start (cargo-run) on project myhippoproject: Cannot start
container
[org.codehaus.cargo.container.tomcat.
Tomcat8xInstalledLocalContainer#40f8f
5a8]: Deployable [http://localhost:8080/cargocpc/index.html] failed to
finish deploying within the timeout period [600000]. The Deployable
state is thus unknown. -> [Help 1] [ERROR] [ERROR] To see the full
stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-
run Maven using the -X switch to enable full debug logging. [ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles: [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Any hint, advice, tipp, suggestion is very welcome, thanks.
Finally i solved it. The Maven setup was not correctly wired. In any case i had to reset my pc, and suddenly it works now. Also i had different java versions at the time. Great help was also the hippo forum Hippo Community Forum. Thanks guys.
The error just means that the container did not start. The connection refused in this case is just a symptom of how cargo checks if the container is up.
That being said, this is quite a long time to have to wait to start. You could try to increase the timeout, but even this timeout is too long for regular work purposes.
Things to try include increasing the timeout, increasing jvm memory, start over, or try a different computer. Also make sure the process is running with the right permissions.
I've read the following previous answers to similar topics, but none have worked for me.
Here is what I've tried:
Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved
Maven Build Failure - failure to find plugins
The first link doesn't really apply because I'm not using a proxy, but I did check the settings.xml file for other possibilities. I can download directly by going to the plugin .jar file.
The second link might apply, but I have no idea what they mean by: "change user settings to point out to correct settings.xml and to your repository folder should exist in your system." I don't know how to do this and am not sure which repository they are referring to and how I find out. I'm looking only at my Maven settings.xml file.
So here's my errors
C:\cas-overlay-template-master>mvn package install
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building cas-overlay 1.0
[INFO] ------------------------------------------------------------------------
Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/3.3/maven-compiler-plugin-3.3.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.965 s
[INFO] Finished at: 2017-03-21T23:42:13-04:00
[INFO] Final Memory: 7M/97M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.3 or one of its dependencies could not be resolved: Could not transfer artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.3 from/to central (https://repo.maven.apache.org/maven2): java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
My goal is to get CAS 5.0.4 working for a Liferay 7.0ga3, running Tomcat 8, JDK 1.8, and Maven 3. I am a student, have never used any of these technologies except JDK 1.8, so I really need very understandable answers. Not veteran answers for those that should know what they are doing. Thanks
The actual problem here is around the certificates the Maven JVM is trusting:
Unexpected error: java.security.InvalidAlgorithmParameterException:
the trustAnchors parameter must be non-empty
Various things can fix it, but this question has a lot of solutions (and one more here).
I am facing a similar issue as in https://issues.apache.org/jira/browse/MNG-4001
but with maven-sonar-plugin. Versions i am using are:
Jenkins - 1.580.1, SonarQube-plugin in Jenkins -2.1, tried with Sonar 4.0 and SonarQube 4.5.1 but faced same error, sonar-maven-plugin: 2.6 /2.7.1 (tried both) I face this error when i use Sonar post build step in my Jenkins configuration and this is frequent issue seen in different jobs
Error is
[INFO] Searching repository for plugin with prefix: 'sonar'.
[INFO] artifact org.apache.maven.plugins:maven-sonar-plugin: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-sonar-plugin: checking for updates from snapshots
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-sonar-plugin' does not exist or no valid version could be found
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-sonar-plugin' does not exist or no valid version could be found
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:462)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:175)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-sonar-plugin' does not exist or no valid version could be found
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:229)
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:91)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:179)
at org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540)
... 15 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Dec 16 13:13:35 CET 2015
[INFO] Final Memory: 7M/238M
[INFO] ------------------------------------------------------------------------
Sonar analysis completed: FAILURE
Build step 'Sonar' changed build result to FAILURE
Build step 'Sonar' marked build as failure
Finished: FAILURE
why am i facing this error ? is the issue(bug) with Sonarqube plugin in Jenkins?
for time being to avoid this error i have deleted Sonar post build step and added the sonar analysis step in maven goals for maven 3.0.4
Maven goals :: clean install -Dmaven.test.skip=true -Dsonar.jdbc.url=jdbc:postgresql://sonardb.test.com:5555/sonar -Dsonar.host.url=http://localhost:9000/sonar org.codehaus.mojo:sonar-maven-plugin:2.6:sonar <br>
but this is a temporary solution, I would like to use Sonar post build step in my job configuration and not face this error.
Thanks for your help
SonarQube FAQ recommends the following:
If you get this error message after launching the maven command line "mvn sonar:sonar" add the "-U" parameter to the command line. Maven will then update its local repository with the latest version of the Sonar Maven plugin.
If adding the "-U" parameter doesn't fix your issue, you've certainly encountered Maven bug MNG-4001. The only known workaround is to delete the org\codehaus\mojo directory in your local Maven repository. Of course, if your local Maven repository is synchronized with a repository manager like Nexus, this operation must be also done on the repository manager side.
The problem is simply cause you are using the wrong coordinates of the plugin:
'org.apache.maven.plugins:maven-sonar-plugin'
The sonar-maven-plugin is not part of Apache Software Foundation.
You will find it here:
http://www.mojohaus.org/sonar-maven-plugin/
And how to use it here:
http://www.mojohaus.org/sonar-maven-plugin/plugin-info.html
I'm new to Spring Roo as well as Maven. I was trying to setup a basic Google App Engine web application using Spring Roo. But when I run the tests - perform tests/mvn test - I get an error saying unable to run the goal Unpack due to API incomatibility.
Details:
gae.version: 1.6.1
gae-runtime: 0.9.2
Tried the same with 1.6.0 and 0.9.0 - still gives me the same error.
Exception:
[INFO] --- maven-gae-plugin:0.9.2:unpack (default) # project_x ---
Feb 8, 2012 2:47:40 PM org.sonatype.guice.bean.reflect.Logs$JULSink warn
WARNING: Error injecting: net.kindleit.gae.UnpackGoal
java.lang.TypeNotPresentException: Type net.kindleit.gae.UnpackGoal not present
at org.sonatype.guice.bean.reflect.URLClassSpace.loadClass(URLClassSpace.java:109)
at org.sonatype.guice.bean.reflect.NamedClass.load(NamedClass.java:45)
...
...
... 41 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 27.836s
[INFO] Finished at: Wed Feb 08 14:47:40 IST 2012
[INFO] Final Memory: 6M/12M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.kindleit:maven-gae-plugin:0.9.2:unpack (default) on project project_x: Execution default of goal net.kindleit:maven-gae-plugin:0.9.2:unpack failed: Unable to load the mojo 'unpack' in the plugin 'net.kindleit:maven-gae-plugin:0.9.2' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Bad version number in .class file
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>net.kindleit:maven-gae-plugin:0.9.2
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/Users/myself/.m2/repository/net/kindleit/maven-gae-plugin/0.9.2/maven-gae-plugin-0.9.2.jar
[ERROR] urls[1] = file:/Users/myself/.m2/repository/net/kindleit/gae-runtime/1.6.1/gae-runtime-1.6.1.pom
...
..
I tried googling this issue, but didn't come across anyone facing this issue. I guess, I'm missing some dependency in the generated POM - but due to my inexperience I'm not able to figure out the exact cause.
Let me know, if I need to upload the generated pom.xml or any other details.
meanwhile, I'll continue to figure out what is causing the issue.
Thanks in advance.
Looks like an API incompatibility:
due to an API incompatibility:
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Bad version number in .class file