When I run my Maven-managed CodeNameOne project, Maven gives me some alerts that make me worried.
The alerts are:
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.iw.mobile:iwcareapp-javase:jar:1.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.codenameone:codenameone-core:jar -> duplicate declaration of version (?) # line 60, column 19
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.codenameone:codenameone-javase:jar -> duplicate declaration of version (?) # line 70, column 19
[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]
Are these alerts deserve attention?
If yes. Is there any work being done to eliminate them?
This is a relatively simple warning that as far as I know is necessary for compatibility across versions of Maven. Removing the duplication should be easy if such a future version ever comes out.
Related
I'm getting this error. It all started when I tried to make use of react-native-camera and run my project
> Task :react-native-camera:compileGeneralDebugJavaWithJavac
> Task :app:mergeDexDebug FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
252 actionable tasks: 33 executed, 219 up-to-date
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\Users\joans\Desktop\Project\new_project\node_modules\react-native-camera\android\src\main\java\com\google\android\cameraview\Camera2.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
D8: Cannot fit requested classes in a single dex file (# methods: 65711 > 65536 ; # fields: 71075 > 65536)
com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
The number of method references in a .dex file cannot exceed 64K.
Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html
.....
* What went wrong:
Execution failed for task ':app:mergeDexDebug'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
The number of method references in a .dex file cannot exceed 64K.
Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html
Please, any suggestions would be helpful
I am getting an error while adding packages to the julia:
Error
DataFrame
(#v1.5) pkg> add DataFrames
Updating registry at `C:\Users\.julia\registries\JuliaComputingRegistry`
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package DataFramesMeta [1313f7d8]:
DataFramesMeta [1313f7d8] log:
├─DataFramesMeta [1313f7d8] has no known versions!
└─restricted to versions * by an explicit requirement — no versions left
CUDA
(#v1.5) pkg> add CUDA
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package CUDA [052768ef]:
CUDA [052768ef] log:
├─CUDA [052768ef] has no known versions!
└─restricted to versions * by an explicit requirement — no versions left
This happens every time I try to add any package to julia. I have tried reinstalling the julia but the issue still persist.
Please suggest a solution to this issue. I have also posted this issue on julia-discourse.
Thanks in advance.
Update
The issue is related to cloning of registry during update. Apparently, it is some kind of a bug.
To resolve this issue, you may delete the registry/General folder and then restart Julia. This will make Julia to rebuild all the packages and then everything should run smoothly.
To delete the folder, one may either go to console and perform following operations:
(#v1.5) pkg> registry rm General
Removing registry `General` from ~/.julia/registries/General
or
Look for the folder .julia/registries/General (tested in windows) and delete it manually. (Path will look something like this: C:\Users\User\.julia\registries\General
Thanks!!
My app compile for android ok.
When I create the android certificate, and send to the codename compiler it don´t compile.
I tried to generate the certificate with the keytool and tried with the assitant on codenameone, the result is similar.
If I delete the keystore file and resend to the dashboard, the app compile ok.
This is the log errors
Note: there were 3 references to unknown classes.
You should check your configuration for typos.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unknownclass)
Note: there were 1 references to unknown class members.
You should check your configuration for typos.
Note: there were 22 unkept descriptor classes in kept class members.
You should consider explicitly keeping the mentioned classes
(using '-keep').
(http://proguard.sourceforge.net/manual/troubleshooting.html#descriptorclass)
Note: there were 17 unresolved dynamic references to classes or interfaces.
You should check if you need to specify additional program jars.
(http://proguard.sourceforge.net/manual/troubleshooting.html#dynamicalclass)
Note: there were 5 class casts of dynamically created class instances.
You might consider explicitly keeping the mentioned classes and/or
their implementations (using '-keep').
(http://proguard.sourceforge.net/manual/troubleshooting.html#dynamicalclasscast)
Warning: there were 25 unresolved references to classes or interfaces.
You may need to add missing library jars or update their versions.
If your code works fine without the missing classes, you can suppress
the warnings with '-dontwarn' options.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedclass)
Warning: there were 2 unresolved references to program class members.
Your input classes appear to be inconsistent.
You may need to recompile the code.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedprogramclassmember)
Warning: Exception while processing task java.io.IOException: Please correct the above warnings
first.
:transformClassesAndResourcesWithProguardForRelease FAILED
:transformClassesAndResourcesWithProguardForRelease (Thread[Task worker for ':',5,main]) completed. Took 3.21 secs.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':transformClassesAndResourcesWithProguardForRelease'.
> Job failed, see logs for details
* Try:
Run with --debug option to get more log output. Run with --scan to get full insights.
* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task
':transformClassesAndResourcesWithProguardForRelease'.
at
This has nothing to do with the certificate. It fails in the obfuscation stage before the certificate. These errors are notoriously hard to read and it seems you snipped it a bit too late. I need the section above that which includes the detailed warning about the class/method that isn't found.
Go to the error and scroll a bit higher and look for a familiar class name with a proguard warning next to it. This is the class causing a problem probably because of a missing dependency. If you can't find it just post the log link to the website chat and our support will look over that for you.
We are inundated with the entry:
Deprecated: Directive 'safe_mode' is deprecated in PHP 5.3 and greater in Unknown on line 0
Deprecated: Directive 'safe_mode' is deprecated in PHP 5.3 and greater in Unknown on line 0
Deprecated: Directive 'safe_mode' is deprecated in PHP 5.3 and greater in Unknown on line 0
in the apache2 error logs. But the bug doesn't seem to have any notable effect on our systems. It makes it very hard for us to diagnose actual problems and errors by overfilling our error logs.
None of the sysadmins I work with are aware of when the error started appearing or what software might be causing it.
We are using Apache/2.2.16 on Debian.
Edit: I have tracked the problem down to Froxlor adding per-user ini files, some of which have safe_mode enabled. There seems to be no way to disable safe_mode either globally in froxlor or per user and the froxlor manual has nothing. Any help?
Safe_mode is a PHP feature that has been depreciated in 5.3 and ultimately removed in 5.4. It is pointless and potentially dangerous and should not be used.
To turn it off go to your php.ini file and change
safe_mode = on
to
safe_mode = off
Restart apache and you should be good to go.
I am using Eclipse 3.6 (Helios64) and m2eclipse 0.12.1.20110112-1712. I have a new project that only contains two classes that builds a jar. When I right click the project and select "Run As -> Maven package", I get the following error:
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) # switch-provisioning-rest-client --- [INFO] Compiling 2 source files to C:\Devel\EclipseProjects\MyProject\target\classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Failure executing javac, but could not parse the error:
javac: invalid flag: -s
...
[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.
When I set up a run configuration with the Goals "package -X", the project builds without error. If I run a configuration with the goal set to compile, it builds without error and I can then run "Maven package" successfully.
This is the only project I'm having issues with. All my other projects build sucessfully when doing a "Maven package".
There's nothing exceptional about the project pom.xml. It refers to the same parent pom as the other projects and contains its project specific dependencies.
Has anybody got any ideas what could be different about this project?
TIA!
This issue was answered on the m2eclipse mailing list:
http://dev.eclipse.org/mhonarc/lists/m2e-users/msg01818.html
Although my pom had 1.6 as the version, the project configuration hadn't been updated.
From: Benjamin Bentmann
This issue is not really specific to m2e but applies to mvn in general, as such the Maven user list might provide a better audience for help.
IIRC, the specific error means you trying to use a JDK 1.5 while you need JDK 1.6+ where the javac option in question was added. Assuming your project should actually compile against JDK 1.5, downgrading the maven-compiler-plugin version might also do, I would expect it started to use the -s option when the annotation processing support was added.