I upgraded the eclipse plugin to 2.1.1 yesterday I now I get this error each time I try to compile any widgets:
Starting GWT compiler
Unknown argument: -war
Google Web Toolkit 2.3.0
And 2.0.1 doesn’t seem to be available for download anymore, so Eclipse can’t revert back to it:
No repository found containing: org.eclipse.update.feature,com.vaadin.integration.eclipse,2.0.1.201105170102
Thankfully I had a not-so-old tarball of the eclipse installation to fix my IDE again.
I have the same problem!
You could try the latest experimental version of the plugin from the update site http://vaadin.com/eclipse/experimental .
Note that you need to uncheck the “Group items by category” at the moment when using the experimental site to see the available features. Only the main feature should be installed (it also contains the visual designer) unless upgrading from a very old version with a separate visual designer plugin.
If the latest experimental plugin does not work, please
create a ticket
including details about the plugin version used, the Vaadin version used in the project etc.
I want to know, why there is no way of downgrading the eclipse plugin? Now I am stuck with broken plugin and can’t “reverse” back to working one (tried both normal and experimental 2.2 and both are broken with regards to widgetset compilation).
There is no update site with metadata for older plugin versions even though the plugin and feature JARs still exist on the site, so no easy way to downgrade. At the moment the experimental site is practically identical to the main site.
What Vaadin version and GWT version are you using in the project? Do you get the message about “-war” not supported or some other problem? Any other information about how it does not work, what kind of project configuration you have etc?
The thing is, it works on some projects, does not work on others.
One project works fine, other is saying the error about -war and yet another project is throwing IllegalArgumentException:
java.lang.IllegalArgumentException: Attempted to beginRule: MultiRule[P/operaty-ui,P/.org.eclipse.jdt.core.external.folders]
, does not match outer scope rule: P/operaty-ui
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:286)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:118)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2282)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2339)
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:793)
at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3102)
at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3064)
at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3117)
at com.vaadin.integration.eclipse.util.ProjectDependencyManager.updateGWTLibraries(ProjectDependencyManager.java:475)
at com.vaadin.integration.eclipse.util.ProjectDependencyManager.ensureGWTLibraries(ProjectDependencyManager.java:342)
at com.vaadin.integration.eclipse.util.WidgetsetUtil.compileWidgetset(WidgetsetUtil.java:126)
at com.vaadin.integration.eclipse.builder.WidgetsetBuildManager.compileWidgetsetIfNotRunning(WidgetsetBuildManager.java:579)
at com.vaadin.integration.eclipse.builder.WidgetsetBuildManager.compileWidgetset(WidgetsetBuildManager.java:642)
at com.vaadin.integration.eclipse.handlers.CompileWidgetsetHandler.compileFile(CompileWidgetsetHandler.java:152)
at com.vaadin.integration.eclipse.handlers.CompileWidgetsetHandler$1.run(CompileWidgetsetHandler.java:64)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
eclipse.buildId=3.3.0.201307092139-RELEASE-e38
java.version=1.6.0_37
java.vendor=Sun Microsystems Inc.
Vaadin: 6.8.7
GWT:
<gwt.version>2.3.0</gwt.version>
<gwt.plugin.version>2.3.0-1</gwt.plugin.version>
Here is -war log:
Executing compiler with command line:
C:\Program Files\Java\jdk1.6.0_37\bin\java.exe -Djava.awt.headless=true -Xss8M -Xmx512M -XX:MaxPermSize=512M -classpath C:\Program Files\Java\jdk1.6.0_37\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\dnsns.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\jmagick.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\localedata.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\sunjce_provider.jar;C:/Users/Peter/Documents/bach-dataframe/vaadin-addons/src/main/java;C:/Users/Peter/Documents/bach-dataframe/vaadin-addons/src/test/java;C:/Users/Peter/Documents/bach-dataframe/vaadin-addons/target/classes;C:/Users/Peter/Documents/bach-dataframe/vaadin-addons/target/test-classes;C:/Users/Peter/Desktop/STS/springsource/sts-3.1.0.RELEASE/configuration/com.vaadin.integration.eclipse/download/gwt-dev/2.3.0/gwt-dev.jar;C:/Users/Peter/.m2/repository/com/google/gwt/gwt-user/2.3.0/gwt-user-2.3.0.jar;C:/Users/Peter/.m2/repository/com/vaadin/vaadin/6.8.7/vaadin-6.8.7.jar;C:/Users/Peter/.m2/repository/org/vaadin/addons/contextmenu/3.1.0/contextmenu-3.1.0.jar;C:/Users/Peter/.m2/repository/org/vaadin/addons/easyuploads/0.5.1/easyuploads-0.5.1.jar -Dgwt.persistentunitcachedir=C:\Users\Peter\AppData\Local\Temp\widgetset_cz.bach.vaadin.addons.widgetset.widgetsetdc2ea9e2-62ac-4d9b-9c18-9ad92275cef8 com.vaadin.tools.WidgetsetCompiler -war src/main/webapp/VAADIN/widgetsets -deploy C:\Users\Peter\AppData\Local\Temp\widgetset_cz.bach.vaadin.addons.widgetset.widgetsetdc2ea9e2-62ac-4d9b-9c18-9ad92275cef8 -extra C:\Users\Peter\AppData\Local\Temp\widgetset_cz.bach.vaadin.addons.widgetset.widgetsetdc2ea9e2-62ac-4d9b-9c18-9ad92275cef8 -localWorkers 4 -logLevel INFO cz.bach.vaadin.addons.widgetset.widgetset
Updating GWT module description file...
15.7.2013 16:29:16 com.vaadin.terminal.gwt.widgetsetutils.ClassPathExplorer getAvailableWidgetSets
INFO: Widgetsets found from classpath:
com.vaadin.terminal.gwt.DefaultWidgetSet in jar:file:C:/Users/Peter/.m2/repository/com/vaadin/vaadin/6.8.7/vaadin-6.8.7.jar!/
org.vaadin.easyuploads.EasyuploadsWidgetset in jar:file:C:/Users/Peter/.m2/repository/org/vaadin/addons/easyuploads/0.5.1/easyuploads-0.5.1.jar!/
org.vaadin.peter.contextmenu.ContextmenuWidgetset in jar:file:C:/Users/Peter/.m2/repository/org/vaadin/addons/contextmenu/3.1.0/contextmenu-3.1.0.jar!/
cz.bach.vaadin.addons.widgetset.widgetset in file://C/Users/Peter/Documents/bach-dataframe/vaadin-addons/src/main/java
15.7.2013 16:29:16 com.vaadin.terminal.gwt.widgetsetutils.ClassPathExplorer getAvailableWidgetSets
INFO: Search took 6ms
Done.
Starting GWT compiler
Unknown argument: -war
Google Web Toolkit 2.3.0
GWTCompiler [-logLevel level]
[-workDir dir]
[-gen dir]
[-style style]
[-ea]
[-XdisableClassMetadata]
[-XdisableCastChecking]
[-validateOnly]
[-draftCompile]
[-optimize level]
[-compileReport]
[-strict]
[-out dir]
[-localWorkers count]
module[s]
where
-logLevel The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL
-workDir The compiler's working directory for internal use (must be writeable; defaults to a system temp dir)
-gen Debugging: causes normally-transient generated types to be saved in the specified directory
-style Script output style: OBF[USCATED]
, PRETTY, or DETAILED (defaults to OBF)
-ea Debugging: causes the compiled output to check assert statements
-XdisableClassMetadata EXPERIMENTAL: Disables some java.lang.Class methods (e.g. getName())
-XdisableCastChecking EXPERIMENTAL: Disables run-time checking of cast operations
-validateOnly Validate all source code, but do not compile
-draftCompile Enable faster, but less-optimized, compilations
-optimize Sets the optimization level used by the compiler. 0=none 9=maximum.
-compileReport Create a compile report that tells the Story of Your Compile
-strict Only succeed if no input files have errors
-out The directory to write output files into (defaults to current)
-localWorkers The number of local workers to use when compiling permutations
and
module[s]
Specifies the name(s) of the module(s) to compile
Widgetset compilation failed
Vaadin version for the -war error:
6.8.7
GWT:
<gwt.version>2.3.0</gwt.version>
<gwt.plugin.version>2.3.0-1</gwt.plugin.version>
You do not seem to be using the latest Eclipse plug-in at least for the “-war” issue. I would recommend checking what errors (if any) you get with it.
The IllegalArgumentException looks like you have two conflicting versions of Eclipse JDT on your classpath - one from GWT, the other from somewhere else or another copy of a different version of GWT.
Also the “-war” issue looks like a build path issue: there is a newer GWT class on the classpath of the GWT compiler that makes it assume you are using a new GWT version with different parameters to the compiler. It is not obvious to me where that class would be in your case, although I did notice some of your dependencies came from your Maven cache and some (like the gwt-dev) from elsewhere by Eclipse. The detection problem could also be somehow related to one of the add-ons. If you are using Maven, it might be a good idea to also use Maven to compile the widgetset rather than using the Eclipse plugin for that.
In a new Vaadin 6.8.7 project, I did not have any problems with widgetset compilation with the latest plug-in.
Here is the project that works:
Executing compiler with command line:
C:\Program Files\Java\jdk1.6.0_37\bin\java.exe -Djava.awt.headless=true -Xss8M -Xmx512M -XX:MaxPermSize=512M -classpath C:\Program Files\Java\jdk1.6.0_37\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\dnsns.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\jmagick.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\localedata.jar;C:\Program Files\Java\jdk1.6.0_37\jre\lib\ext\sunjce_provider.jar;C:/Users/Peter/Documents/bach-dataframe/foto-ui/src/main/java;C:/Users/Peter/Documents/bach-dataframe/foto-ui/src/main/resources;C:/Users/Peter/Documents/bach-dataframe/foto-ui/src/test/java;C:/Users/Peter/Documents/bach-dataframe/foto-ui/target/classes;C:/Users/Peter/Documents/bach-dataframe/foto-ui/target/test-classes;C:/Users/Peter/Desktop/STS/springsource/sts-3.1.0.RELEASE/configuration/com.vaadin.integration.eclipse/download/gwt-dev/2.3.0/gwt-dev.jar;C:/Users/Peter/Desktop/STS/springsource/sts-3.1.0.RELEASE/configuration/com.vaadin.integration.eclipse/download/gwt-user/2.3.0/gwt-user.jar;C:/Users/Peter/.m2/repository/com/vaadin/vaadin/6.8.7/vaadin-6.8.7.jar;C:/Users/Peter/Desktop/STS/springsource/sts-3.1.0.RELEASE/configuration/com.vaadin.integration.eclipse/download/gwt-dependencies/2.3.0/validation-api-1.0.0.GA-sources.jar;C:/Users/Peter/Desktop/STS/springsource/sts-3.1.0.RELEASE/configuration/com.vaadin.integration.eclipse/download/gwt-dependencies/2.3.0/validation-api-1.0.0.GA.jar;C:/Users/Peter/.m2/repository/org/vaadin/addons/contextmenu/3.1.0/contextmenu-3.1.0.jar;C:/Users/Peter/.m2/repository/org/vaadin/addons/easyuploads/0.5.1/easyuploads-0.5.1.jar com.vaadin.tools.WidgetsetCompiler -out src/main/webapp/VAADIN/widgetsets -localWorkers 4 -logLevel INFO cz.bach.clients.amp.foto.ui.widgetset.widgetset
Updating GWT module description file...
16.7.2013 12:34:08 com.vaadin.terminal.gwt.widgetsetutils.ClassPathExplorer getAvailableWidgetSets
INFO: Widgetsets found from classpath:
com.vaadin.terminal.gwt.DefaultWidgetSet in jar:file:C:/Users/Peter/.m2/repository/com/vaadin/vaadin/6.8.7/vaadin-6.8.7.jar!/
org.vaadin.easyuploads.EasyuploadsWidgetset in jar:file:C:/Users/Peter/.m2/repository/org/vaadin/addons/easyuploads/0.5.1/easyuploads-0.5.1.jar!/
cz.bach.clients.amp.foto.ui.widgetset.widgetset in file://C/Users/Peter/Documents/bach-dataframe/foto-ui/src/main/java
org.vaadin.peter.contextmenu.ContextmenuWidgetset in jar:file:C:/Users/Peter/.m2/repository/org/vaadin/addons/contextmenu/3.1.0/contextmenu-3.1.0.jar!/
16.7.2013 12:34:08 com.vaadin.terminal.gwt.widgetsetutils.ClassPathExplorer getAvailableWidgetSets
INFO: Search took 6ms
Done.
Starting GWT compiler
Compiling module cz.bach.clients.amp.foto.ui.widgetset.widgetset
Scanning for additional dependencies: jar:file:/C:/Users/Peter/.m2/repository/com/vaadin/vaadin/6.8.7/vaadin-6.8.7.jar!/com/vaadin/terminal/gwt/client/WidgetSet.java
Computing all possible rebind results for 'com.vaadin.terminal.gwt.client.WidgetMap'
Rebinding com.vaadin.terminal.gwt.client.WidgetMap
Invoking generator com.vaadin.terminal.gwt.widgetsetutils.EagerWidgetMapGenerator
Detecting Vaadin components in classpath to generate WidgetMapImpl.java ...
16.7.2013 12:34:27 com.vaadin.terminal.gwt.widgetsetutils.ClassPathExplorer getPaintablesHavingWidgetAnnotation
INFO: Searching for paintables..
16.7.2013 12:34:28 com.vaadin.terminal.gwt.widgetsetutils.ClassPathExplorer getPaintablesHavingWidgetAnnotation
INFO: Search took 744ms
Widget set will contain implementations for following components:
com.vaadin.ui.AbsoluteLayout
com.vaadin.ui.Accordion
com.vaadin.ui.Audio
com.vaadin.ui.Button
com.vaadin.ui.CheckBox
com.vaadin.ui.ComboBox
com.vaadin.ui.CssLayout
com.vaadin.ui.CustomComponent
com.vaadin.ui.CustomLayout
com.vaadin.ui.DateField
com.vaadin.ui.DragAndDropWrapper
com.vaadin.ui.Embedded
com.vaadin.ui.Form
com.vaadin.ui.FormLayout
com.vaadin.ui.GridLayout
com.vaadin.ui.HorizontalLayout
com.vaadin.ui.HorizontalSplitPanel
com.vaadin.ui.InlineDateField
com.vaadin.ui.Label
com.vaadin.ui.Link
com.vaadin.ui.ListSelect
com.vaadin.ui.MenuBar
com.vaadin.ui.NativeButton
com.vaadin.ui.NativeSelect
com.vaadin.ui.OptionGroup
com.vaadin.ui.OrderedLayout
com.vaadin.ui.Panel
com.vaadin.ui.PasswordField
com.vaadin.ui.PopupView
com.vaadin.ui.ProgressIndicator
com.vaadin.ui.RichTextArea
com.vaadin.ui.Select
com.vaadin.ui.Slider
com.vaadin.ui.SplitPanel
com.vaadin.ui.TabSheet
com.vaadin.ui.Table
com.vaadin.ui.TextArea
com.vaadin.ui.TextField
com.vaadin.ui.Tree
com.vaadin.ui.TreeTable
com.vaadin.ui.TwinColSelect
com.vaadin.ui.Upload
com.vaadin.ui.UriFragmentUtility
com.vaadin.ui.VerticalLayout
com.vaadin.ui.VerticalSplitPanel
com.vaadin.ui.Video
com.vaadin.ui.Window
org.vaadin.easyuploads.MultiUpload
org.vaadin.peter.contextmenu.ContextMenu
Done. (0seconds)
/snip
same workspace, same vaadin eclipse plugin, same gwt in pom
In the one that works, the gwt-user JAR is managed by the Eclipse plugin whereas in the other project it is used from the Maven cache. Also some (optional) dependencies of gwt-user are only included in the one that works.
Check your Eclipse project build path for gwt-user and whether your pom explicitly includes gwt-user . Vaadin Eclipse plug-in does not try to manage GWT JARs at least if some are found configured explicitly on the project build path.
Here is my pom for the -war problem project:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>cz.bach.vaadin</groupId>
<artifactId>vaadin-addons</artifactId>
<packaging>jar</packaging>
<version>1.0</version>
<properties>
<maven.build.timestamp.format>yyMMdd</maven.build.timestamp.format>
<ui-version>${maven.build.timestamp}</ui-version>
<uiframe-version>1.0.22</uiframe-version>
<commons-locations-version>0.0.1-SNAPSHOT</commons-locations-version>
<aspectj.version>1.7.2</aspectj.version>
<java.version>6</java.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<slf4j.version>1.7.1</slf4j.version>
<spring.version>3.1.1.RELEASE</spring.version>
<gwt.version>2.3.0</gwt.version>
<gwt.plugin.version>2.3.0-1</gwt.plugin.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>${gwt.plugin.version}</version>
<configuration>
<webappDirectory>${project.build.directory}/${project.build.finalName}/VAADIN/widgetsets</webappDirectory>
<extraJvmArgs>-Xmx512M -Xss1024k</extraJvmArgs>
<runTarget>vaadin-addons</runTarget>
<hostedWebapp>${project.build.directory}/${project.build.finalName}</hostedWebapp>
<noServer>true</noServer>
<port>8080</port>
<compileReport>false</compileReport>
</configuration>
<executions>
<execution>
<goals>
<goal>resources</goal>
<goal>compile</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>${gwt.version}</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-dev</artifactId>
<version>${gwt.version}</version>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>${gwt.version}</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-maven-plugin</artifactId>
<version>1.0.2</version>
<executions>
<execution>
<configuration>
</configuration>
<goals>
<goal>update-widgetset</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<repositories>
<repository>
<id>vaadin-snapshots</id>
<url>http://oss.sonatype.org/content/repositories/vaadin-snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>vaadin-addons</id>
<url>http://maven.vaadin.com/vaadin-addons</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>${gwt.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
<!-- UIFRAME -->
<dependency>
<groupId>cz.bach.archives.uiframe</groupId>
<artifactId>uiframe</artifactId>
<version>${uiframe-version}</version>
</dependency>
</dependencies>
</project>
so I do explicitedly include it, since I need it otherwise there would be errors in new wigets I want to make.
Funny thing is, if I remove that gwt user dependency and then attempt (with errors) to compile widgetset, I get that same old Illegal Access Exception:
!ENTRY org.eclipse.jdt.core 4 4 2013-07-16 16:45:03.451
!MESSAGE Exception occurred in listener of Java element change notification
!STACK 0
java.lang.NoSuchMethodError: org.springsource.ide.eclipse.commons.core.SpringCoreUtils.buildProject(Lorg/eclipse/core/resources/IProject;Ljava/lang/String;)V
at org.springframework.ide.eclipse.core.internal.model.SpringModel$ClasspathChangedListener.elementChanged(SpringModel.java:341)
at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672)
at org.eclipse.jdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1506)
at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1482)
at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:2094)
at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:156)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
which is immediatelly gone when I return that dependency back… I am totally lost here what to do.
I should have same java everywhere (1.6 jdk) and build paths look fine…
Okay, after I figured out that it takes gwt user from repo and gwt dev from eclipse, I put gwt into dependencies and let it compile it with maven one (so they are same). But that thing is figting me like a devil. It requires validation-api-1.0.0.GA but I simply CANT PUT IT ANYWHERE to satisfy it. If it is in pom, nada, not included in -classpath argument to java, if it is in referenced build path, again nothing.
The only thing that works is to unzip the validation-api and put it in my project… wtf…
What I dont get is why do I get that beginRule exception if I dont provide any gwt via maven but I dont if I do provide them. And also why it does not include validation jar but does everything else…