I am trying to build a GitHub Actions workflow as a Continuous Deployment procedure on this forked repository of a Clojure project.
The process goes well until it reaches this point:
Error: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project flow: Compilation failure: Compilation failure:
Error: Source option 5 is no longer supported. Use 6 or later.
Error: Target option 1.5 is no longer supported. Use 1.6 or later.
Error: -> [Help 1]
Usually, other problems in Stack Overflow related to this error message involve tweaking the pom.xml (see examples: 1, 2, 3, 4, 5, 6).
However, since this is a Clojure project managed by Leiningen, there is not such a file initially. The pom.xml is generated after lein install (and other command) is executed. Clojure is a hosted language on the JVM, after all.
As a side note, I am not sure why this project has :java-source-paths (link) instead of :source-paths. Not sure if this aspect is related to the problem discussed here.
How to fix it?
Related
After making a GitHub repo and adding my code to my account my code now throws me an error, previous resolutions to the error include changing the sequence of the build phases in Xcode but I seem to have no luck, I also don't have a header phase in my build phases which rules out the older method, error below.
Showing Recent Messages
Prepare build
note: Using new build system
note: Planning
note: Build preparation complete
note: Building targets in dependency order
error: Cycle inside Target.swift; building could produce unreliable results.
Cycle details:
→ Target 'Target': CodeSign /Users/macbook/Desktop/target/Build/Products/Debug-iphonesimulator/target.app
Raw dependency cycle trace:
target: ->
node: ->
command: ->
CYCLE POINT ->
node: /Users/name/Desktop/Target/Build/Products/Debug-iphonesimulator/Target.app/_CodeSignature ->
Build failed 4/10/22, 10:12 PM 0.7 seconds
I am running a custom Jenkins 2.263.4 build on Travis-CI. We need a fix with relative pathes that never made it into the Jenkins core...well for us it is mandatory.
Based on release 2.263.4 I applied the fix in core/SecretRewriter.java and core/VirtualFile.java and also changed the version name to give it branding. This worked very well in the past releases. But the last update we did was one year ago.
Now I am running into the error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.2.1:shade (default) on project cli: Error creating shaded jar: duplicate entry: META-INF/services/io.jenkins.cli.shaded.org.apache.sshd.common.io.IoServiceFactoryFactory -> [Help 1]
I am not able to understand it at all.
Travis-CI is here: https://travis-ci.com/github/DanielWeber/jenkins
GitHub: https://github.com/DanielWeber/jenkins
I was not able to find this exact problem from somewhere else. I tried a bit with the shade config to set
<minimizeJar>false</minimizeJar>
and similar small things, but didn't really help.
My change is so small, I don't really understand what's happening.
If nothing helps, I might consider doing changes step by step then, rather than just merging the releae to our for, but hope someone sees the problem.
The issue is that the build is being execute two times based on the mvn install followed by mvn package which is defined in travis.yml file. This causes the issue.
I'm moving some libs to openjdk11 using the third approach described here.
The whole project is being compiled into 8, while only module-info.class to 11.
In the process of doing this, I found out that writing an empty main somewhere and running it, is the quickest way to check if there are any missing dependencies, the module-info.java has been properly detected and configured (because apparently gradle build is not that reliable).
I already did this for glm, which has two modules, decleared in the same build.gradle
Now I'm testing uno, but unfortunately I keep getting this error
Error:(1, 1) java: modules are not supported in -source 8
(use -source 9 or higher to enable modules)
My question is, why do I keep this error, when glm works fine?
I´m trying to optimizes a planning problem with OptaPlanner - it should be a lightweight and easy.
It´s the first time I get in contact with such programming stuff, but I´m quite proud for going as fare in a few days (for it is not easy at all - and all in English (I´m German) - Last time I was programming Pascal 25 years ago in secondary-school.)
I downloaded and installed
optaplanner-distribution-6.5.0.Final.zip
jre-8u121-windows-x64.exe
I could run the Examples!
Now I would like to customise one example and therefore run the Examples in an IDE fist.
I downloaded and installed
NetBeans 8.2 Patch 1
jdk-8u121-nb-8_2-windows-x64.exe
apache-maven-3.3.9-bin.zip
So I just open the file examples/sources/pom.xml as a new project (as recommended in OptaPlanner User Guide 1.4.2)
but the maven integration will not take care of the rest.
I receive the error report below.
What should I do now?
Is there a simple trick I could use?
Or a simpler way to succeed?
Or is this all to difficult for the fist task?
Do I have to learn all about maven plugins?
Do I have to be an NetBeans expert fist?
Downloaded: https://repository.jboss.org/nexus/content/groups/public/org/jboss/shrinkwrap/descriptors/shrinkwrap-descriptors-bom/2.0.0-alpha-8/shrinkwrap-descriptors-bom-2.0.0-alpha-8.pom (6 KB at 7.1 KB/sec)
Some problems were encountered while building the effective model for org.optaplanner:optaplanner-examples:jar:7.0.0.Beta7
'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-project-info-reports-plugin is missing. # org.kie:kie-parent:7.0.0.Beta7, C:\Users\ray-club.m2\repository\org\kie\kie-parent\7.0.0.Beta7\kie-parent-7.0.0.Beta7.pom, line 1173, column 15
'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-jxr-plugin is missing. # org.kie:kie-parent:7.0.0.Beta7, C:\Users\ray-club.m2\repository\org\kie\kie-parent\7.0.0.Beta7\kie-parent-7.0.0.Beta7.pom, line 1177, column 15
'reporting.plugins.plugin.version' for org.codehaus.mojo:findbugs-maven-plugin is missing. # org.kie:kie-parent:7.0.0.Beta7, C:\Users\ray-club.m2\repository\org\kie\kie-parent\7.0.0.Beta7\kie-parent-7.0.0.Beta7.pom, line 1203, column 15
It is highly recommended to fix these problems because they threaten the stability of your build.
For this reason, future Maven versions might no longer support building such malformed projects.
and at the end
Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message: To build this project Maven 3.2.5 (or greater) is required. Please install it.
BUILD FAILURE
Total time: 4:00.537s
Finished at: Sat Mar 25 17:21:31 CET 2017
Final Memory: 22M/154M
Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) on project optaplanner-examples: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.
For more information about the errors and possible solutions, please read the following articles:
[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
When I build my project by tycho-maven-plugin, I encounter the following message:
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: foo-updatesite raw:0.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.2.0-SNAPSHOT
[ERROR] Missing requirement for filter properties ~= $0: foo-feature.feature.group 0.2.0.qualifier requires 'foo-plugin 0.0.0' but it could not be found
[ERROR] Cannot satisfy dependency: foo-updatesite raw:0.2.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.2.0-SNAPSHOT depends on: foo-feature.feature.group [0.2.0,0.2.1)
This error occurs when building an update site. Plugin and feature are build normally. I build the update site from PDE without issues.
The project structure is common: there is a parent project with pom packaging and three modules: plugin, feature and updatesite. Of course, I invoke mvn clean package from the parent project.
What can be the reason for this error? How can I debug it?
UPD: I tried many things: removed "grandparent" pom, removed SNAPSHOT/qualifier, played with configuration. However, I found the solution: I switched to tycho 0.19 instead of 0.21. So I suppose there is a bug in tycho 0.21.
The error message
Missing requirement for filter properties ~= $0
indicates that you have defined an environment filter when you include the plugin foo-plugin in the feature.xml. However this does not explain the dependency resolution error you are seeing. The only way I can reproduce the error message is by adding an Eclipse-PlatformFilter header in the manifest of the plugin using a value which doesn't match environments configuration in the POM.
I had the same error message:
Missing requirement for filter properties ~= $0: foo-feature.feature.group 0.2.0.qualifier requires 'foo-plugin 0.0.0' but it could not be found
For some reason this error (also) means, that foo-plugin is present... twice.
So in your case, open the "Content" tab of the "Target Editor" and make sure that foo-plugin is not present in two distinct versions. I common way this could happen is if two features contain the same bundle.