[jira] [Updated] (PROTON-210) Proton release.sh should create a single release tarball for proton-c/proton-j
[ https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-210: --- Fix Version/s: 0.4 Proton release.sh should create a single release tarball for proton-c/proton-j -- Key: PROTON-210 URL: https://issues.apache.org/jira/browse/PROTON-210 Project: Qpid Proton Issue Type: New Feature Components: proton-c, proton-j Reporter: Keith Wall Assignee: Rafael H. Schloming Fix For: 0.4 Following changes made by PROTON-194, the release script must change to create a single tarball containing proton-c, proton-j and test trees. The tarball should exclude proton-c/examples/mailbox and proton-j/contrib. It should contain to perform a maven the maven version set/commit. The ruby gem will be unaffected by this change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-210) Proton release.sh should create a single release tarball for proton-c/proton-j
[ https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-210: -- Issue Type: New Feature (was: Task) Proton release.sh should create a single release tarball for proton-c/proton-j -- Key: PROTON-210 URL: https://issues.apache.org/jira/browse/PROTON-210 Project: Qpid Proton Issue Type: New Feature Components: proton-c, proton-j Reporter: Keith Wall Assignee: Keith Wall Following changes made by PROTON-194, the release script must change to create a single tarball containing proton-c, proton-j and test trees. The tarball should exclude proton-c/examples/mailbox and proton-j/contrib. It should contain to perform a maven the maven version set/commit. The ruby gem will be unaffected by this change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-210) Proton release.sh should create a single release tarball for proton-c/proton-j
[ https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-210: -- Component/s: proton-j Proton release.sh should create a single release tarball for proton-c/proton-j -- Key: PROTON-210 URL: https://issues.apache.org/jira/browse/PROTON-210 Project: Qpid Proton Issue Type: New Feature Components: proton-c, proton-j Reporter: Keith Wall Assignee: Keith Wall Following changes made by PROTON-194, the release script must change to create a single tarball containing proton-c, proton-j and test trees. The tarball should exclude proton-c/examples/mailbox and proton-j/contrib. It should contain to perform a maven the maven version set/commit. The ruby gem will be unaffected by this change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-210) Proton release.sh should create a single release tarball for proton-c/proton-j
[ https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-210: -- Component/s: (was: proton-j) Proton release.sh should create a single release tarball for proton-c/proton-j -- Key: PROTON-210 URL: https://issues.apache.org/jira/browse/PROTON-210 Project: Qpid Proton Issue Type: New Feature Components: proton-c Reporter: Keith Wall Assignee: Keith Wall Following changes made by PROTON-194, the release script must change to create a single tarball containing proton-c, proton-j and test trees. The tarball should exclude proton-c/examples/mailbox and proton-j/contrib. It should contain to perform a maven the maven version set/commit. The ruby gem will be unaffected by this change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
