In IntelliJ 2017.2.2 I am able to run a Vaadin 8.1.2 app (brand-new vaadin-archetype-application archetype) with Tomcat 8.5.20 under Java 9+181 if the Project Structure > Project SDK is set to Java 1.8.
If Project Structure > Project SDK is set to Java 9 I get this compiler error around FillIn with assertion error about filling something to do with Vaadin MouseEvents. I have tried googling but found no clues.
Information:java: An exception has occurred in the compiler (9). Please file a bug against the Java compiler via the Java bug reporting page (http://bugreport.java.com) after checking the Bug Database (http://bugs.java.com) for duplicates. Include your program and the following diagnostic in your report. Thank you.
Information:java: at jdk.compiler/com.sun.tools.javac.code.ClassFinder.fillIn(ClassFinder.java:340)
Information:java: at jdk.compiler/com.sun.tools.javac.code.ClassFinder.complete(ClassFinder.java:285)
Information:java: at jdk.compiler/com.sun.tools.javac.code.Symbol.complete(Symbol.java:633)
Information:java: at jdk.compiler/com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:1314)
Information:java: at jdk.compiler/com.sun.tools.javac.code.Symbol$ClassSymbol.flags(Symbol.java:1248)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Resolve.isAccessible(Resolve.java:405)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Resolve.isAccessible(Resolve.java:389)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Resolve.findImmediateMemberType(Resolve.java:2170)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Resolve.findMemberType(Resolve.java:2225)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Resolve.findIdentInType(Resolve.java:2403)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.selectSym(Attr.java:3588)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3453)
Information:java: at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCFieldAccess.accept(JCTree.java:2104)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.attribTree(Attr.java:653)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.attribType(Attr.java:713)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.attribType(Attr.java:706)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.attribBase(Attr.java:859)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter$AbstractHeaderPhase.attribSuperTypes(TypeEnter.java:669)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter$HierarchyPhase.runPhase(TypeEnter.java:742)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter$Phase.doCompleteEnvs(TypeEnter.java:270)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter$HierarchyPhase.complete(TypeEnter.java:785)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter$HierarchyPhase.doCompleteEnvs(TypeEnter.java:730)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter$Phase.completeEnvs(TypeEnter.java:245)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter$Phase.completeEnvs(TypeEnter.java:254)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.TypeEnter.complete(TypeEnter.java:195)
Information:java: at jdk.compiler/com.sun.tools.javac.code.Symbol.isInterface(Symbol.java:393)
Information:java: at jdk.compiler/com.sun.tools.javac.jvm.ClassReader.readMethod(ClassReader.java:2353)
Information:java: at jdk.compiler/com.sun.tools.javac.jvm.ClassReader.readClass(ClassReader.java:2641)
Information:java: at jdk.compiler/com.sun.tools.javac.jvm.ClassReader.readClassBuffer(ClassReader.java:2706)
Information:java: at jdk.compiler/com.sun.tools.javac.jvm.ClassReader.readClassFile(ClassReader.java:2719)
Information:java: at jdk.compiler/com.sun.tools.javac.code.ClassFinder.fillIn(ClassFinder.java:348)
Information:java: at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.complete(Type.java:1139)
Information:java: at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.getTypeArguments(Type.java:1065)
Information:java: at jdk.compiler/com.sun.tools.javac.code.Type$ClassType.isErroneous(Type.java:1095)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Check.checkNonCyclicInternal(Check.java:2316)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Check.checkNonCyclicInternal(Check.java:2327)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Check.checkNonCyclicInternal(Check.java:2330)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Check.checkNonCyclicInternal(Check.java:2323)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Check.checkNonCyclic(Check.java:2277)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.checkBase(Attr.java:901)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Attr.attribBase(Attr.java:860)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Enter.complete(Enter.java:577)
Information:java: at jdk.compiler/com.sun.tools.javac.comp.Enter.main(Enter.java:554)
Information:java: at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:1052)
Information:java: at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:923)
Information:java: at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:100)
Information:java: at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:142)
Information:java: at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:96)
Information:java: at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:90)
Information:java: at org.jetbrains.jps.javac.JavacMain.compile(JavacMain.java:190)
Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.compileJava(JavaBuilder.java:473)
Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.compile(JavaBuilder.java:328)
Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.doBuild(JavaBuilder.java:255)
Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.build(JavaBuilder.java:208)
Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.runModuleLevelBuilders(IncProjectBuilder.java:1260)
Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.runBuildersForChunk(IncProjectBuilder.java:937)
Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.buildTargetsChunk(IncProjectBuilder.java:1009)
Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunkIfAffected(IncProjectBuilder.java:900)
Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunks(IncProjectBuilder.java:733)
Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:385)
Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:192)
Information:java: at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:138)
Information:java: at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:295)
Information:java: at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:125)
Information:java: at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler.lambda$channelRead0$0(BuildMain.java:236)
Information:java: at org.jetbrains.jps.service.impl.SharedThreadPoolImpl.lambda$executeOnPooledThread$0(SharedThreadPoolImpl.java:42)
Information:java: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
Information:java: at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
Information:java: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
Information:java: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
Information:java: at java.base/java.lang.Thread.run(Thread.java:844)
Information:java: Errors occurred while compiling module 'vnine'
Information:javac 9 was used to compile java sources
Information:Module "vnine" was fully rebuilt due to project configuration/dependencies changes
Information:2017-08-18, 15:40 - Compilation completed with 2 errors and 0 warnings in 1s 866ms
Error:java: java.lang.AssertionError: Filling jar:file:///Users/basilbourque/.m2/repository/com/vaadin/vaadin-server/8.1.2/vaadin-server-8.1.2.jar!/com/vaadin/ui/Component$Event.class during JarFileObject[/Users/basilbourque/.m2/repository/com/vaadin/vaadin-server/8.1.2/vaadin-server-8.1.2.jar:/com/vaadin/event/MouseEvents$ClickEvent.class]
Error:java: at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:162)
So, two questions:
Can IntelliJ + Vaadin + Tomcat be made to work under Java 9 yet? (that is, running as a Java 9 project – does indeed run on Java 9 but only as a Java 8 project)
If so, what might be the problem in my case using a brand-new unmodified Vaadin application Maven archetype?
Inlined as timeline
What might be the problem in my case using a brand-new unmodified Vaadin application Maven archetype?
To get to the root cause for your case specifically, we would surely need more details to what you've tried in terms of code definitions.
Can IntelliJ + Vaadin + Tomcat be made to work under Java 9 yet?*
On 22 August 2017
Yes.You can make this specific combination work. After solving the problem where I was Unable to process file module-info.class within a Java9 project results in ClassFormatException I could get the war created using mvn package to run with tomcat finally.
Details: You need to use a Java 9 compatible version of Tomcat. (apache-tomcat-9.0.0.M26 in my case) and configure it to start with
Using JRE_HOME: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/
Once the server is started, you can access the application # localhost:8080/vaadinjavanine/ where vaadinjavanine is the war file name within my tomcat's webapps folder.
On 21 August 2017
The answer specific to the combination sadly is still No. I believe it's not yet possible to make this combination work.
Jetty Server
Here's a sample application updated by me which works with IntelliJ + Vaadin + Jetty on my localhost:8080 using Jetty server, irrespective of my Project SDK being set to Java1.8 or Java9. It works something like this:
This was attained after overcoming the #jetty.project/1758 by upgrading to the 6.0_BETA of asm and asm-commons libraries and using the custom 9.4.7-SNAPSHOT built on my local used in the project(commit - #e34415.)
Tomcat Server
Following the recommended way of creating a war, I 've created the application war(in my case <finalName>vaadinjavanine</finalName>) using the command:
mvn package
Made sure that the CATALINA_HOME/webapps included this file. Copied it basically.
Started tomcat on the default port to access the url for the application: localhost:8080/vaadinjavanine/
But have ended up finding another issue in the current chain:
Unable to process file module-info.class within a Java9 project results in ClassFormatException
On 20 August 2017
The answer to the question is No.
What I did was, tried out creating a maven based vaadin application from scratch based out of java9, following the getting started guide. Using the following configurations:
apache-tomcat-8.0.22
intelliJ-IDEA 2017.2.2
<vaadin.version>8.1.2</vaadin.version>
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T01:09:06+05:30)
Maven home: /usr/local/Cellar/maven/3.5.0/libexec
Java version: 9, vendor: Oracle Corporation (jdk-9+181)
Created a maven module using the vaadin-archetype-application as shared in the guide shared. Updated
pom.xml with
<maven.compiler.source>1.9</maven.compiler.source>
<maven.compiler.target>1.9</maven.compiler.target>
Added a module-info.java to the module under development.
I was able to execute mvn package on the same but running mvn jetty:run to run the application ended up achieving MultiException | java.lang.RuntimeException: Error scanning UI and Servlet class
Related
I have the following error during my generator development.
I tried several times to refresh my workspace but it'd not worked.
org.osgi.framework.BundleException: Could not resolve module:
org.artop.ecuc.gautosar.accessors.check [72]
org.osgi.framework.BundleException: Could not resolve module:
org.eclipse.emf.mwe2.language [123]
org.osgi.framework.BundleException: Could not resolve module:
org.eclipse.sphinx.emf.check [151]
org.osgi.framework.BundleException: Could not resolve module:
org.eclipse.sphinx.emf.mwe.dynamic [152]
org.osgi.framework.BundleException: Could not resolve module:
org.eclipse.xtend.core [168]
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.xtext.common.types [173]
org.osgi.framework.BundleException: Could not resolve module:
org.eclipse.xtext.xbase.testing
The messages were not meaningful enough for me to resolve the issue.
It looked like it was the version problem.
Anyone can help?
I checked throughout all plugins and I believed that they have been installed.
If your Eclipse environment doesn't have these kinds of plugins installed, you should check for installation.
In my case, the problem had come from my workspace.
I wiped out all data and make it again.
And after the new workspace finished to build, my application worked well. I think due to run-time exception of javaw (JRE), some plugins were broken, but just my guess.
I have used seedstack dependecies for Hibernate and JPA to create DAO services that performs crud operations on Database.
I am trying to Launch this Seedstack application module through Java application Launcher in eclipse, by SeedMain class.
In pom.xml - dependecy for undertow is given.
<dependency>
<groupId>org.seedstack.seed</groupId>
<artifactId>seed-web-undertow</artifactId>
</dependency>
When executing the SeedMain class, I am getting the below error snakeyaml error:-
Exception in thread "main" java.lang.NoSuchMethodError: org.yaml.snakeyaml.DumperOptions.setSplitLines(Z)V
at com.fasterxml.jackson.dataformat.yaml.YAMLGenerator.buildDumperOptions(YAMLGenerator.java:259)
at com.fasterxml.jackson.dataformat.yaml.YAMLGenerator.<init>(YAMLGenerator.java:232)
at com.fasterxml.jackson.dataformat.yaml.YAMLFactory._createGenerator(YAMLFactory.java:447)
at com.fasterxml.jackson.dataformat.yaml.YAMLFactory.createGenerator(YAMLFactory.java:397)
at org.seedstack.seed.core.internal.diagnostic.DefaultDiagnosticReporter.writeDiagnosticReport(DefaultDiagnosticReporter.java:75)
at org.seedstack.seed.core.internal.diagnostic.DefaultDiagnosticReporter.writeDiagnosticReport(DefaultDiagnosticReporter.java:67)
at org.seedstack.seed.core.internal.diagnostic.DiagnosticManagerImpl.dumpDiagnosticReport(DiagnosticManagerImpl.java:70)
at org.seedstack.seed.core.SeedMain.handleException(SeedMain.java:68)
at org.seedstack.seed.core.SeedMain.main(SeedMain.java:61)
As per my understanding the Error is due to some version inconsistency for snakeyaml, But for Seedstack as the versions for dependecies are resolved by seedstack-bom dependecy, so where exactly should I do the changes to resolve the error.
Thanks in Advance!
From reading the stacktrace, it seems that you have some error on startup which is handled by the handleException() method. This method then tries to write a YAML diagnostic report but ultimately fails due to the snakeyaml version issue you mentioned.
You should do two things:
Fix the snakeyaml dependency issue by looking into the dependency tree. This kind of problem is often caused by some library that makes Maven choose an older version. SeedStack needs at least jackson-dataformat-yaml version 2.9.4 which in turn needs at least snakeyaml 1.18.
Fix the other error by looking at the full stacktrace. When a diagnostic report cannot be written, the original exception is still printed on the console (on stderr).
I'm using SBT 0.13.2-M3 for Lift 2.6-M2 development. I'm also using sbt-escalante 0.2.0 which allows me to start a different application server than Jetty. Now I tried to integrate JRebel 5.2.2 to avoid application restarts. When I run escalante-run I get a lot of JRebel exceptions and the JBoss application server starts but there's no class reloading.
There are so many exceptions that I just list two of them and hope someone has a clue how to fix it.
JRebel: Class 'org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex' could not be processed by org.zeroturnaround.javarebel.jboss7.cbp.DeploymentReflectionIndexCBP#sbt.PluginManagement$PluginClassLoader#411f8c70
2014-03-27 23:02:40 JRebel: ERROR org.zeroturnaround.bundled.javassist.NotFoundException: org.zeroturnaround.javarebel.jboss7.JrDeploymentReflectionIndex
at org.zeroturnaround.bundled.javassist.ClassPool.get(JRebel:450)
at org.zeroturnaround.javarebel.jboss7.cbp.DeploymentReflectionIndexCBP.process(DeploymentReflectionIndexCBP.java:22)
at org.zeroturnaround.javarebel.integration.support.JavassistClassBytecodeProcessor.process(JRebel:70)
at com.zeroturnaround.javarebel.xB.a(JRebel:257)
at com.zeroturnaround.javarebel.xB.a(JRebel:246)
at com.zeroturnaround.javarebel.xB.a(JRebel:224)
at com.zeroturnaround.javarebel.SDKIntegrationImpl.runBytecodeProcessors(JRebel:128)
at com.zeroturnaround.javarebel.xl.transform(JRebel:45)
at java.lang.ClassLoader.defineClass(ClassLoader.java)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327)
JRebel: Class 'org.jboss.as.web.deployment.component.WebComponentInstantiator$1' could not be processed by org.zeroturnaround.javarebel.jboss7.as.cbp.web.WebComponentInstantiator$1CBP#sbt.PluginManagement$PluginClassLoader#411f8c70
2014-03-27 23:02:48 JRebel: ERROR org.zeroturnaround.bundled.javassist.NotFoundException: org.zeroturnaround.javarebel.jboss7.as.contracts.JrServletReinjector
at org.zeroturnaround.bundled.javassist.ClassPool.get(JRebel:450)
at org.zeroturnaround.javarebel.jboss7.as.cbp.web.WebComponentInstantiator$1CBP.process(WebComponentInstantiator$1CBP.java:31)
at org.zeroturnaround.javarebel.integration.support.JavassistClassBytecodeProcessor.process(JRebel:70)
at com.zeroturnaround.javarebel.xB.a(JRebel:257)
at com.zeroturnaround.javarebel.xB.a(JRebel:246)
at com.zeroturnaround.javarebel.xB.a(JRebel:224)
at com.zeroturnaround.javarebel.SDKIntegrationImpl.runBytecodeProcessors(JRebel:128)
at com.zeroturnaround.javarebel.xl.transform(JRebel:45)
I am trying to use eclipse's CDT for generating an AST for some cpp files. I am following the instructions given here: http://wiki.eclipse.org/images/c/c7/CDT_APIs_for_code_introspection.pdf
However, I ran into an error saying:
Exception in thread "main" java.lang.IllegalStateException: Workspace is closed.
at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:399)
at etl.CppParser.Parser(CppParser.java:23)**
After googling about it for a while, I understood that in order to access a project in the workspace (using ResourcesPlugin.getWorkspace().getRoot().getFile(path);), the project should be a plugin project, but my project was a simple Java project.
Therefore, I started to developed a plugin project in eclipse. I created a target platform to which I added all the required plugin dependencies required for my project. But I still have a problem when I run the plugin project as an Eclipse application. Here is the exact error:
!ENTRY org.eclipse.cdt.launch.remote 4 0 2013-11-30 01:43:27.379
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.cdt.launch.remote [300]
Unresolved requirement: osgi.wiring.bundle; filter:="(&(osgi.wiring.bundle=org.eclipse.rse.ui)(&(bundle-version>=3.0.0)(!(bundle-version>=4.0.0))))"
at org.eclipse.osgi.container.Module.start(Module.java:424)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1509)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: org.osgi.service.resolver.ResolutionException: Unable to resolve osgi.identity; osgi.identity="org.eclipse.cdt.launch.remote"; type="osgi.bundle"; version:Version="2.4.0.201309180223"; singleton:="true": missing requirement osgi.wiring.bundle; filter:="(&(osgi.wiring.bundle=org.eclipse.rse.ui)(&(bundle-version>=3.0.0)(!(bundle-version>=4.0.0))))"
at org.apache.felix.resolver.Candidates.populateResource(Candidates.java:285)
at org.apache.felix.resolver.Candidates.populate(Candidates.java:153)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:147)
at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
at org.eclipse.osgi.container.Module.start(Module.java:406)
... 7 more
Root exception:
org.osgi.service.resolver.ResolutionException: Unable to resolve osgi.identity; osgi.identity="org.eclipse.cdt.launch.remote"; type="osgi.bundle"; version:Version="2.4.0.201309180223"; singleton:="true": missing requirement osgi.wiring.bundle; filter:="(&(osgi.wiring.bundle=org.eclipse.rse.ui)(&(bundle-version>=3.0.0)(!(bundle-version>=4.0.0))))"
at org.apache.felix.resolver.Candidates.populateResource(Candidates.java:285)
at org.apache.felix.resolver.Candidates.populate(Candidates.java:153)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:147)
at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
at org.eclipse.osgi.container.Module.start(Module.java:406)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1509)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Could someone please tell me what I could do to get rid of this problem... I am not able to understand what the problem is at this point.
Thank you very much for any help.
Okay, I have solved the problem myself. What I did is as follows: I found this link for Target Management related Downloads and I downloaded the RSE runtime 3.2.2 (it is >=3 and <4)
http://download.eclipse.org/tm/downloads/
Then I went to Eclipse Windows->Preferences->Plugin Development->Target Platform , then selected my Target Platform->Edit-> Add->Directory and add the directory obtained by extracting the downloaded RSE runtime 3.2.2.zip.
After this, when I ran my plug in project as an Eclipse Application, I had no errors anymore because now, the plugins used by my plugin project do not have any unresolved dependencies.
I hope this helps someone.
The error says that bundle org.eclipse.cdt.launch.remote has a Require-Bundle (osgi.wiring.bundle) statement which lists bundle org.eclipse.rse.ui and the bundle version range [3.0,4.0). So org.eclipse.cdt.launch.remote cannot resolve because it is dependent on bundle org.eclipse.rse.ui having bundle version >=3 and < 4.
I'm using RAD 8.0.4 version. After installing plugins like SVN, Maven and PMD, when I try to open 'Deployment Assembly' option for any EAR project(right click->properties->deployment assembly) its showing that "The currently displayed page contains invalid values".
Can anyone help me out to solve this..??
I met the same issue, and the log in .metadata/log like this:
!ENTRY org.eclipse.jface 4 2 2012-11-23 11:37:45.031
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NoSuchMethodError: org/eclipse/jst/j2ee/componentcore/J2EEModuleVirtualComponent.getDefaultDeploymentDescriptorFolder(Lorg/eclipse/wst/common/componentcore/resources/IVirtualFolder;)Lorg/eclipse/core/runtime/IPath;
I had this same issue. It was because I didn't have all projects being referenced, in my workspace. To fix the issue, I had to remove the references. To do that, I had to open the referenced projects first, then open the deployment assembly, and remove the reference.