vaadin-framework

19189 İşlemeler

Dal: master

Yazar	SHA1	Mesaj	Tarih
Denis	65220e4794	chore: avoid repackaging of google elemental dep and use it directly (#12416) * chore: avoid repackaging of google elemental dep and use it directly The google elemental dependency is not OSGi compatible so it's repackaged into shared module to use it directly from there. But there is a custom Vaadin version of google elemental dep and it's OSGi compatible. Flow uses this version and to be able to use FW in MPR the versions should match. So the Vaadin google elemental dep is added instead of repackaging. * chore: import elemental package in the bnd file	2 yıl önce
Ahmed Ashour	829c9d7256	Fix bnd warnings	6 yıl önce
Henri Sara	e788fa906b	Rename OSGi classes for Java naming conventions (#9320) - Rename OSGi to Osgi in class names. - Rename VaadinOSGiPortlet to OSGiVaadinPortlet for consistency with Spring, CDI etc. add-ons - Add missing javadoc	7 yıl önce
Ilia Motornyi	d0a64a8049	Fixes repackaging the whole elemental into shared. (#9207)	7 yıl önce
Henri Sara	df060e265a	Add missing fields to OSGi manifests Adds RequiredExecutionEnvironment and License fields and renames some bundles (SymbolicName) for backwards compatibility.	7 yıl önce
Mirjan Merruko	9a6ebeb5a8	Add OSGi support #8830 #8827 #8828 #8829 Use bnd-maven-plugin instead of maven-bundle-plugin and helper class, and add support for publishing static resources such as themes and widgetsets.	7 yıl önce