You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Thomas Andraschko (Jira)" <ji...@apache.org> on 2019/10/05 16:00:00 UTC

[jira] [Commented] (OWB-1299) Add an openwebbeans.properties property to not scan jars with an extension

    [ https://issues.apache.org/jira/browse/OWB-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945086#comment-16945086 ] 

Thomas Andraschko commented on OWB-1299:
----------------------------------------

Wouldnt it be better to add a flag to skip scanning JARs without beans.xml?

> Add an openwebbeans.properties property to not scan jars with an extension
> --------------------------------------------------------------------------
>
>                 Key: OWB-1299
>                 URL: https://issues.apache.org/jira/browse/OWB-1299
>             Project: OpenWebBeans
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>            Assignee: Romain Manni-Bucau
>            Priority: Major
>             Fix For: 2.0.13
>
>
> {code:java}
> org.apache.webbeans.scanExtensionJars = true {code}
> Can be added to openwebbeans.properties to disable the scanning of the jars with an extension. Long story short, this is the official CDI behavior since 1.1 but in 1.0 it was the opposite so we kept it in most of our default implementations to ensure backward compatibility.
>  
> {code:java}
> org.apache.webbeans.scanExclusionPaths = ....,/my-extension-jar {code}
> was a workaround until today to get the specification behavior.
>  
> Side note: in general you don't need to set this and default will work smoothless until the extension scanning duplicates the beans it register programmatically.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)