Our installer build (using install4j 5.1.15) has started generating warnings (about 1500 per media file) which I think might be related to the fact that we have upgraded our project to Java 8. Is there a way to solve this? Should we be concerned about this message? Can it cause any problems? I found this post but it doesn't explain if it can cause problem, or if there's a way to resolve the issue (e.g.: upgrading to a newer version of install4j)
[INFO] [warning] major version should be between 45 and 51 for JDK <= 1.7
install4j 5 cannot read Java class file with -target 1.8. install4j checks your code for usages of the install4j API so that the shrinked runtime file includes all required classes. The warning messages mean that install4j cannot perform this task. You can switch off runtime shrinking to avoid this problem on the "General Settings->Media File Options" step.
Also, this problem goes away when using install4j 6.
Related
Due to where I work I am mot allowed to use screenshots although it is just one error anyway.
Friday I upgraded to Eclipse 2021-03 and AdoptOpenSDK 16. My main project (ActivePivot webapp) built successfully with Java 8 so I went home all happy and ready to come back Monday for the main plan!
Monday I obtained the vendor's Java11 only libs and added stuff to my repo. I have lots to do for the Java 11 cut but that is another story. (Feel free to tell me to go back to the LTS 11 if this is better although I thought I should be able to have two projects; 1 at 8 and 1 at 11 for time being).
Where I added the newer libs to the repo it obviously broke my Java 8 project. I thought it would be a simple case of just adding version tags for the many libraries/folders but of course, maybe it just me, but I've seen Maven get itself in a right old state before. And it did this time... :)
Eclipse launched the store and suggested I install some stuff to help with the project and it had detected I need Maven Natures. So I went with it. After that I now see this error:
'Could not initialize class org.apache.maven.plugin.war.util.WebappStructureSerializer pom.xml /cacib-activepivot line 1 Maven Configuration Problem'.
Has anyone seen this before? I can't seem to find much on it!
Thanks in advance for your assistance.
Leigh
tilleytech.com
Eclipse 2021-03 was released at the same time as Java 16 and therefore has no built-in Java 16 support yet and was only able to be tested with early-access builds of Java 16.
Running Eclipse with Java 16 might cause issues in some plugins because of more stricter permissions in Java 16:
JEP 396: Strongly Encapsulate JDK Internals by Default
In eclipse.ini adding --illegal-access=permit should fix that (see e.g. here).
For using Java 16 in your projects (which is independent from the Java used to run Eclipse), install Java 16 Support for Eclipse 2021-03 (4.19), try a developer build or wait for Eclipse 2020-06, which will be released on 16 Juni, 2021. Also make sure that additionally installed plugins are up to date.
My application isn't running correctly with Java 9. In order to debug it, I upgraded to Eclipse 4.7 (oxygen) since Neon doesn't have Java 9 support, and applied the Java 9 support patch.
After doing so, eclipse was failing to load any of my pre-existing Java Applications. Thinking it might be a version difference thing, I deleted them, to try re-adding. But when I click the "New" button to add a configuration, nothing happens.
If I double-click "Java Application," I get the following error:
An error has occurred. See error log for more details.
tried to access method org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.getTabViewer()Lorg/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationTabGroupViewer; from class org.eclipse.jdt.internal.debug.ui.launcher.LocalJavaApplicationTabGroup
I am able to add configurations for other types of applications (Java Applet, Eclipse Application) so it seems only to be an issue with Java Applications.
I also tried a fresh workspace, but that has the same issue. How can I fix this?
This is kind of a duplicate but since I experienced the issue and have seen a few others post about it, I'll post my answer of how I fixed it here.
If you go here: https://marketplace.eclipse.org/content/java-9-support-beta-oxygen/
You need to follow the step about updating Eclipse 4.7 from the link that ends in 4.7-U-builds. When you go to Install New Software and select Eclipse SDK, click Next until you get to the Install Remediation Page, and make sure that you are selecting the second option that says something like "update my installation to be compatible with the items being installed" instead of the option that says "keep my installation the same and modify the items being installed to be compatible."
The first time I installed Java 9 updates, I did it the latter way and ran into this problem. Now that I've gone back and chosen the former, I am able to add Java Application Run Configurations again.
Hope this helps.
Eclipse Oxygen.1a (4.7.1a) Release
Update as of 11 October,2017 - You shall upgrade to the latest eclipse package Eclipse Oxygen.1a (4.7.1a) which is marked as released and supports Java 9.
I just upgraded my version of Eclipse to 4.5.1. I have a target platform and if I use it, it takes 1 min 45 seconds for the instance of Eclipse to startup. If I use the running platform instead, it takes all of 10 seconds.
I found this bug report which seems to suggest that the issue crept in between 4.5M1 and 4.5M2, but apparently has been fixed in the latest version of Mars. In light of my unsuccessful attempt, what specific version of Mars eliminates this issue if I use a target platform?
I wish to load my applet with JRE version 1.6.0_14. I have installed updates 14, 17, 24 and 35. I am using <object> tag with classid to load version with update 14.
in this case, the applet get loaded with update 35 and then again with update 14. on the java console on update 35 no error noticed and on Java console of update 1.6.0_14 we see the following error.
java.lang.ClassNotFoundException: sun/net/www/protocol/http/NTLMAuthenticationCallback
How to avoid higher version JRE to be used? And how to avoid the class not found error?
It is a serious security risk to run with a lower version of the JRE. Not when you run your own applet, cause you trust your own code. But others ought to refuse running it. You, yourself, should be wary when browsing the net with a browser that does not have the latest version of the JRE installed.
The JRE installer installs the Java Plugin into your browser and one single version of the Plug-in will always be started, independent of the Java version you request. The Plugin will then run the applet in the JRE that is specified in the classid of your object tag. The versions available to the Plug-in are configurable in the Java Control Panel.
This leaves the question of why your application won't run with a recent version of java 1.6. The Plugin got a big overhaul in 1.6.0_something into what's called the Next Generation Plug-in. Maybe that is what is giving you trouble. You can indicate that you wish to use the old Plug-in on your machine in the Java Control Panel on the advanced tab. ("Enable the Next Generation Java Plug-in (requires a Browser restart"). I'd think it's interesting to know if disabling the Next Generation Plug-in solves your issue.
Since adding the Blackberry Java classes from their website into eclipse, I've had it where eclipse will randomly close, with no discernible pattern, rhyme, error or reason. Here is the environment/software packages that I am using:
Windows XP SP2
Eclipse v3.5.1
Blackberry Java Plugin v1.1.1.200911111641-15
Blackberry Java SDK 4.5.0.21
I've tried the usual steps of complete uninstall and reinstallation of Eclipse and the accompanying plugins on multiple systems with the same configuration, including one that had a fresh install of Windows XP SP2. Upgrading to Eclipse 3.6 didn't work (the plugin wont' install as it's the wrong version), nor the downgrade to 3.4 for the same reason. I also increased the heap size to 512 (system has two gigs of memory) as some research into Eclipse doing this type of thing with Groovy was resolved that way, but again, no dice. Eclipse works great when the blackberry plugins are not installed, and no entries of errors or issues in the event log are helping to show what the issue with these plug-ins might be.
So if anyone has ran into this issue, and even better, has a solution, I'd love to hear about it. Thanks in advance.
EDIT: An additional to my issue, autoComplete with the Blackberry SDK seems to make this extremely unstable, like almost a guaranteed crash. Is this fixable at all?
For anyone that loads this question up trying to find a solution, I've never found a fix. It seems to be a bug with this version of the IDE. If there is a fix, please post.
Did you try to downgrade Eclipse to 3.4 (Ganymede)? I experienced similar issues when I tried upgrading Eclipse to something greater than 3.4.2.
I think the problem is with the plugin, not the IDE. Eclipse has always been stable for me until I installed the BB plugin. Since then it crashes all the time. Since I've installed the release (non-beta) version of the plugin that was recently released I can't even get my project to build.
This could be a manifestation of this bug in Eclipse. Check your C:\eclipse directory for files like hs_err_pidxxxx.log. The file goes on to explain this error:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x753ba053, pid=3144, tid=5820
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [USP10.dll+0x1a053]
I've been experiencing this as well. It's completely debilitating. It causes Eclipse to just up and crash out of nowhere (and programming in a language as verbose as Java without Content-Assist is insane).
The bug has been fixed in Eclipse 3.6M7, but unfortunately I can't get the JDE Plug-in to install in the latest release candidate.
This is a known issue with Eclipse 3.5.X and has been fixed for 3.6.0
Bug Ticket link on Eclipse Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=283503
Looks like we are stuck with this until the next update to the BB Eclipse plugin.