Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <5551F8E6.1070300@linagora.com>
References: <5551F8E6.1070300@linagora.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 12 May 2015 15:20:59 +0200
Message-ID: 
 <CAGB5yNkovvbhZz62-un2oGSD9gGrR57E_N8aStRt-ukGG-N_8A@mail.gmail.com>
Subject: Re: Why spi-annotation content is included in camel-core?
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi

As end users you should not depend on spi-annotations - only camel-core.
spi-annotations is an internal model used as part of building
camel-core using the camel apt compiler plugin.

On Tue, May 12, 2015 at 2:58 PM, Victor NO=C3=8BL <victor.noel@linagora.com=
> wrote:
> Hi,
>
> Why is spi-annotation included in camel-core?
>
> It's bothering because:
>  - the source are not in camel-core so one can't see the definition of th=
e
> annotatons (so it's not easy to use them like that).
>  - and then if we add spi-annotation to the pom, there is duplicate class=
es
> from the two artefacts which is not very nice in term of code quality.
>
> Is there really a reason to do that?
>
> Thanks,
>
> Victor


--=20
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/