release Version 1.0.2

andreashuthe · Oct 13, 2017 · deb41d7 · deb41d7
1 parent 9cd769e
commit deb41d7
Show file tree

Hide file tree

Showing 7 changed files with 8 additions and 8 deletions.
diff --git a/README.md b/README.md
@@ -57,13 +57,13 @@ If you have not already compiled the widgetset, do it now by running vaadin:inst
 
 If you have a JRebel license, it makes on the fly code changes faster. Just add JRebel nature to your date-time-fields-demo project by clicking project with right mouse button and choosing JRebel > Add JRebel Nature
 
-To debug project and make code modifications on the fly in the server-side, right-click the date-time-fields-demo project and choose Debug As > Debug on Server. Navigate to http://localhost:8080/joda-time-fields-demo/ to see the application.
+To debug project and make code modifications on the fly in the server-side, right-click the date-time-fields-demo project and choose Debug As > Debug on Server. Navigate to http://localhost:8888/joda-time-fields-demo/ to see the application.
 
 ### Debugging client-side
 
 The most common way of debugging and making changes to the client-side code is dev-mode. To create debug configuration for it, open date-time-fields-demo project properties and click "Create Development Mode Launch" button on the Vaadin tab. Right-click newly added "GWT development mode for date-time-fields-demo.launch" and choose Debug As > Debug Configurations... Open up Classpath tab for the development mode configuration and choose User Entries. Click Advanced... and select Add Folders. Choose Java and Resources under joda-time-fields/src/main and click ok. Now you are ready to start debugging the client-side code by clicking debug. Click Launch Default Browser button in the GWT Development Mode in the launched application. Now you can modify and breakpoints to client-side classes and see changes by reloading the web page. 
 
-Another way of debugging client-side is superdev mode. To enable it, uncomment devModeRedirectEnabled line from the end of DemoWidgetSet.gwt.xml located under joda-time-fields-demo resources folder and compile the widgetset once by running vaadin:compile Maven target for date-time-fields-demo. Refresh date-time-fields-demo project resources by right clicking the project and choosing Refresh. Click "Create SuperDevMode Launch" button on the Vaadin tab of the date-time-fields-demo project properties panel to create superder mode code server launch configuration and modify the class path as instructed above. After starting the code server by running SuperDevMode launch as Java application, you can navigate to http://localhost:8080/date-time-fields-demo/?superdevmode. Now all code changes you do to your client side will get compiled as soon as you reload the web page. You can also access Java-sources and set breakpoints inside Chrome if you enable source maps from inspector settings. 
+Another way of debugging client-side is superdev mode. To enable it, uncomment devModeRedirectEnabled line from the end of DemoWidgetSet.gwt.xml located under joda-time-fields-demo resources folder and compile the widgetset once by running vaadin:compile Maven target for date-time-fields-demo. Refresh date-time-fields-demo project resources by right clicking the project and choosing Refresh. Click "Create SuperDevMode Launch" button on the Vaadin tab of the date-time-fields-demo project properties panel to create superder mode code server launch configuration and modify the class path as instructed above. After starting the code server by running SuperDevMode launch as Java application, you can navigate to http://localhost:8888/date-time-fields-demo/?superdevmode. Now all code changes you do to your client side will get compiled as soon as you reload the web page. You can also access Java-sources and set breakpoints inside Chrome if you enable source maps from inspector settings. 
 
 ## Issue tracking
 

diff --git a/date-time-fields-demo-eventbus/pom.xml b/date-time-fields-demo-eventbus/pom.xml
@@ -5,7 +5,7 @@
     <parent>
         <artifactId>date-time-fields-root</artifactId>
         <groupId>org.vaadin</groupId>
-        <version>1.0.1</version>
+        <version>1.0.2</version>
     </parent>
     <modelVersion>4.0.0</modelVersion>
 

diff --git a/date-time-fields-demo-mvp-vaadin/pom.xml b/date-time-fields-demo-mvp-vaadin/pom.xml
@@ -5,7 +5,7 @@
     <parent>
         <artifactId>date-time-fields-root</artifactId>
         <groupId>org.vaadin</groupId>
-        <version>1.0.1</version>
+        <version>1.0.2</version>
     </parent>
     <modelVersion>4.0.0</modelVersion>
 

diff --git a/date-time-fields-demo-mvp/pom.xml b/date-time-fields-demo-mvp/pom.xml
@@ -5,7 +5,7 @@
     <parent>
         <artifactId>date-time-fields-root</artifactId>
         <groupId>org.vaadin</groupId>
-        <version>1.0.1</version>
+        <version>1.0.2</version>
     </parent>
     <modelVersion>4.0.0</modelVersion>
 

diff --git a/date-time-fields-demo/pom.xml b/date-time-fields-demo/pom.xml
@@ -5,7 +5,7 @@
 	<groupId>org.vaadin</groupId>
 	<artifactId>date-time-fields-demo</artifactId>
 	<packaging>war</packaging>
-	<version>1.0.1</version>
+	<version>1.0.2</version>
 	<name>date-time-fields Add-on Demo</name>
 
 	<properties>

diff --git a/date-time-fields/pom.xml b/date-time-fields/pom.xml
@@ -4,7 +4,7 @@
 	<groupId>org.vaadin</groupId>
 	<artifactId>date-time-fields</artifactId>
 	<packaging>jar</packaging>
-	<version>1.0.1</version>
+	<version>1.0.2</version>
 	<name>date-time-fields Add-on</name>
 
 	<properties>

diff --git a/pom.xml b/pom.xml
@@ -5,7 +5,7 @@
 	<groupId>org.vaadin</groupId>
 	<artifactId>date-time-fields-root</artifactId>
 	<packaging>pom</packaging>
-	<version>1.0.1</version>
+	<version>1.0.2</version>
 	<name>date-time-fields Add-on Root Project</name>
 
 	<modules>