[ https://jira.jboss.org/jira/browse/JASSIST-96?page=com.atlassian.jira.plu... ] Pete Muir commented on JASSIST-96: ---------------------------------- 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JASSIST-96?page=com.atlassian.jira.plu... ] Andrew Dinn commented on JASSIST-96: ------------------------------------ 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JASSIST-96?page=com.atlassian.jira.plu... ] Andrew Dinn commented on JASSIST-96: ------------------------------------ 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? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JASSIST-96?page=com.atlassian.jira.plu... ] Pete Muir commented on JASSIST-96: ---------------------------------- I mean, should detail both licenses :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JASSIST-96?page=com.atlassian.jira.plugin.s... ] Shigeru Chiba commented on JASSIST-96: -------------------------------------- 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? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JASSIST-96?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on JASSIST-96: ---------------------------------- 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JASSIST-96?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on JASSIST-96: ---------------------------------- Outstanding tasks: * Ensure that the POMs are well formed - https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repositor... * 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-96?page=com.atlassian.jira.plugin... ] Shigeru Chiba closed JASSIST-96. -------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira