You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Bozhong Lin <bl...@iona.com> on 2006/10/19 03:14:14 UTC
jsr173-api-1.0.jar and stax_api-1.0.jar
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
Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Posted by James Strachan <ja...@gmail.com>.
On 10/19/06, Bozhong Lin <bl...@iona.com> wrote:
> There does have another public jsr173-api.jar available here [1], and
> that one seems to be one that CXF is getting.
Though my build error was not CXF not finding that jar, it was the Sun
jaxb maven plugin not finding a different dependent jar, namely
javax.xml:jsr173:jar:1.0
It turns out if I zapped my ~/.m2/repository/com/sun directory and
tried again, it seems to work now! It could be the dependency changed
in a more recent distro or something.
Damn these random local maven repos! :)
--
James
-------
http://radio.weblogs.com/0112098/
Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Posted by Bozhong Lin <bl...@iona.com>.
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 <da...@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
>>
>>
>
>
Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Posted by James Strachan <ja...@gmail.com>.
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 <da...@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
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Posted by Daniel Kulp <da...@iona.com>.
On Wednesday October 18 2006 9:15 pm, Dan Diephouse 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.
> 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.
Just FYI: changing version numbers should NEVER involve a "lot of POM
changes." There is a dependencyManagement section of the top level pom
that should define all the versions of the "stuff" that is depended on by
all the other artifacts. In ALL the other poms, the <version> tag
should be left out of all dependencies so the version in the top level
pom is picked up. Thus, it's "easy" to update the entire tree.
Enjoy!
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Posted by David Jencks <da...@yahoo.com>.
On Oct 18, 2006, at 6:15 PM, Dan Diephouse 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.
I have not personally tried this but I've been told that the stax-api
1.0.1 version includes fixes to some bugs present in the jsr173 jar
and stax-api 1.0 jar that prevent stax from working on non-sun jdks
such as the ibm jdk. For integration with geronimo it will make our
life simpler if you use the stax-api 1.0.1 jar.
thanks
david jencks
>
> - Dan
>
> --
> Dan Diephouse
> (616) 971-2053
> Envoi Solutions LLC
> http://netzooid.com
>
Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Posted by Dan Diephouse <da...@envoisolutions.com>.
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
Re: jsr173-api-1.0.jar and stax_api-1.0.jar
Posted by Guillaume Nodet <gn...@gmail.com>.
Btw, where did you find the jsr173 jar in public repo ?
The public ones only include the pom:
http://repo.mergere.com/maven2/javax/xml/jsr173/1.0/
On 10/19/06, Bozhong Lin <bl...@iona.com> 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
>
--
Cheers,
Guillaume Nodet