Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of Bozhong.Lin@iona.com designates
 65.223.216.181 as permitted sender)
Message-ID: <45374BFE.4000106@iona.com>
Date: Thu, 19 Oct 2006 17:57:18 +0800
From: Bozhong Lin <blin@iona.com>
User-Agent: Thunderbird 1.5.0.4 (X11/20060516)
MIME-Version: 1.0
To: cxf-dev@incubator.apache.org
Subject: Re: jsr173-api-1.0.jar and stax_api-1.0.jar
References: <4536D166.8050902@iona.com> <4536D1C0.10603@envoisolutions.com>
 <ec6e67fd0610190141k25d1c986v94e06df418999883@mail.gmail.com>
In-Reply-To: <ec6e67fd0610190141k25d1c986v94e06df418999883@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I can build cxf without any problem.

There does have another public jsr173-api.jar available here [1], and 
that one seems to be one that CXF is getting. The same api jar appears 
in multiple places in public repo, isn't this confusing? Hope someone 
can clean it up in the future.

Regards,
Bo

[1] http://repo1.maven.org/maven2/javax/xml/bind/jsr173_api/1.0/

James Strachan wrote:
> Can anyone else build cxf? I'm having trouble due to the jaxb maven
> plugin from Sun depending on the non-existing jsr173-api.jar (log
> below).
> 
> That reminds me, we should have a CI build where we zap the local
> maven repo before doing the build to check that the build really does
> work for everyone, not those who have a lucky local repo with just the
> right stuff in it :).
> 
> [INFO] 
> ---------------------------------------------------------------------------- 
> 
> [INFO] Building CXF XJC Configurable Beans Plugin Tests
> [INFO]    task-segment: [install]
> [INFO] 
> ---------------------------------------------------------------------------- 
> 
> [WARNING]
>        Artifact javax.xml.bind:jaxb-api:jar:2.0:runtime retains local
> scope 'runtime' overriding broader scope 'compile'
>        given by a dependency. If this is not intended, modify or
> remove the local scope.
> 
> [WARNING]
>        Artifact com.sun.xml.bind:jaxb-xjc:jar:2.0.1:runtime retains
> local scope 'runtime' overriding broader scope 'compile'
>        given by a dependency. If this is not intended, modify or
> remove the local scope.
> 
> [WARNING]
>        Artifact javax.xml.bind:jsr173_api:jar:1.0:runtime retains
> local scope 'runtime' overriding broader scope 'compile'
>        given by a dependency. If this is not intended, modify or
> remove the local scope.
> 
> [WARNING]
>        Artifact com.sun.xml.bind:jaxb-impl:jar:2.0.1:runtime retains
> local scope 'runtime' overriding broader scope 'compile'
>        given by a dependency. If this is not intended, modify or
> remove the local scope.
> 
> Downloading: 
> https://maven-repository.dev.java.net/nonav/repository//javax.xml/jars/jsr173-1.0.jar 
> 
> [WARNING] Unable to get resource from repository java.net
> (https://maven-repository.dev.java.net/nonav/repository/)
> Downloading: 
> file:/workspace/eclipse/cxf/tools/xjc/cfg-test/../../../maven_repo/javax/xml/jsr173/1.0/jsr173-1.0.jar 
> 
> [WARNING] Unable to get resource from repository snapshots_internal
> (file:/workspace/eclipse/cxf/tools/xjc/cfg-test/../../../maven_repo)
> Downloading: 
> http://repo1.maven.org/maven2/javax/xml/jsr173/1.0/jsr173-1.0.jar
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> 
> Missing:
> ----------
> 1) javax.xml:jsr173:jar:1.0
> 
>  Try downloading the file manually from:
>      http://ftpna2.bea.com/pub/downloads/jsr173.jar
> 
>  Then, install it using the command:
>      mvn install:install-file -DgroupId=javax.xml -DartifactId=jsr173 \
>          -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
> 
>  Path to dependency:
>        1) com.sun.tools.xjc.maven2:maven-jaxb-plugin:maven-plugin:1.0
>        2) com.sun.xml.bind:jaxb-impl:jar:2.0.1
>        3) javax.xml:jaxb-api:jar:2.0
>        4) javax.xml:jsr173:jar:1.0
> 
> ----------
> 1 required artifact is missing.
> 
> for artifact:
>  com.sun.tools.xjc.maven2:maven-jaxb-plugin:maven-plugin:1.0
> 
> from the specified remote repositories:
>  central (http://repo1.maven.org/maven2),
>  java.net (https://maven-repository.dev.java.net/nonav/repository/),
>  snapshots_internal
> (file:/workspace/eclipse/cxf/tools/xjc/cfg-test/../../../maven_repo)
> 
> 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 4 minutes 1 second
> [INFO] Finished at: Wed Oct 18 10:28:37 BST 2006
> [INFO] Final Memory: 17M/33M
> [INFO] 
> ------------------------------------------------------------------------
> 
> 
> 
> On 10/19/06, Dan Diephouse <dan@envoisolutions.com> wrote:
>> Bozhong Lin wrote:
>>
>> > Does anyone has any idea why we have both jsr173-api-1.0.jar and
>> > stax_api-1.0.jar? They seem to contain the same set of binary classes,
>> > which all belong to Stax api classes.
>> >
>> > Thanks,
>> > Bo
>>
>> Probably errors in dependency's poms. Some include stax-api, some
>> include jsr173. I suppose the later is more correct, but the former has
>> been around long (then maven people didn't add jsr173 until later).
>> Also, the stax API's current version is 1.0.1 so we might want to think
>> about using that, however probably not critical ifit involves a lot of
>> POM changes.
>>
>> - Dan
>>
>> -- 
>> Dan Diephouse
>> (616) 971-2053
>> Envoi Solutions LLC
>> http://netzooid.com
>>
>>
> 
>