can't build java_first_spring_support example
---------------------------------------------

                 Key: CXF-3120
                 URL: https://issues.apache.org/jira/browse/CXF-3120
             Project: CXF
          Issue Type: Bug
          Components: Samples
    Affects Versions: 2.2.11
            Reporter: Freeman Fang
            Assignee: Freeman Fang


get exception like
/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[21,25]
 package org.mortbay.jetty does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[22,25]
 package org.mortbay.jetty does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[23,33]
 package org.mortbay.jetty.handler does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[24,33]
 package org.mortbay.jetty.handler does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[25,29]
 package org.mortbay.jetty.nio does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[26,32]
 package org.mortbay.jetty.webapp does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[40,25]
 package org.mortbay.jetty does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[40,63]
 package org.mortbay.jetty does not exist

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[42,8]
 cannot find symbol
symbol  : class SelectChannelConnector
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[42,47]
 cannot find symbol
symbol  : class SelectChannelConnector
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[44,33]
 cannot find symbol
symbol  : class Connector
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[46,8]
 cannot find symbol
symbol  : class WebAppContext
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[46,42]
 cannot find symbol
symbol  : class WebAppContext
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[51,8]
 cannot find symbol
symbol  : class HandlerCollection
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[51,41]
 cannot find symbol
symbol  : class HandlerCollection
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[52,33]
 cannot find symbol
symbol  : class Handler
location: class demo.spring.servlet.Server

/Users/ffang/apache-cxf-2.2.11/samples/java_first_spring_support/src/demo/spring/servlet/Server.java:[52,63]
 cannot find symbol
symbol  : class DefaultHandler
location: class demo.spring.servlet.Server

This is because in the pom.xml, use <cxf.version>[2,)</cxf.version>, which in 
turn the dependency tree will pick up  the latest 
cxf-rt-transports-http-jetty(it's 2.4.0-SNAPSHOT from my test, not the latest 
released version 2.3.0), which use jetty 7.0, so the jetty related class 
package just change.

I believe this problem also in other samples which use jetty related class, and 
I think we need use exact version for each release rather than the version 
range(in which case during the building of released example will pick up the 
snapshot dependency, we should avoid it )

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to