Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Resolution: Won't Fix
    • Component/s: Invalid POM
    • Labels:
      None
    • Group ID:
      javax.xml.ws
    • Artifact ID:
      jaxws-api
    • Version:
      2.1

      Description

      Sun just released jaxws 2.1 and the jaxws-api available at repo1.maven.org is not the same with the Sun's one (both pom and the jar )
      I am working jaxws-maven-plugin and the generate code crash due to missing interfaces

      We can either sync the sun version over, or remove it from repo1 to remove confusion

      Here is the link to java.net repo

      https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.ws/

        Issue Links

          Activity

          Hide
          Marat Radchenko added a comment -

          This isn't good. My pom refers to both repo1 and java.net. I don't have any means to specify where jaxws-2.1 should be taken from (and of course it's taken from wrong repository).

          Show
          Marat Radchenko added a comment - This isn't good. My pom refers to both repo1 and java.net. I don't have any means to specify where jaxws-2.1 should be taken from (and of course it's taken from wrong repository).
          Hide
          Carlos Sanchez added a comment -

          Marat, that's not our responsibility, by definition releases shouldn' t be changed on the repository, and they were changed at java.net repo

          Show
          Carlos Sanchez added a comment - Marat, that's not our responsibility, by definition releases shouldn' t be changed on the repository, and they were changed at java.net repo
          Hide
          Dan Tran added a comment -

          Marat, here is the work around

          • install a good copy of javax-api at your internal repo.
          • Use maven-proxy and configure it to pickup artifact at your internal repo first then repo1

          On the second thought, It is a real pain for this setup. Can we make it as an exception??

          Show
          Dan Tran added a comment - Marat, here is the work around install a good copy of javax-api at your internal repo. Use maven-proxy and configure it to pickup artifact at your internal repo first then repo1 On the second thought, It is a real pain for this setup. Can we make it as an exception??
          Hide
          Carlos Sanchez added a comment -

          the solution was already proposed, we can host a 2.1-1 with the right pom and jar, but somebody has to prepare and request it

          Show
          Carlos Sanchez added a comment - the solution was already proposed, we can host a 2.1-1 with the right pom and jar, but somebody has to prepare and request it
          Hide
          Daniel Kulp added a comment -

          Created upload request for a 2.1-1 version.

          http://jira.codehaus.org/browse/MAVENUPLOAD-1786

          Show
          Daniel Kulp added a comment - Created upload request for a 2.1-1 version. http://jira.codehaus.org/browse/MAVENUPLOAD-1786

            People

            • Assignee:
              Carlos Sanchez
              Reporter:
              Dan Tran
            • Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: