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

ASF GitHub Bot commented on CXF-7328:
-------------------------------------

GitHub user deki opened a pull request:

    https://github.com/apache/cxf/pull/259

    CXF-7328: fixed property metadata for Spring Boot CxfProperties, updated 
maven-bundle-plugin

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/deki/cxf CXF-7328

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf/pull/259.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #259
    
----
commit 04816a5f959288af53c0f6f41dca55db18442811
Author: Dennis Kieselhorst <d...@apache.org>
Date:   2017-04-13T13:44:22Z

    CXF-7328: updated maven-bundle-plugin

commit 9bb319dea1462644d559f223ed23507431cb0067
Author: Dennis Kieselhorst <d...@apache.org>
Date:   2017-04-13T13:45:15Z

    CXF-7328: fixed property metadata for Spring Boot CxfProperties

----


> No property metadata for CxfProperties
> --------------------------------------
>
>                 Key: CXF-7328
>                 URL: https://issues.apache.org/jira/browse/CXF-7328
>             Project: CXF
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 3.1.11
>            Reporter: Stephane Nicoll
>
> The Spring Boot integration exposes a `cxf` namespace via `CxfProperties` and 
> none of the advertized keys are exposed in the metadata.
> This means there is no autocompletion for those keys in IDEs. It is really 
> easy to get those metadata so please add the annotation processor to the 
> build of the autoconfigure module.
> http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#configuration-metadata-annotation-processor



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to