Seems to work pretty well with my Karaf 4 application, but I'm not sure if
Camel is finding my custom TypeConverter classes. I'm using MapStruct and
writing custom wrapper classes with the @Converter annotation along with
the META-INF file to show the package. Do these converter packages need to
be manually exported as packages in OSGi now, or could this be a regression
from 2.17?

On 5 October 2016 at 09:54, Gregor Zurowski <gre...@list.zurowski.org>
wrote:

> Hi Everyone:
>
> This is a vote to release Apache Camel 2.18.0, the first release that
> requires Java 8, comes with a much-improved Spring Boot support, and
> ships with numerous new features and improvements. (For further
> details please see
> http://www.davsclaus.com/2016/06/apache-camel-218-
> highlights-of-what-is.html.)
>
> Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12334759&projectId=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1059/
>
> Tarballs: https://repository.apache.org/content/repositories/
> orgapachecamel-1059/org/apache/camel/apache-camel/2.18.0/
>
> Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> e278cf0a1fe689d43e913009e88688c591e291b2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.18.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.  Due to the bigger changes
> introduced with this release, it would be beneficial if we could get
> as many Camel riders involved in testing this RC as possible.
>
> Thanks,
> Gregor
>



-- 
Matt Sicker <boa...@gmail.com>

Reply via email to