camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zemian Deng <saltnlig...@gmail.com>
Subject Re: About the spi-annotations dependency
Date Fri, 09 Aug 2013 01:53:59 GMT
Proper pom.xm should let IDE automatically do that without manually adding
classpath. Either add spi-annotations to camel-core as non-optional, or
have any other modules declare it explicitly.

I think more puzzling to me is how come running maven on command line works
fine?


On Thu, Aug 8, 2013 at 9:03 AM, Devendra Khanolkar
<devendra0008@yahoo.com>wrote:

> Do you have the latest build?
> I had a similar problem but a quick way to get around this is just to add
> the spi-annotations.jar manually in the project classpath. And yes the
> UriParam annotation is derived from that spi-annotations jar.
>
> Thanks.
> Dev.
>
> Sent from my iPad
>
> On 07/08/2013, at 11:01 AM, saltnlight5 <saltnlight5@gmail.com> 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.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message