Willem,

I will vote to make spi-annotation non-optional in camel-core since it only
has 4 classes, and they are already used in quite of few sub modules.

But if you stick to optional in camel-core, then any modules that uses
@UriParam should has a hard dependency on spi-annotation, not optional. We
should add spi-annotation in camel-jms/pom.xml as regular dependency. Here
is a list of modules that I can see using @UriParam:

camel-jms
camel-salesforce
camel-sap-netweaver
camel-sjms
camel-sql
camel-ssh
camel-twitter
camel-weather
camel-yammer

Same need to be check on other annotations usage, which I haven't check.



On Sat, Aug 10, 2013 at 3:08 AM, Willem jiang <willem.ji...@gmail.com>wrote:

>
> How about add the spi-annotation dependency as optional in the
> camel-jms/pom.xml?
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
> (English)
>           http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>
> On Wednesday, August 7, 2013 at 9:01 AM, saltnlight5 wrote:
>
> > Hi,
> >
> > I have a question on camel pom usage.
> >
> > In camel-core/pom.xml, the spi-annotations dependency is added as
> > <optional>true</optional>, however other modules such as
> camel-jms/pom.xml
> > do not include this dependency explicitly. Is that intentional? How does
> > camel-jms resolve this spi-annotations jar if it's only optional from the
> > core?
> >
> > When I use IntelliJ IDE to open the camel project, and it complains the
> > @UriParam is not resolvable in JmsEndpoint.java until I add this
> > spi-annotations into camel-jms/pom.xml. I wonder if any of you experience
> > this, or just my misunderstanding of the maven usage?
> >
> > Zemian
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/About-the-spi-annotations-dependency-tp5736873.html
> > Sent from the Camel Development mailing list archive at Nabble.com (
> http://Nabble.com).
>
>
>
>

Reply via email to