1 <?xml version="1.0" encoding="utf-8"?>
2 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
3 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
5 <modelVersion>4.0.0</modelVersion>
7 <groupId>org.vaadin.addons</groupId>
8 <artifactId>console</artifactId>
9 <version>1.2.0-SNAPSHOT</version>
10 <packaging>jar</packaging>
11 <name>Vaadin Console add-on</name>
16 <artifactId>maven-source-plugin</artifactId>
22 <phase>generate-sources</phase>
30 <groupId>org.apache.maven.plugins</groupId>
31 <artifactId>maven-compiler-plugin</artifactId>
39 <groupId>org.apache.maven.plugins</groupId>
40 <artifactId>maven-jar-plugin</artifactId>
41 <version>2.3.1</version>
46 <addClasspath>true</addClasspath>
48 Implementation-Title and Implementation-Version come from the
51 <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
54 <!-- Package format version - do not change -->
55 <Vaadin-Package-Version>1</Vaadin-Package-Version>
57 <!-- Add-on specific fields to update -->
58 <Vaadin-License-Title>Apache License 2.0</Vaadin-License-Title>
61 Implementation-Title and Implementation-Version come from the
64 <Implementation-Vendor>Vaadin Ltd</Implementation-Vendor>
65 <Implementation-Title>${pom.name}</Implementation-Title>
66 <Implementation-Version>${pom.version}</Implementation-Version>
68 <!-- Comma-separated list of widgetsets in the package -->
69 <Vaadin-Widgetsets>org.vaadin.console.ConsoleWidgetset</Vaadin-Widgetsets>
75 <!-- Compiles your custom GWT components with the GWT compiler -->
77 A hosted mode browser for client-side widget debugging can be run
78 with the goal gwt:run after uncommenting the correct line below. A
79 remote debugger can then be connected to port 8998. Note that e.g. a
80 Jetty server should be running with the server side parts - use the
84 <groupId>org.codehaus.mojo</groupId>
85 <artifactId>gwt-maven-plugin</artifactId>
86 <version>2.2.0</version>
88 <!-- if you don't specify any modules, the plugin will find them -->
89 <webappDirectory>${project.build.directory}/${project.build.finalName}/VAADIN/widgetsets</webappDirectory>
90 <!-- On Mac running Snow Leopard, add "-d32" -->
92 This causes error messages (but build works) in phase "package":
93 two processes would use the same debug port
96 extraJvmArgs>-Xmx512M -Xss1024k -Xdebug
97 -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8998</extraJvmArgs
99 <extraJvmArgs>-Xmx512M -Xss1024k</extraJvmArgs>
100 <runTarget>xsite</runTarget>
101 <hostedWebapp>${project.build.directory}/${project.build.finalName}</hostedWebapp>
102 <noServer>true</noServer>
109 <goal>resources</goal>
118 This is needed for the sources required by the GWT compiler to be
119 included in the produced JARs
123 <directory>src/main/java</directory>
126 <directory>src/main/resources</directory>
133 <id>updateWidgetset</id>
137 <groupId>com.vaadin</groupId>
138 <artifactId>vaadin-maven-plugin</artifactId>
139 <version>1.0.2</version>
145 <goal>update-widgetset</goal>
157 <groupId>com.vaadin</groupId>
158 <artifactId>vaadin</artifactId>
159 <version>6.6.0</version>
162 <groupId>org.vaadin.addons</groupId>
163 <artifactId>widget-rpc</artifactId>
164 <version>1.1.3</version>
167 <groupId>com.google.gwt</groupId>
168 <artifactId>gwt-user</artifactId>
169 <version>2.2.0</version>
170 <scope>provided</scope>
177 <url>http://oss.sonatype.org/content/repositories/vaadin/</url>
179 <enabled>true</enabled>
182 <enabled>false</enabled>
186 <id>vaadin-addons</id>
187 <url>http://maven.vaadin.com/vaadin-addons</url>
189 <enabled>true</enabled>
192 <enabled>false</enabled>