On May 6, 2008, at 5:36 PM, Gotosleep3 wrote:


Here are my dependencies..

       <dependency>
           <groupId>org.apache.cxf</groupId>
           <artifactId>cxf-rt-frontend-jaxws</artifactId>
           <version>2.1</version>
       </dependency>
       <dependency>
           <groupId>org.apache.cxf</groupId>
           <artifactId>cxf-rt-transports-http</artifactId>
           <version>2.1</version>
       </dependency>

       <dependency>
           <groupId>org.apache.cxf</groupId>
           <artifactId>cxf-rt-transports-http-jetty</artifactId>
           <version>2.1</version>
       </dependency>

Same ones I used for 2.0.5. Except for the version number. My previous
post was invalid.

My findings so far:

jaxb-impl:2.1.6, jaxb-xjc:2.1.6, fastInfoset:1.2.2 Have to be resolved from
download.java.net/Maven/1

The CXF top level pom adds that to the repositories list so it should automatically grab stuff from there correctly.


wsdl4j:1.6.1 is only at cropwiki.irri.org/m2repo/wsdl4j/wsdl4j/.

I see that at central just fine:
http://repo1.maven.org/maven2/wsdl4j/wsdl4j/1.6.1/


This seems very strange to me that CXF 2.1 can be released with problems
like this.  How was it built?
Did you guys deploy the dependencies locally?

Actually, 2.1 was actually built and released with a completely clean local repository. Thus, I know it can grab everything it needs from the repos it has defined in it's poms. At least for build time.

Dan





dkulp wrote:


On May 5, 2008, at 6:31 PM, Gotosleep3 wrote:

Doing an install I am getting the following errors:

Missing:
----------
1) org.apache.cxf:apache-cxf:jar:2.1

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=org.apache.cxf
-DartifactId=apache-cxf
-Dversion=2.1 -Dpackaging=jar -Dfile=/path/to/file


This seems to be very strange..... From that, it looks like you have
a dependency on:
groupId: org.apache.cxf
artifactId: apache-cxf


That's not a valid dependency.   That's the full distribution
packaging project which isn't a "jar" project.   Thus, you  cannot
really depend on it.

Dan




Alternatively, if you host your own repository you can deploy the
file
there:

    mvn deploy:deploy-file -DgroupId=org.apache.cxf
-DartifactId=apache-cxf -D
version=2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]


Path to dependency:
      1) com.monsanto.tps.architecture:cxf-test:war:1.0.0-SNAPSHOT
      2) org.apache.cxf:apache-cxf:jar:2.1

2) com.sun.xml.bind:jaxb-xjc:jar:2.1.6

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=com.sun.xml.bind
-DartifactId=jaxb-xjc
-Dversion=2.1.6 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the
file
there:

    mvn deploy:deploy-file -DgroupId=com.sun.xml.bind
-DartifactId=jaxb-xjc -D
version=2.1.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[i
d]

Path to dependency:
      1) com.monsanto.tps.architecture:cxf-test:war:1.0.0-SNAPSHOT
      2) org.apache.cxf:apache-cxf:jar:2.1
      3) org.apache.cxf:cxf-tools-common:jar:2.1
      4) com.sun.xml.bind:jaxb-xjc:jar:2.1.6

3) com.sun.xml.bind:jaxb-impl:jar:2.1.6

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=com.sun.xml.bind
-DartifactId=jaxb-impl
-Dversion=2.1.6 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the
file
there:

    mvn deploy:deploy-file -DgroupId=com.sun.xml.bind
-DartifactId=jaxb-impl -
Dversion=2.1.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[
id]

Path to dependency:
      1) com.monsanto.tps.architecture:cxf-test:war:1.0.0-SNAPSHOT
      2) org.apache.cxf:apache-cxf:jar:2.1
      3) org.apache.cxf:cxf-tools-common:jar:2.1
      4) com.sun.xml.bind:jaxb-impl:jar:2.1.6

4) com.sun.xml.fastinfoset:FastInfoset:jar:1.2.2

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=com.sun.xml.fastinfoset
-DartifactId=Fa
stInfoset -Dversion=1.2.2 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the
file
there:

    mvn deploy:deploy-file -DgroupId=com.sun.xml.fastinfoset
-DartifactId=Fast
Infoset -Dversion=1.2.2 -Dpackaging=jar -Dfile=/path/to/file -
Durl=[url]
-Drepos
itoryId=[id]

Path to dependency:
      1) com.monsanto.tps.architecture:cxf-test:war:1.0.0-SNAPSHOT
      2) org.apache.cxf:apache-cxf:jar:2.1
      3) org.apache.cxf:cxf-rt-core:jar:2.1
      4) com.sun.xml.fastinfoset:FastInfoset:jar:1.2.2

5) javax.ws.rs:jsr311-api:jar:0.6

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=javax.ws.rs -
DartifactId=jsr311-api
-Dv
ersion=0.6 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the
file
there:

    mvn deploy:deploy-file -DgroupId=javax.ws.rs -
DartifactId=jsr311-api
-Dver
sion=0.6 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

Path to dependency:
      1) com.monsanto.tps.architecture:cxf-test:war:1.0.0-SNAPSHOT
      2) org.apache.cxf:apache-cxf:jar:2.1
      3) org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.1
      4) javax.ws.rs:jsr311-api:jar:0.6

----------
5 required artifacts are missing.

I browsed to see if these dependencies are in repo1.  They are not.

What to do?





--
View this message in context:
http://www.nabble.com/CXF-2.1-Maven-Dependency-Resolution-from-repo1-tp17071460p17071460.html
Sent from the cxf-user mailing list archive at Nabble.com.


Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog






--
View this message in context: 
http://www.nabble.com/CXF-2.1-Maven-Dependency-Resolution-from-repo1-tp17071460p17092850.html
Sent from the cxf-user mailing list archive at Nabble.com.


Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog



Reply via email to