[ https://jira.jboss.org/jira/browse/JGRP-819?page=com.atlassian.jira.plugi... ] Manik Surtani commented on JGRP-819: ------------------------------------ JBoss-parent POM [1] has an example of using the "maven-source-plugin" plugin. [1] http://repository.jboss.org/maven2/org/jboss/jboss-parent/4.0.CR1/jboss-p... -- 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/JGRP-819?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on JGRP-819: ------------------------------------------ I've had a look at the issue and have a proposal: 1. At present, JGroups uses an ant-based build, so that the maven-source-plugin for generating the file jgroups-sources.jar isn't practicable. Easiest is to add a new target to the JGroups ant build to build the jgroups-sources.jar file (which has a format different from that of the JGroups-x.y.z.src.zip file) and place it in the dist directory along with jgroups-all.jar and jgroups-core.jar. 2. At present, we update the buildmagic repository (component-info.xml, lib/jgroups.jar) by hand by checking out the jgroups subdirectory, creating directories and adding in the files required to the working copy, and then committing the changes. We update the maven2 repository (maven-meta-data, jgroups.jar, checksums) in a similar way, but making use of the maven command deploy:deploy-file to create directories, copy and rename files, and create checksums: With the file jgroups-sources.jar available in the distribution, we can add a copy of jgroups-sources.jar to the repo, appropriately renamed and checksums updated, by using the command: This is the only extra step in the release process required once the ant tasks have been created. If this seems OK, i'll go ahead and (i) add the ant tasks to 2.7 and 2.6.4 to build the jgroups-sources.jar by default when the distribution is built (ii) update the release docs to describe the process above in more detail so anyone can carry it out (iii) update the JGroups entry on the JBoss QA wiki with the same info (iv) put the source files up there so that Manik can have access to them -- 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/JGRP-819?page=com.atlassian.jira.plugi... ] Manik Surtani commented on JGRP-819: ------------------------------------ If you could do 2.6.3.GA and 2.6.4.CR1 this would be great. Thanks! Manik -- 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/JGRP-819?page=com.atlassian.jira.plugi... ] Richard Achmatowicz closed JGRP-819. ------------------------------------ Resolution: Done Waiting offline for the reply from Paul Gier concerning the maven metadata.xml file. -- 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