[jbossws-issues] [JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec

[r searls (Jira)]

    [ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716919#comment-13716919 ] 

r searls commented on JBWS-4154:
--------------------------------

Jim,
I resolved my maven-enforcer issue.  Something in my env.

A different issue however,

I had trouble running the integration-tests.

I got the error that jbossws-cxf-performance-tests can not find
rome:rome:1.0
in the developer repository.  I checked the repository and indeed this
directory does not exist
    https://repository.jboss.org/nexus/content/groups/developer/rome/rome

The directory above it,
https://repository.jboss.org/nexus/content/groups/developer/rome
does exist and is dated Sun Mar 24 18:33:22 EDT 2019.  Nexus appear to have
failed with
this upload.

In order to run the tests I downloaded the jar from maven central and put
it in my local repo.

In looking for this jar file I found rome:rome:1.0 is very old. The last
release
was 2010-05-10.

There is a newer version here,
https://mvnrepository.com/artifact/com.rometools/rome
    <dependency>
        <groupId>com.rometools</groupId>
        <artifactId>rome</artifactId>
         <version>1.12.0</version>
    </dependency>


I have not been able to determine what is depending on this archive.
mvn dependency:tree does not provided helpful information.
Adding the dependency above does not override the old version and use the
newer one.


I don't know who is responsible for fixing the developer nexus
  https://repository.jboss.org/nexus/content/groups/developer/rome/rome

Should a jira be created to upgrade rome to a more current version?







> jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec
> ----------------------------------------------------------------------------------------
>
>                 Key: JBWS-4154
>                 URL: https://issues.jboss.org/browse/JBWS-4154
>             Project: JBoss Web Services
>          Issue Type: Bug
>    Affects Versions: jbossws-cxf-5.2.4.Final
>            Reporter: Jan Blizňák
>            Assignee: r searls
>            Priority: Major
>             Fix For: jbossws-cxf-5.3.0.Final
>
>
> dependency:tree goal output shows that jbossws-cxf-client (and transitively other modules too) depends on two versions of JBoss JAX-WS API:
> org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile
> org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec:jar:1.0.0.Final:compile
> The former is brought in by:
> {code:java}
>    +- org.jboss.ws.cxf:jbossws-cxf-transports-undertow:jar:5.2.5-SNAPSHOT:compile
>    |  \- org.jboss.ws.projects:jaxws-undertow-httpspi:jar:1.0.1.Final:compile
>    |   +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile
> {code}
> I guess we should stick to the newer one which would mean add some dependency exclude or update jaxws-undertow-httpspi to new API version stream (I vote for this)
> Whole dependency tree at https://github.com/jbliznak/jbws-dependency-trees/blob/jdk11-after/jbossws-cxf-client_module.txt



--
This message was sent by Atlassian Jira
(v7.12.1#712002)