Building a central Go modules repository: GoCenter’s back to the future. @jfrog @ankushchadha111 GopherCon 2019 Lightning Talk Ankush Chadha About me • Dev Manager, Community & Partner Engineering

in the Apache Unomi server. There are two ways to register rules : either by building a custom OSGi bundle plugin or using the REST API to directly send a JSON representation of the rule to be saved. We contains both system properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: contextserver.publicAddress=${org $MY_KARAF_HOME/etc/unomi.custom.system.properties (and create it if you haven’t yet) file: org.osgi.service.http.port.secure=9443 org.osgi.service.http.port=8181 If you change these ports, also make sure you adjust the

contains both system properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: Default values are secured. For each trusted third party server, you need to add these 3 lines : org.osgi.service.http.port.secure=9443 org.osgi.service.http.port=8181 org.apache.unomi.cluster.public.address=http://localhost:8181 following command: And the corresponding rule can be deleted using the following command: INJECT AN OSGI SERVICE IN A GROOVY SCRIPT It’s possible to use the services provided by unomi directly in the groovy

Documenting Kotlin Code Annotation Processing with Kotlin Using Gradle Using Maven Using Ant Kotlin and OSGi Compiler Plugins Code Style Migration Guide Evolution Kotlin Evolution Stability of Different strongly-typed API, you can convert TypeScript definitions from the Definitely Typed type definitions repository to Kotlin using the ts2kt tool. Alternatively, you can use the dynamic type to access any framework side is not supported. A library built from a multiplatform project may be published to a Maven repository with the Gradle maven-publish plugin, which can be applied as follows: plugins { /* ...

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 Spring Data Repository Metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692 18.12.5. Storing the Job Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <repository> spring-snapshots https://repo.spring.io/snapshot true repository>

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 Spring Data Repository Metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692 18.12.6. Storing the Job Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . of the spring-boot-cli-*-bin.zip or spring-boot-cli-*-bin.tar.gz files from the Spring software repository. Once downloaded, follow the INSTALL.txt instructions from the unpacked archive. In summary,

classes * annotation-config registers PersistenceAnnotationBeanPostProcessor independent from client bundle's class loader * added CUSTOM value to FilterType enumeration Package org.springframework.core * provider's ClassLoader (for full visibility in OSGi) * Spring-enriched JPA proxies are created in the application's ClassLoader (making any vendor interfaces work in OSGi) * fixed AbstractEntityManagerFactoryBean's fixed spring-core.jar's manifest to contain correct OSGi Import-Package declaration * removed superfluous DynamicImport-Package declarations from OSGi manifests * all decorator proxies are using identity

classes * annotation-config registers PersistenceAnnotationBeanPostProcessor independent from client bundle's class loader * added CUSTOM value to FilterType enumeration Package org.springframework.core * provider's ClassLoader (for full visibility in OSGi) * Spring-enriched JPA proxies are created in the application's ClassLoader (making any vendor interfaces work in OSGi) * fixed AbstractEntityManagerFactoryBean's fixed spring-core.jar's manifest to contain correct OSGi Import-Package declaration * removed superfluous DynamicImport-Package declarations from OSGi manifests * all decorator proxies are using identity

------------------------------------- * removed INDEX.LIST entries from Spring jar META-INF dirs * fixed OSGi metadata for optional "javax.inject" package import * fixed AbstractResource's InputStream-based "contentLength()" resource type does not have a filename * Resource "contentLength()" implementations work with OSGi bundle resources and JBoss VFS resources * PathMatchingResourcePatternResolver preserves caching for Changes in version 3.1 RC2 (2011-11-28) --------------------------------------- * fixed OSGi manifest for spring-web bundle to not require Apache HttpComponents anymore * fixed GenericTypeResolver to consistently

------------------------------------- * removed INDEX.LIST entries from Spring jar META-INF dirs * fixed OSGi metadata for optional "javax.inject" package import * fixed AbstractResource's InputStream-based "contentLength()" resource type does not have a filename * Resource "contentLength()" implementations work with OSGi bundle resources and JBoss VFS resources * PathMatchingResourcePatternResolver preserves caching for Changes in version 3.1 RC2 (2011-11-28) --------------------------------------- * fixed OSGi manifest for spring-web bundle to not require Apache HttpComponents anymore * fixed GenericTypeResolver to consistently