Details

    • Type: Task Task
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.15.0-GA
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      It would be nice if Javassist were published to Maven central regularly

        Issue Links

          Activity

          Hide
          Pete Muir
          added a comment -

          I am happy to take on this task, but I will need

          a) to make a few modifications to the metadata in Javassist POM (such as license, committers etc.) so that it passes the quality guidelines
          b) to be notified when releases are made.

          If this is desirable, please assign the issue to me, and I will work on this at some point.

          Show
          Pete Muir
          added a comment - I am happy to take on this task, but I will need a) to make a few modifications to the metadata in Javassist POM (such as license, committers etc.) so that it passes the quality guidelines b) to be notified when releases are made. If this is desirable, please assign the issue to me, and I will work on this at some point.
          Show
          firstname lastname
          added a comment - Thanks Pete, this would help powermock too http://code.google.com/p/powermock/issues/detail?id=45#c2 http://groups.google.com/group/powermock/browse_thread/thread/1e24fc6a94161c34
          Hide
          Andrew Dinn
          added a comment -

          I have updated the pom to allow publishing to the new jboss repo, either of snapshots or full releases. I used this to install the jars derived from the 3.12.0.GA tagged tree.

          I added all the required elements such as license, scm, etc. So far, I have only added myself and chiba as devs – I don't have the required info for other contributors.

          Also, I rolled over the version number to 3.12.1-SNAPSHOT after uploading 3.12.0.GA. So, any new snapshjots should sort correctly.

          Pete, if you can check this is ok then we should be able to close this JIRA.

          Show
          Andrew Dinn
          added a comment - I have updated the pom to allow publishing to the new jboss repo, either of snapshots or full releases. I used this to install the jars derived from the 3.12.0.GA tagged tree. I added all the required elements such as license, scm, etc. So far, I have only added myself and chiba as devs – I don't have the required info for other contributors. Also, I rolled over the version number to 3.12.1-SNAPSHOT after uploading 3.12.0.GA. So, any new snapshjots should sort correctly. Pete, if you can check this is ok then we should be able to close this JIRA.
          Hide
          Pete Muir
          added a comment -

          I have set up a Hudson job to publish snapshots to the JBoss Snapshots repository. It's currently failing on the problem compiling the test classes, I will try to work out the problem and file an issue.

          I would still like to get this published to Maven central (repo1.maven.org) if possible. If you are happy for me to do this, I will get the process started.

          I also noticed that the license section doesn't mention the MPL - I think it should.

          Show
          Pete Muir
          added a comment - I have set up a Hudson job to publish snapshots to the JBoss Snapshots repository. It's currently failing on the problem compiling the test classes, I will try to work out the problem and file an issue. I would still like to get this published to Maven central (repo1.maven.org) if possible. If you are happy for me to do this, I will get the process started. I also noticed that the license section doesn't mention the MPL - I think it should.
          Hide
          Andrew Dinn
          added a comment -

          I'm happy about this being published to Maven central but it is Chiba who needs to confirm that.

          Regarding the license: I specifed LGPL 2.1 as the license in the pom because I understood that to be the license under which JBoss ships javassist as part of AS. The license details available via in the Readme (in the root of the distribution) make provision for this form of redistribution.

          This may not be appropriate if we install the release in Maven central since we are not then distributing it.

          Also, if we do continue to distribute from our repo then the license terms may need revisiting. It is not clear to me whether we have to explicitly remove the MPL details as included by Chiba and replace them with a reference to the LGPL or whether we are covered by the fact that we have specified the LGPL in the pom. Perhaps someone else (Chiba and/or a lawyer) can comment?

          Show
          Andrew Dinn
          added a comment - I'm happy about this being published to Maven central but it is Chiba who needs to confirm that. Regarding the license: I specifed LGPL 2.1 as the license in the pom because I understood that to be the license under which JBoss ships javassist as part of AS. The license details available via in the Readme (in the root of the distribution) make provision for this form of redistribution. This may not be appropriate if we install the release in Maven central since we are not then distributing it. Also, if we do continue to distribute from our repo then the license terms may need revisiting. It is not clear to me whether we have to explicitly remove the MPL details as included by Chiba and replace them with a reference to the LGPL or whether we are covered by the fact that we have specified the LGPL in the pom. Perhaps someone else (Chiba and/or a lawyer) can comment?
          Hide
          Pete Muir
          added a comment -

          Ok, we will wait on Chiba for Maven central.

          I believe that Javassist is dual-licensed under both the MPL AND the LGPL. As such the POM such detail both licenses.

          Show
          Pete Muir
          added a comment - Ok, we will wait on Chiba for Maven central. I believe that Javassist is dual-licensed under both the MPL AND the LGPL. As such the POM such detail both licenses.
          Hide
          Pete Muir
          added a comment -

          I mean, should detail both licenses

          Show
          Pete Muir
          added a comment - I mean, should detail both licenses
          Hide
          Andrew Dinn
          added a comment -

          I agree about the dual licensing – I have patched the pom.xml license section accordingly with a comment indicating that LGPL 2.1 applies when javassist is bundled with JBoss AS.

          Show
          Andrew Dinn
          added a comment - I agree about the dual licensing – I have patched the pom.xml license section accordingly with a comment indicating that LGPL 2.1 applies when javassist is bundled with JBoss AS.
          Hide
          Shigeru Chiba
          added a comment -

          I am also happy to publish Javassist to Maven central.
          As for b), how do I do that? Is just sending an email to Pete enough?

          Show
          Shigeru Chiba
          added a comment - I am also happy to publish Javassist to Maven central. As for b), how do I do that? Is just sending an email to Pete enough?
          Hide
          Pete Muir
          added a comment -

          Chiba, for now, that is the best plan. I will then write up a wiki page to detail the process I took, so others can replicate it.

          Show
          Pete Muir
          added a comment - Chiba, for now, that is the best plan. I will then write up a wiki page to detail the process I took, so others can replicate it.
          Hide
          Pete Muir
          added a comment -

          https://issues.sonatype.org/browse/OSSRH-570 has been created to request the sync up.

          Andrew, I would suggest you create an account on oss.sonatype.org so that you can do this work directly, and then comment on the issue that you need access.

          Show
          Pete Muir
          added a comment - https://issues.sonatype.org/browse/OSSRH-570 has been created to request the sync up. Andrew, I would suggest you create an account on oss.sonatype.org so that you can do this work directly, and then comment on the issue that you need access.
          Hide
          Pete Muir
          added a comment -

          Andrew/Chiba, we've been asked to not use javassist as the group id, but instead use a qualfied name. For example, org.jboss.javassist. WDYT about that?

          Show
          Pete Muir
          added a comment - Andrew/Chiba, we've been asked to not use javassist as the group id, but instead use a qualfied name. For example, org.jboss.javassist. WDYT about that?
          Hide
          Pete Muir
          added a comment -

          Outstanding tasks:

          Show
          Pete Muir
          added a comment - Outstanding tasks: Ensure that the POMs are well formed - https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement Consider qualifying the group id add the ability to sign artifacts to the POMs, and write a profile that will push the release to the oss.sonatype.org repo, so it's as simple as typing -PcentralRelease get someone from the core team an account on oss.sonatype.org so they can push releases Write a short wiki page to explain the process

            People

            • Assignee:
              Unassigned
              Reporter:
              Pete Muir
            • Votes:
              6 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: