vaadin-framework

Tree: f7279f7330

Author	SHA1	Message	Date
Ilia Motornyi	f7279f7330	Update Copyright headers for year 2018 (#10762)	6 years ago
Artur Signell	c5c52684eb	Format Java files using Eclipse Neon and Vaadin settings Using the same formatting in the 7.7 branch and the master branch eases porting of fixes Change-Id: I51b4693f2f120447702cf322ce4505608ad92987	7 years ago
elmot	521ec24c62	Build client-compiler with maven Change-Id: Ic86a95ce44cc37c8d34d607b39f2aec4cc922ce2	8 years ago
Teppo Kurki	3ecc805eff	Fixed CvalChecker invalid version message (#17879) Change-Id: I2eed6d907be299ebca3e69d7f492aff6f1244fe4	9 years ago
Artur Signell	32a5d8f382	Reformat project using Eclipse Luna SR1 Change-Id: I58748499c87d470e70304d882d3227cda5803481	9 years ago
Jonatan Kronqvist	272711e6f7	Fix the license checker after elemental.json #15383 The elemental.json update changed how null values and string representations of numbers were parsed, which caused a lot of tests for CvalChecker to fail. Unfortunately the tests were never run in an automated fashion, which means that they were never discovered until we stumbled upon it due to the issue reported in #15383 Change-Id: If2cb9fa96effea7ce55a4ffe6d1666ca7521e1fb	9 years ago
Jonatan Kronqvist	fba69ae5d8	Allow for multiple license keys in a single license file #14408 License files can now contain multiple keys to support different versions of a product. The keys are identified by the major version number followed by an equals sign and the key for that version, e.g. 1 = foo-bar-baz 2 = baz-foo-bar The license file can also contain a "default" license key, which is used for all versions except for the explicitly defined ones, e.g. foo-bar-baz 3 = baz-bar-foo 4 = bar-baz-baz Change-Id: Id07d22e9fdc44189c4298b634006cf0df128bfd9	9 years ago
Manolo Carrasco	9a84fb14f2	License Checker for vaadin cval products (#13696 #13474) - This patch includes four elements: 1.- A class able to validate a licensed product against Vaadin license server. It can be used in any vaadin product (thought for non addons like TB) just adding vaadin dependency, or copying the class. 2.- A class able to inspect all addons in the classpath and figure out, based on the MANIFEST.MF info, whether we have to check developer license. 3.- A modification to Vaadin connector generator to use the classes above and to stop compilation in case. 4.- A modification to ConnectorBundleLoader, so as when a new connector is instatiated, we check whether it is using an evaluation license and show a notice. We only show the notice once. - In addition to validating developer licenses, the checker caches the server response for using it when there are connection problems. - This stuff is in Vaadin core, so as we dont maintain license code in each addon. For checking an addon license we just add the license type to the manifest when packaging the artefact. - It checks expiration time, product name and major version. Fixes: #13696 In some-way related with: #13474 Change-Id: Ib61b1c2e9c3cacd463a1ce5db02c2cfbc06851c2	10 years ago

3 Commits (f7279f7330a3673e88e97552bb623fc21c2971e9)