You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cxf.apache.org by Christian Schneider <ch...@die-schneider.net> on 2012/11/29 11:16:44 UTC

CXF-DOSGI: Update to Java 1.6?

I would like to update CXF-DOSGi to Java 1.6. This gets us in sync again
with CXF which also uses 1.6 now.
The advantage is that we avoid some API constraint warnings and do not
need to import APIs like JAXWS.
Java 1.6 also allows to use @Override for methods defined in interfaces
which gives some safety.

What do you think?

Christian

Re: CXF-DOSGI: Update to Java 1.6?

Posted by Daniel Kulp <dk...@apache.org>.

Since DOSGi is now up to using CXF 2.7.0, you should just set it at 1.6 since it won't work on 1.5 anyway.   

Likely should update the Maven pre-req to 3.0 as well.   Not sure if it will properly work with 2.2.

Dan

On Nov 29, 2012, at 5:16 AM, Christian Schneider <ch...@die-schneider.net> wrote:

> I would like to update CXF-DOSGi to Java 1.6. This gets us in sync again
> with CXF which also uses 1.6 now.
> The advantage is that we avoid some API constraint warnings and do not
> need to import APIs like JAXWS.
> Java 1.6 also allows to use @Override for methods defined in interfaces
> which gives some safety.
> 
> What do you think?
> 
> Christian

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: CXF-DOSGI: Update to Java 1.6?

Posted by David Bosschaert <da...@gmail.com>.

Sounds like a good idea to me.

David


On 29 November 2012 10:16, Christian Schneider <ch...@die-schneider.net>wrote:

> I would like to update CXF-DOSGi to Java 1.6. This gets us in sync again
> with CXF which also uses 1.6 now.
> The advantage is that we avoid some API constraint warnings and do not
> need to import APIs like JAXWS.
> Java 1.6 also allows to use @Override for methods defined in interfaces
> which gives some safety.
>
> What do you think?
>
> Christian
>