Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Issue Links

        Activity

        Hide
        ramapulavarthi added a comment -

        Yes, most of the sub components are created for the consumption of JAX-WS/Metro project and are hosted as separate projects on java.net for reuse in other projects. The primary (possibly only) consumer of the policy project as of now is JAX-WS RI. We can assume for policy, all policy developers are jax-ws developers.

        If we publish the artifacts in use under a new groupId, would n't it be a problem for the migration of old artifacts already deployed on http://download.java.net/maven/2 to this new repo? Also, would n't it be a compatibility problem for the users to know about the new groupId to pick up updated versions. Is there a recommended way to document about the change of groupId, artifactId in the maven artifacts rather than in a website?

        Show
        ramapulavarthi added a comment - Yes, most of the sub components are created for the consumption of JAX-WS/Metro project and are hosted as separate projects on java.net for reuse in other projects. The primary (possibly only) consumer of the policy project as of now is JAX-WS RI. We can assume for policy, all policy developers are jax-ws developers. If we publish the artifacts in use under a new groupId, would n't it be a problem for the migration of old artifacts already deployed on http://download.java.net/maven/2 to this new repo? Also, would n't it be a compatibility problem for the users to know about the new groupId to pick up updated versions. Is there a recommended way to document about the change of groupId, artifactId in the maven artifacts rather than in a website?
        Hide
        juven added a comment -

        So when we migrate old artifacts on http://download.java.net/maven/2/, we don't care about which project they belong to or what groupId they use, because people already use them a lot and they will be frozen, what I'm trying to do here is make sure new artifacts are good maven citizen .

        Maven does not have any method for documenting groupId change , so the project owners have to do it by themselves. From my experience I don't think it's a big problem since lots of projects hosted on oss.sonatype.org did that, and w/ the help of search engine like http://search.maven.org/, it's very easy for your users to get your latest maven coordinates.

        You know, if people don't follow a convention to define their groupId/artifactId, the repository will soon become a mess.

        thanks,
        juven

        Show
        juven added a comment - So when we migrate old artifacts on http://download.java.net/maven/2/ , we don't care about which project they belong to or what groupId they use, because people already use them a lot and they will be frozen, what I'm trying to do here is make sure new artifacts are good maven citizen . Maven does not have any method for documenting groupId change , so the project owners have to do it by themselves. From my experience I don't think it's a big problem since lots of projects hosted on oss.sonatype.org did that, and w/ the help of search engine like http://search.maven.org/ , it's very easy for your users to get your latest maven coordinates. You know, if people don't follow a convention to define their groupId/artifactId, the repository will soon become a mess. thanks, juven
        Hide
        ramapulavarthi added a comment -

        I came across this page to document groupId change/relocation.
        http://maven.apache.org/guides/mini/guide-relocation.html

        We might have to push all our old artifacts one more time with the relocation information.

        Show
        ramapulavarthi added a comment - I came across this page to document groupId change/relocation. http://maven.apache.org/guides/mini/guide-relocation.html We might have to push all our old artifacts one more time with the relocation information.
        Hide
        ramapulavarthi added a comment -

        Hi Juven,
        You mentioned that repo org.jvnet.mimepull is setup, but I see net.java.mimepull. Can you please fix this?

        Show
        ramapulavarthi added a comment - Hi Juven, You mentioned that repo org.jvnet.mimepull is setup, but I see net.java.mimepull. Can you please fix this?
        Hide
        juven added a comment -

        @ramapulavarthi should be fixed now.

        Show
        juven added a comment - @ramapulavarthi should be fixed now.

          People

          • Assignee:
            juven
            Reporter:
            jitu
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: