[
https://issues.apache.org/jira/browse/CAMEL-9764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220111#comment-15220111
]
Raúl Kripalani commented on CAMEL-9764:
---------------------------------------
Fixed camel-ognl and camel-ftp. I wonder why those tests didn't fail at first
with a full execution of run-tests.sh.
With regards to the WARNINGs, there's little we can do. Never versions of the
maven-bundle-plugin print out that WARN without an option to turn them off.
They even acknowledge in code comments that the plugin can be used in POM
project types (does it makes a sense to print out a warning when it's a valid
use case?).
https://github.com/apache/felix/blob/ac5ec40ee40ec92dc8124e22afa855ab2c4a850f/tools/maven-bundle-plugin/src/main/java/org/apache/felix/bundleplugin/BundlePlugin.java#L271-L277
An alternative would be to never inherit the plugin execution, and to declare
it individually in all pom.xml of JAR types only. This is unmanageable and no
one wants that.
BTW - if we are focusing on warnings that don't affect the build, the unused
imports are more important (produced by fixed block OSGi imports inherited from
the parent pom.xml).
Cheers,
Raúl.
> Maven build: fix to support lambdas in code (JDK8)
> --------------------------------------------------
>
> Key: CAMEL-9764
> URL: https://issues.apache.org/jira/browse/CAMEL-9764
> Project: Camel
> Issue Type: Task
> Reporter: Raúl Kripalani
> Assignee: Raúl Kripalani
> Fix For: 2.18.0
>
>
> See
> http://camel.465427.n5.nabble.com/Usage-of-Lambdas-in-our-Maven-build-jdk8-lambdas-branch-tp5779737.html.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
