I am trying to modify the PrimeFaces 1.1 sources to fit my application needs. However I ran into trouble compiling the sources.
I am using the sources from:
http://repository.prime.com.tr/org/primefaces/primefaces/1.1/
Downloaded and extracted:
primefaces-1.1-sources.jar
However when i try to run the primefaces-1.1.pom it fails because its referencing to some XML files which contains the tag info, but I couldn't find those in the sources. I assume this build file is for PrimeFaces 2.x?
Or am i missing something? Would be great if you could help me!
Using Maven "Install"
"c:\program files (x86)\jetbrains\intellij idea 10.0\jre\jre\bin\java" -Dclassworlds.conf=D:\Werk\Binaries\Maven\bin\m2.conf -Dmaven.home=D:\Werk\Binaries\Maven -Didea.launcher.port=7532 "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA 10.0\bin" -Dfile.encoding=windows-1252 -classpath "D:\Werk\Binaries\Maven\boot\plexus-classworlds-2.4.jar;C:\Program Files (x86)\JetBrains\IntelliJ IDEA 10.0\lib\idea_rt.jar" com.intellij.rt.execution.application.AppMain org.codehaus.classworlds.Launcher --no-plugin-registry --fail-fast --no-plugin-updates --strict-checksums --update-snapshots -f C:\Users\Mark\Downloads\primefaces-1.1-sources\pom.xml install
[WARNING] Command line option -npu is deprecated and will be removed in future Maven versions.
[WARNING] Command line option -npr is deprecated and will be removed in future Maven versions.
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.primefaces:primefaces:jar:1.1
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. # line 156, column 12
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building primefaces 1.1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- xslt-maven-plugin:1.0:transform (generate-ui-metadata) # primefaces ---
[ERROR] XSL file does not exist: C:\Users\Mark\Downloads\primefaces-1.1-sources\src\main\resources-maven-jsf\misc\resolve_entities.xsl
[INFO]
[INFO] --- xslt-maven-plugin:1.0:transform (generate-touch-metadata) # primefaces ---
[ERROR] XSL file does not exist: C:\Users\Mark\Downloads\primefaces-1.1-sources\src\main\resources-maven-jsf\misc\resolve_entities.xsl
[INFO]
[INFO] --- maven-jsf-plugin:1.1.3:generate-tld (generate-ui) # primefaces ---
[INFO] Generating TLD
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.711s
[INFO] Finished at: Thu Dec 30 11:29:43 CET 2010
[INFO] Final Memory: 2M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.primefaces:maven-jsf-plugin:1.1.3:generate-tld (generate-ui) on project primefaces: Execution generate-ui of goal org.primefaces:maven-jsf-plugin:1.1.3:generate-tld failed. NullPointerException -> [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/PluginExecutionException
Process finished with exit code 1
If you just need to modify a single class (or a few), it may be easiest to take that class's source code alone, modify and compile it with the rest of Primefaces as JAR in the classpath, then replace that single class file in the JAR.
Related
A little bit of context:
Im working as a FE developer for an AEM project. The project is a SPA AEM as cloud service. I am running the author instance from the command line.
My pc specs are:
CPU: Intel(R) Core(TM) i5-7400 CPU # 3.00GHz 3.00 GHz
RAM: 24.0 GB
SSD: 476 GB
OS: Windows 10 Pro
For the AEM Project we are using
Java sdk 11
Maven 3.6.3
I have already set up everything, the path variables, JAVA_HOME, mvn. All of them work fine, even trying to build other type of projects with "older" versions of AEM like 6.5 build perfectly. I don't have a problem with them. But with this version of AEM I am getting this error
[WARNING] Rule 9: org.apache.maven.plugins.enforcer.RequireFileChecksum failed with message:
There have been changes detected in a file which is supposed to be immutable according to https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html#file-structure: src/conf.dispatcher.d/renders/default_renders.any
[WARNING] Rule 10: org.apache.maven.plugins.enforcer.RequireFileChecksum failed with message:
There have been changes detected in a file which is supposed to be immutable according to https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html#file-structure: src/conf.dispatcher.d/virtualhosts/default_virtualhosts.any
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for xxxxxx 1.0.0-SNAPSHOT:
[INFO]
[INFO] xxxxxx ................................. SUCCESS [ 0.270 s]
[INFO] xxxxxx - Core .......................... SUCCESS [ 59.232 s]
[INFO] xxxxxx - UI Frontend ................... SUCCESS [ 19.876 s]
[INFO] xxxxxx - UI Frontend React ............. SUCCESS [ 39.613 s]
[INFO] xxxxxx - Repository Structure Package .. SUCCESS [ 0.991 s]
[INFO] xxxxxx - UI apps ....................... SUCCESS [ 12.990 s]
[INFO] xxxxxx - UI content .................... SUCCESS [ 4.178 s]
[INFO] xxxxxx - UI config ..................... SUCCESS [ 0.314 s]
[INFO] xxxxxx - All ........................... SUCCESS [ 1.052 s]
[INFO] xxxxxx - Integration Tests ............. SUCCESS [ 12.166 s]
[INFO] xxxxxx - Dispatcher .................... FAILURE [ 0.030 s]
[INFO] xxxxxx - UI Tests ...................... SKIPPED
[INFO] xxxxxx - Project Analyser .............. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:34 min
[INFO] Finished at: 2021-08-22T15:11:20-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce (enforce-checksum-of-immutable-files) on project xxxxxxx.dispatcher.cloud: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :xxxxxx.dispatcher.cloud
I've been searching in sites, some of the answers for this problem haven't work for me.
I tried to run everything from the "gitbash"
command line and I had the same problem.
I tried to change the version in the pom.xml, didnt work.
I tried to build the project using eclipse IDE and all the build-in tools, I get an error that org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce is missing
Disable firewall and antivirus, nope
Use other versions of maven like 3.8.2
Delete the .m2 directory and download again all the plugins, not working
One of many answers tell me to comment out the dispatcher module in the pom.xml and after I did that builds fine. Other is doing the same and upload the ui.apps/target/*.zip with the crx package manager I did it but im not sure if the result is the "best".
To end, I installed the same project in a Mac Pro and i did without a problem. I hope someone can help me with this. Thanks for reading.
[WARNING] Rule 9: org.apache.maven.plugins.enforcer.RequireFileChecksum failed with message:
There have been changes detected in a file which is supposed to be immutable according to https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html#file-structure: src/conf.dispatcher.d/renders/default_renders.any
The Maven Enforcer Plugin is checking for some files to have an specific checksum using requireFileChecksum rule
Somewhere in your pom.xml the Enforcer Maven plugin should be declared, so you will be able to see the rule and the hash it is applying. This xml snippet is from the maven plugin documentation.
<requireTextFileChecksum>
<file>E:\java-workspace\apache-maven-enforcer\maven-enforcer\target\checkout\enforcer-rules\target\classes/foo.txt</file>
<checksum>d41d8cd98f00b204e9800998ecf8427e</checksum>
<type>md5</type>
</requireTextFileChecksum>
Check that hash against the hash of the file of your filesystem. Maybe when you change aem version, you need to upgrade some of those files.
As discussed here: https://github.com/adobe/aem-guides-wknd/pull/202
Adobe have reported the issue and the fix to Adobe AEM WKND project:
Some Windows users experience a Maven enforcer issue where it appears that default dispatcher files have been modified. Unclear if this is a result of differences between Mac and Windows or something that occurs during the checkout process. Most users simply want to install the code base to a local environment and this check is unnecessary. Removing the enforcement for windows builds.
so you can :
Skips Dispatcher enforcement plugin for users on windows environments.
doing a change you dispatcher/pom.xml
with the commit reported here:
https://github.com/adobe/aem-guides-wknd/pull/202/commits/bebcf5d2236c75a95055d5ff71ea58f66379f271
replacing the line:
<goal>enforce</goal>
with:
<goal>display-info</goal>
I am currently trying to start developing a Jira plugin. However, I needed to configure the Maven settings to use my company's proxy server. This proxy seems to block the google analytics server.
When I try to create a new plugin project following the official tutorial the step 2 (execute atlas-create-jira-plugin) produces the following error:
PS C:\Users\XXX\Documents\Jira Plugins\test> atlas-create-jira-plugin
Executing: "C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7\apache-maven-3.5.4\bin\mvn.cmd" com.atlassian.maven.plugins:jira-maven-plugin:8.1.2:create -gs C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7\apache-maven-3.5.4/conf/settings.xml
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------< org.apache.maven:standalone-pom >-------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- jira-maven-plugin:8.1.2:create (default-cli) # standalone-pom ---
[INFO] Google Analytics Tracking is enabled to collect AMPS usage statistics.
[INFO] Although no personal information is sent, you may disable tracking by adding <allowGoogleTracking>false</allowGoogleTracking> to the amps plugin configuration in your pom.xml
[INFO] Sending event to Google Analytics: AMPS:jira - Create Plugin
[INFO] using stable product version: 7.13.0
[INFO] using stable data version: 7.13.0
Define value for groupId: : [ERROR] Error making tracking request
java.net.UnknownHostException: www.google-analytics.com
at java.net.AbstractPlainSocketImpl.connect (AbstractPlainSocketImpl.java:184)
at java.net.PlainSocketImpl.connect (PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect (SocksSocketImpl.java:392)
at java.net.Socket.connect (Socket.java:607)
at java.net.Socket.connect (Socket.java:556)
at sun.net.NetworkClient.doConnect (NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer (HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer (HttpClient.java:558)
at sun.net.www.http.HttpClient.<init> (HttpClient.java:242)
at sun.net.www.http.HttpClient.New (HttpClient.java:339)
at sun.net.www.http.HttpClient.New (HttpClient.java:357)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:1226)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0 (HttpURLConnection.java:1205)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:1056)
at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:990)
at com.dmurph.tracking.JGoogleAnalyticsTracker.dispatchRequest (JGoogleAnalyticsTracker.java:463)
at com.dmurph.tracking.JGoogleAnalyticsTracker.access$100 (JGoogleAnalyticsTracker.java:76)
at com.dmurph.tracking.JGoogleAnalyticsTracker$1.run (JGoogleAnalyticsTracker.java:431)
As I said, I am pretty sure that java.net.UnknownHostException: www.google-analytics.com is caused by my company's proxy.
I then tried to disable google analytics. The problem is: the command does not create any project files until here and so there is no pom.xml that I could edit. When I try to edit the default Maven profile in ~/.m2/settings.xml as described here, Maven complains that the project does not have a pom.xml:
Executing: "C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7\apache-maven-3.5.4\bin\mvn.cmd" com.atlassian.maven.plugins:jira-maven-plugin:8.1.2:create -gs C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7\apache-maven-3.5.4/conf/settings.xml
[INFO] Scanning for projects...
[WARNING] The POM for com.atlassian.maven.plugins:jira-maven-plugin:jar:8.1.2 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.268 s
[INFO] Finished at: 2021-06-18T15:08:01+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin com.atlassian.maven.plugins:jira-maven-plugin:8.1.2 or one of its dependencies could not be resolved: Failure to find com.atlassian.maven.plugins:jira-maven-plugin:jar:8.1.2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [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
Finally, when I try to execute atlas-create-jira-plugin -Dallow.google.tracking=false (also described here) I am getting a similar error:
Executing: "C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7\apache-maven-3.5.4\bin\mvn.cmd" com.atlassian.maven.plugins:jira-maven-plugin:8.1.2:create -gs C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7\apache-maven-3.5.4/conf/settings.xml -Dallow .google.tracking=false
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.203 s
[INFO] Finished at: 2021-06-18T15:14:56+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] The goal you specified requires a project to execute but there is no POM in this directory (C:\Users\KUJ5MU\Documents\Jira Plugins\test). Please verify you invoked Maven from the correct directory. -> [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/MissingProjectException
Does anyone have a solution for this problem? How can I tell the Atlassian SDK not to use Google analytics before creating my first project?
Ignore that error. you can see that error occured after "group id:". So just give ur groupid after the error and press enter. it will as k for the other settings. You can contine from there without issues.
I'm proceeding with the README.md procedure at the following URL, but when compiling, I get the following error message and cannot proceed.
https://github.com/actions-on-google/smart-home-dashboard
[ERROR] Failed to execute goal
org.xolstice.maven.plugins:protobuf-maven-plugin:0.5.0:compile
(default) on project dashboard: An error occurred while invoking
protoc.: Error while executing process. Cannot run program
"C:\test\target\protoc-plugins\protoc-3.5.1-1-windows-x86_64.exe":
CreateProcess error=206, The filename or extension is too long ->
[Help 1]
I put the source code near the C drive, but it didn't solve.
If anyone knows how to solve it, Would you tell me how to solve?
OS：Windows 10
Result of command line：
C:\test>mvn compile
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for com.google.homegraph:dashboard:war:0.1.0-SNAPSHOT
[WARNING]
'dependencies.dependency.(groupId:artifactId:type:classifier)' must be
unique: com.googlecode.objectify:objectify:jar -> duplicate
declaration of version 5.1.22 # line 164, column 15
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique
but found duplicate declaration of plugin
org.apache.maven.plugins:maven-war-plugin # line 304, column 13
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer
support building such malformed projects.
[WARNING]
[INFO]
------------------------------------------------------------------------
[INFO] Detecting the operating system and CPU architecture
[INFO]
------------------------------------------------------------------------
[INFO] os.detected.name: windows
[INFO] os.detected.arch: x86_64
[INFO] os.detected.version: 10.0
[INFO] os.detected.version.major: 10
[INFO] os.detected.version.minor: 0
[INFO] os.detected.classifier: windows-x86_64
[WARNING] The project
com.google.homegraph:dashboard:war:0.1.0-SNAPSHOT uses prerequisites
which is only intended for maven-plugin projects but not for non
maven-plugin projects. For such purposes you should use the
maven-enforcer-plugin. See
https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
[INFO]
[INFO] -------------------< com.google.homegraph:dashboard >-------------------
[INFO] Building dashboard 0.1.0-SNAPSHOT
[INFO] --------------------------------[ war ]---------------------------------
[INFO]
[INFO] --- protobuf-maven-plugin:0.5.0:compile (default) # dashboard ---
[INFO] Compiling 1579 proto file(s) to
C:\test\target\generated-sources\protobuf\java
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.583 s
[INFO] Finished at: 2019-10-22T18:03:49+09:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.xolstice.maven.plugins:protobuf-maven-plugin:0.5.0:compile
(default) on project dashboard: An error occurred while invoking
protoc.: Error while executing process. Cannot run program
"C:\test\target\protoc-plugins\protoc-3.5.1-1-windows-x86_64.exe":
CreateProcess error=206, The filename or extension is too long ->
[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
I'm sorry, it seems my procedure was wrong.
I didn't have to do manually the "Build from source" field in README.md,
I copied extra files in this step.
It was automatically added when compiling at the beginning of the work.
Finally, I was able to compile in the following environment.
OS:Linux (CentOS7)
maven version:3.3.9 (I matched it to the version written in `pom.xml`.)
Good Day,
I try to build "jul-to-log4j-bridge" jar file using Apache Maven 3.6.0 (Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_181\jre)
The aim is to redirect JUL to log4j 1.2.17.
I'm brand new in the java dev world, and have no real background, but :
I installed svn OK
I gathered sources from http://svn.apache.org/repos/asf/logging/sandbox/jul-to-log4j-bridge/ usign svn
(svn export http://svn.apache.org/repos/asf/logging/sandbox/jul-to-log4j-bridge/)
I installed JDK 1.8.0_181 OK
I installed maven 3.6.0 OK
I modified versions of build.plugins.plugin, because they where missing :
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. # line 102, column 15
[WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:cobertura-maven-plugin is missing. # line 109, column 15
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-checkstyle-plugin is missing. # line 92, column 15
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing. # line 152, column 15
usign this kind of command : mvn help:describe -DartifactId=cobertura-maven-plugin -DgroupId=org.codehaus.mojo
=> I modified pom.xml
But I stumble on the concepts of import / packages / plugins etc ... of maven as the error message I got from "mvn package" is :
[INFO] -------------< org.apache.logging:apache-jul-log4j-bridge >-------------
[INFO] Building java.util.logging to log4j Bridge 1.0.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) # apache-jul-log4j-bridge ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) # apache-jul-log4j-bridge ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 8 source files to C:\Users\llv\Documents\#D\Part\maven\svn\jul-to-log4j-bridge\target\classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /C:/Users/llv/Documents/#D/Part/maven/svn/jul-to-log4j-bridge/src/main/java/org/apache/log4j/jul/JULReceiver.java:[19,32] package org.apache.log4j.plugins does not exist
Can someone please help to pass trough this ?
this is about JULReceiver.java..
Any help really appreciated.
thank you
Searching , googling, I founded :
https://logging.apache.org/log4j/extras/
https://logging.apache.org/log4j/extras/apidocs/org/apache/log4j/component/plugins/Receiver.html
And bingo!
package "org.apache.log4j.plugins" does not exist in apache-log4j-extras 1.2.17
but package "org.apache.log4j.component.plugins" does !
So I updated JULReceiver.java from :
import org.apache.log4j.plugins.Plugin;
import org.apache.log4j.plugins.PluginSkeleton;
to:
import org.apache.log4j.component.plugins.Plugin;
import org.apache.log4j.component.plugins.PluginSkeleton;
and compilation is successfull
[INFO] --- maven-source-plugin:3.0.1:jar (default) # apache-jul-log4j-bridge ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.813 s
[INFO] Finished at: 2018-11-08T09:43:07+01:00
[INFO] ------------------------------------------------------------------------
but now tomcat 7.0.23 stops without saying nothing more than :
1/ I set the jar in the classpath:
D:\appli\tomcat\instances\desktop11\lib\apache-jul-log4j-bridge-1.0.0-SNAPSHOT.jar;
2/ I configured all applications using JUL in JVM to use the "apache-jul-log4j-bridge"
JVM parameters:
-Djava.util.logging.manager=org.apache.logging.julbridge.JULBridgeLogManager
instead of the "classic":
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
JVM starts on : D:\opt\jdk1.7.0_80\jre\bin\server\jvm.dll
I guess tomcat (it uses JUL internally) does not supports this java.util.logging.manager ..
or maybe because of this error at compilation (not blocking) about which I seen infos on stackoverflow , but the fix given leads to another pb (I will seach more..)
[INFO] Compiling 9 source files to C:\Users\llv\Documents\#D\Part\maven\svn\jul-to-log4j-bridge\target\test-classes
[WARNING] /C:/Users/llv/Documents/#D/Part/maven/svn/jul-to-log4j-bridge/src/test/java/org/apache/logging/julbridge/MockAppender.java: C:\Users\llv\Documents\#D\Part\maven\svn\jul-to-log4j-bridge\src\test\java\org\apache\logging\julbridge\MockAppender.java uses unchecked or unsafe operations.
[WARNING] /C:/Users/llv/Documents/#D/Part/maven/svn/jul-to-log4j-bridge/src/test/java/org/apache/logging/julbridge/MockAppender.java: Recompile with -Xlint:unchecked for details.
But by the way can someone help me ?
thank you
I tried to run Optaplanner's vrp-dataset-generator. But I have some errors. And I tried to run Optaplanner web examples but it has also error.
This is Web example Error.
## at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke
(JUnit4Provider.java:128)
Results :
Tests in error:
JUnit4Provider.invoke:128->executeTestSet:153->executeWithRerun:173-
>execute:283 ▒ ExceptionInInitializer
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO] ---------------------------------------------------------------------
---
[INFO] BUILD FAILURE
[INFO] ---------------------------------------------------------------------
---
[INFO] Total time: 01:48 min
[INFO] Finished at: 2018-01-28T11:17:13+02:00
[INFO] Final Memory: 78M/149M
[INFO] ---------------------------------------------------------------------
---
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-
plugin:2.18.1:test (default-test) on project optaplanner-webexamples: There
are test failures.
[ERROR]
[ERROR] Please refer to F:\optaplanner\optaplanner-master\optaplanner-
webexamples\target\surefire-reports for the individual test results.
[ERROR] -> [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/MojoFailureException
And this is vrp-dataset-generator's error.
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (no-managed-deps) #
vrpdatasetgenerator ---
[WARNING] Rule 0: org.commonjava.maven.enforcer.rule.EnforceManagedDepsRule
failed with message:
The following 1 dependencies are NOT using a managed version:
- com.graphhopper:graphhopper:jar
[INFO] ---------------------------------------------------------------------
---
[INFO] BUILD FAILURE
[INFO] ---------------------------------------------------------------------
---
[INFO] Total time: 26.236 s
[INFO] Finished at: 2018-01-28T11:26:19+02:00
[INFO] Final Memory: 35M/118M
[INFO] ---------------------------------------------------------------------
---
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-
plugin:1.4.1:enforce (no-managed-deps) on project vrpdatasetgenerator: Some
Enforcer rules have failed. Look above for specific messages explaining why
the rule failed. -> [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 ##
I think I have some issue in Maven, but I can't find errors.
Please help me.
This question is mixing 2 separate questions into one question, which creates a lot of confusion. One is about optaplanner-webexamples, one is about the external repo vrp-dataset-generator.
vrp-dataset-generator is not a part of OptaPlanner. It's not in the OptaPlanner GitHub repository. It's an experimental repo in my GitHub repo. Some day it might be cleaned up and some of the code might be added in optaplanner-examples (or optashift-vehicle-routing when we start that), but today it's not ready for mass-consumption.
(Anyway, the reason vrp-dataset-generator is apparently failing is in the maven pom, that dependency's version should be declared in dependencyManagment instead of just dependencies.)
optaplanner-webexamples should build from source. If it doesn't, well want to figure out why and see if we can improve something in the sources. There's a jenkins job doing also building it and it's green, so it must be something that's different on your local machine. Can you edit your question to include the failing unit test and it's stacktrace? Also state your JDK, maven and wildfly versions.