Find a replacement for -Xbootclasspath/p option when using jdk 11 - jboss

I am upgrading to jdk 11 and from what I've noticed, the -Xbootclasspath/p option no longer exists. I've tried replacing it with -Xbootclasspath/a, I've also tried using --patch-module(although I've read that it's not recommended in production) or --add-module options instead and none of them seems to work. The reason why -Xbootclasspath/p was added in the first place is the following error:
Could not load Logmanager "org.jboss.logmanager.LogManager"
Do you have any other idea what I should try in order to replace or get rid of -Xbootclasspath/p option? Thanks!

Related

Netbeans php-cs-fixer end up with error "Files that were not fixed due to errors reported during linting after fixing:"

I am using php-cs-fixer for code formatting in Netbeans 8.2. When I try to format one file, it shows the error
Files that were not fixed due to errors reported during linting after fixing:
I searched for the fix in many websites, but couldn't get this fixed. Is there any way to fix this? I tried with both php-cs-fixer 1 and php-cs-fixer 2.
The error message means that PHP CS Fixer loaded some files from drive, apply changes on them, and then realised that files are not valid anymore (invalid PHP syntax) after those changes, thus it decided to not save it. That's one of the safety mechanism of PHP CS Fixer to not break your project.
This means that you have found an issue in PHP CS Fixer itself.
Please, verify you are using newest release, maybe the bug was already fixed!
If not, please consider to expose your configuration file (if any) and content of files you got listed at https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/new !
There is also an option to see what happen in progress.
$ ./vendor/bin/php-cs-fixer fix src/ErrorFile.php -vvv
The --verbose option will show the applied rules. When using the txt format it will also display progress notifications.
NOTE: if there is an error like "errors reported during linting after fixing", you can use this to be even more verbose for debugging purpose
-v: verbose
-vv: very verbose
-vvv: debug

New Delimited File Preview error

I am trying to use Talend Open Studio v5.4.1.
When I want to create a new delimited file metadata, I get the following message error:
Failed to generate code.
Preview error. Some settings must be changed.
Note: Preview errors are generally due to a wrong encoding setting.
org.talend.designer.runprocess.shadow.ShadowFilePreview.preview(ShadowFilePreview.java:90)
org.talend.repository.ui.utils.ShadowProcessHelper.getCsvArray(ShadowProcessHelper.java:383)
org.talend.repository.ui.wizards.metadata.connection.files.delimited.DelimitedFileStep2Form$PreviewProcessor.nonUIProcessInThread(DelimitedFileStep2Form.java:1249)
org.talend.commons.ui.swt.thread.SWTUIThreadProcessor$1.run(SWTUIThreadProcessor.java:74)
And I know the problem is not coming from my file setting because I did the same on Talend OS v6 and it worked!
But I have to use the v5.4.1
I tried running it as an administrator but it didn't change anything.
I finally resolved it. The problem is that the v.5.4.1 doesn't support the Java 1.8.
So the solution is to install the JDK/JRE 1.7 and specify the path into Talend.
In my case it was incorrect setting in Preferences/Java/Installed JRes that was the cause of the same error.
I set JRE home to C:\Program Files\Java\jdk1.8.0_121\bin (wrong) instead of C:\Program Files\Java\jdk1.8.0_121 (right)

Typo3 4.7.0 update breaks my FE login?

I've updated my Typo3 from 4.5.5 to 4.7.0 and I get several deprecated errors:
ERROR: Content Element type "login" has no rendering definition!
call to undefined error in t3lib_div::view_array
fail to include class.t3lib_htmlmail.php
The install tool gives me "typo3/ext/ directory not writable" but I've the correct right. I've even allow all?????
When I select a CType Element in the BE it give me this warning: PHP Warning
PHP Warning: Invalid argument supplied for foreach() in /var/www/typo3_src-4.7.0/t3lib/l10n/parser/class.t3lib_l10n_parser_llphp.php line 95
The solution for 2. is to use the new class t3lib_utility_debug but what is with the other errors?
Edit: 1. http://lists.typo3.org/pipermail/typo3-english/2011-November/078129.html
Edit 2: The solution for the missing class t3lib_htmlmail is to include another class t3lib_mail_message: require_once(PATH_t3lib .'mail/class.t3lib_mail_message.php');
You solved allready: install system extension "felogin"
you solved allready: use t3lib_utility_debug
check where the error is from. Often it is helpfull to search for that file in typo3conf/temp_*.
You could check your filesystem, if your webserver is allowed to write to typo3/ext/. I guess, it is not. But you do not need to. Usually you install extensions to typo3conf/ext/.
Update your language files via the extension manager.
Well, i know it is to late now, but for all others wo think about an update: just activate the deprecation log in the isntall toll and fix that problems first!
Updating from 4.5.X to 4.7.x broke my felogin as well. The reason was that there has been a local extension installation that has been of higher priority than the system one. So if you suffer the same update issue, check for an local installation of felogin in "typo3conf/ext" - and delete it in case it is there. This solved my problem!

Problems using netbeans 7.01 with CMake 2.8.6

so once again, I'm having a little problem I can't figure out myself. Meaning, I'm pretty sure I know what the problem is, I just can't fix it.
I'm developing in C++ using Netbeans 7.01 with CMake 2.8.6. However, when I'm trying to build a project, I get the following error from CMake:
CMake Error: The path to the source directory:
H:/Projects/Netbeans/CppApplication_1/CONF=Release
contains unsupported character '='.
Please use a different source directory name.
Please note, that "CONF=Release" isn't a folder. It seems to be a configuration flag set by Netbeans, as it changes when I'm trying a debug build. So, my guess here is, that theres a space missing, or something similar. Unfortunately, I can't figure out where to change that. There are no options in any related Netbeans window, I can't find anything related in the configuration files for netbeans itself or the project either.
Did anyone here have experienced the same problem and found a solution to it? I would be very glad to hear it. If there's any information missing, let me know, I will add them as fast as possible.
Edit:
Just noticed there is already version 7.1 of netbeans, nice to know. However, even with this version, the same problem occurs.
You must specify the command you ran to allow for the error to be identified. However, it looks like you missed the "source-path" parameter.
The cmake command ends with the path to source and should be something like:
cmake -D CONF=Release <path to source>

syntax error before '^' token in UIView.h - not fixed by changing compiler setting

I installed the latest official iphone sdk and now my personal project is getting the same compiler error in UIView.h as described in this question:
Syntax error before '^' token
syntax error before '^' token
The solution is apparently to change compiler settings to use GCC 4.2 or LLVM.
I've tried using every compiler setting available in Xcode that but am still getting the errors.
Is there something else I should be doing to support the (^) block syntax in my project. The project was building fine with the previous official sdk release (pre OS4)
Another strange detail, I only get the error in debug config, not release.
I tried comparing the build settings between debug and release but didnt see any major differences. Where there were differences I tried setting the debug config to use the release config values but still getting those errors.
thanks in advance for any help
ok so I just found my problem.
I was changing build settings by right click -> Get Info on the project but I should have been doing it on the target (which was still using GCC 4.0 even though the project was set to 4.2)
Make sure you have the right configuration or configurations picked when you change compile settings. It's easy to overlook this, for example: picking the Release build when you meant the Debug, or vice versa; or by using other custom build configurations.