lingwei.kong/hawkbit
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

Migration of Action History to vaadin grid (#420)

Browse Source 
* Migration of Action History to vaadin Grid
Signed-off-by: kaizimmerm <kai.zimmermann@bosch-si.com>
This commit is contained in:
Marcel Mager
2017-03-24 14:03:39 +01:00
committed by Kai Zimmermann
parent 081c3cccbf
commit c8db41ff85
65 changed files with 4713 additions and 1585 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
pom.xml
View File

@@ -105,7 +105,7 @@
<snapshotDependencyAllowed>true</snapshotDependencyAllowed>
<!-- Spring boot version overrides (should be reviewed with every boot upgrade) - START -->
<!-- Newer versions needed than defined in Boot -->
<!-- Newer versions needed than defined in Boot -->
<spring-hateoas.version>0.23.0.RELEASE</spring-hateoas.version>
<assertj.version>3.6.2</assertj.version>
<!-- Older versions needed than defined in Boot -->
@@ -152,7 +152,7 @@
<feign.extension.version>9.3.1</feign.extension.version>
<jayway.awaitility.version>1.7.0</jayway.awaitility.version>
<io-protostuff.version>1.5.2</io-protostuff.version>
<!-- Misc libraries versions - END -->
<!-- Release - START -->
@@ -218,7 +218,7 @@
<version>1.4.1</version>
<executions>
<execution>
<!-- Make sure that only non-snapshot versions are used for the dependencies. Only active when property 'snapshotDependencyAllowed' is
<!-- Make sure that only non-snapshot versions are used for the dependencies. Only active when property 'snapshotDependencyAllowed' is
false. -->
<id>enforce-no-snapshots</id>
<goals>
@@ -415,10 +415,10 @@
<build>
<plugins>
<plugin>
<!-- Use the Nexus Staging plugin as a full replacement for the standard Maven Deploy plugin. See https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
why this makes sense :-) We can control whether we want to deploy to the Eclipse repo or Maven Central by a combination of the version being a SNAPSHOT
or RELEASE version and property skipStaging=true/false. In any case we can take advantage of the plugin's "deferred deploy" feature which makes sure that
all artifacts of a multi-module project are deployed as a whole at the end of the build process instead of deploying each module's artifacts individually
<!-- Use the Nexus Staging plugin as a full replacement for the standard Maven Deploy plugin. See https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
why this makes sense :-) We can control whether we want to deploy to the Eclipse repo or Maven Central by a combination of the version being a SNAPSHOT
or RELEASE version and property skipStaging=true/false. In any case we can take advantage of the plugin's "deferred deploy" feature which makes sure that
all artifacts of a multi-module project are deployed as a whole at the end of the build process instead of deploying each module's artifacts individually
as part of building the module. -->
<groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId>
@@ -629,7 +629,7 @@
<artifactId>feign-jaxrs</artifactId>
<version>${feign.extension.version}</version>
</dependency>
<!-- Protostuff Io -->
<dependency>
<groupId>io.protostuff</groupId>
@@ -641,7 +641,7 @@
<artifactId>protostuff-runtime</artifactId>
<version>${io-protostuff.version}</version>
</dependency>
<!-- RSQL / FIQL parser -->
<dependency>
<groupId>cz.jirutka.rsql</groupId>
@@ -740,4 +740,4 @@
</dependency>
</dependencies>
</dependencyManagement>
</project>
</project>