11 Commits

Author SHA1 Message Date
Ray Milkey
70bd55de56 Upgrade karaf to version 4.2.14
Change-Id: Ibfa72941a01fb8026513d39f5b3d5f2bb3dcc9d2
2022-01-12 16:34:12 +00:00
Matteo Scandolo
cabf6f8427 Bumping onos-maven-plugin version in onos-dependencies
Change-Id: I45a09565196482f057f5e9e0fdc0e926ed2914eb
2021-09-17 16:13:44 +00:00
pierventre
aa263b3f72 [AETHER-966] Upgrade errorprone to 2.3.4
Change-Id: Ibc0e804333b234e9ade3ddb610dbbc30aee3ecd7
2020-11-20 07:59:51 +00:00
Ray Milkey
da74633fb9 Upgrade to apache karaf 4.2.9
Change-Id: Id42b0b0893ee81cb54a50bf6c76da024a9a2d2a8
2020-07-09 07:20:26 +00:00
Daniele Moro
cc41a94599 Add support to propagate ONOS log to Kafka with KafkaAppender in log4j2
- new OSGi Bundle to define extra imports for log4j2
- update OSGiWrapper to support fragment-host tag + bugfix
- add kafka-clients to onos-dependencies package
- add example of how to propagate log to Kafka via KafkaAppender
- bugfix to org.ops4j.pax.logging.cfg

Change-Id: I89992936101a48c6452082bf23c7133c20aa0b48
2020-02-14 19:02:07 +00:00
Ray Milkey
5f5db1fbe3 Upgrade to Apache Karaf 4.2.8
Change-Id: I8ae525e6c8a04c0381c5e3bac39de1a7b85b4446
2020-02-05 04:14:53 +00:00
Carmelo Cascone
e4cf051bd2 Fix mvn checkstyle still failing on autogenerated sources
For some reason the <excludes> tag was ignored. We take a different
approach by forcing checkstyle plugin to consider only the project
source directory

Change-Id: I310d2b5be0f0df8e16b11744d6195db31ee3f35e
2020-01-23 19:54:06 +00:00
Thomas Vachuska
15e5d90bbe Add checkstyle exclusion for generated sources.
Change-Id: I0162e71896a2d2e0b4f3255b8d3b9d3d9dedd07b
2020-01-21 21:12:15 +00:00
Daniele Moro
462547acf8 Fixed bug on generating configuration catalogues
When the OSGi @Component annotation is imported via star import (e.g.,
import org.osgi.service.component.annotations.*), the onos-maven-plugin
does not recognize that and fails to generate the cfgdef file.

Change-Id: I0a0d9c04479e4c27783a37ad3e6245bec1d272a6
2019-12-03 01:24:52 +00:00
Carmelo Cascone
c0e351f8b8 Fix errors when generating javadoc for 3rd-party apps
Because of this bug in Open JDK 11:
https://bugs.openjdk.java.net/browse/JDK-8212233

The fix is to update the maven-javadoc-plugin version in
onos-dependencies via onos-base (bumped to v2).

This patch introduces further improvements to onos-dependencies such as:
- Profile that emulates CI release jobs (e.g., javadoc verification)
- Compile-time errorprone checks

Change-Id: I214482f14ee757f584c506d68a7d91b9a6702c20
(cherry picked from commit 5fcc2fe4c46e57e0c0c36cdb5daa36e57b5c447f)
2019-11-18 23:58:53 +00:00
Carmelo Cascone
27b9712f3a Revamp support for building third-party apps via maven
- Publish onos-dependencies (autogenerated from deps.json). With most
  3rd-party dependencies listed as <dependencyManagement> to avoid
  version conflicts, and a minimal set listed as <dependencies> to
  simplify child poms. Similarly, we provide a number of plugins already
  configured as <pluginManagement> to support the whole life-cycle of
  apps (from build, to reporting and release).
- Update Maven plugins to work with JDK 11 (checkstyle, pmd, etc.)
- Publish onos-build-conf (with common checkstyle and pmd confs)
- Removed unused checkstyle code
- Fix OSGi version mismatch in deps.json to consistently depend on
  release 6 (the one supported by Karaf 4)
- Update/simplify archetypes to use onos-dependencies as the parent pom

Change-Id: Ic09b34e13fb49eb3d96df623b53a3617bbf7b7e4
2019-11-18 23:58:27 +00:00