[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-06-03 Thread michael.m.cla...@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163453#comment-163453 ] Michael Clarke commented on JENKINS-12598: -- This has been included in Version 2.4

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-06-01 Thread scm_issue_l...@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163426#comment-163426 ] SCM/JIRA link daemon commented on JENKINS-12598: Code changed in jenkins

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-05-31 Thread scm_issue_l...@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163378#comment-163378 ] SCM/JIRA link daemon commented on JENKINS-12598: Code changed in jenkins

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-05-31 Thread scm_issue_l...@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12598. Resolution: Fixed In 2.0 update you need to specify branch for

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-05-29 Thread fred...@hotmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G reopened JENKINS-12598: -- Sorry for reopening this issue. I tested version 2.4-SNAPSHOT. During the upgrade from version 2.3 all

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-05-28 Thread michael.m.cla...@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] In 2.0 update you need to specify branch for every module - Key: JENKINS-12598

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-05-28 Thread michael.m.cla...@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke resolved JENKINS-12598. -- Assignee: Michael Clarke Resolution: Fixed A change for this was included in

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-04-06 Thread fred...@hotmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161343#comment-161343 ] Fred G commented on JENKINS-12598: -- I agree, my mockup is definitely not the best.

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-04-02 Thread michael.m.cla...@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke updated JENKINS-12598: - Attachment: repositoryLocationProposal.png I've attached the UI mockup of how I think

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-04-02 Thread michael.m.cla...@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161107#comment-161107 ] Michael Clarke edited comment on JENKINS-12598 at 4/2/12 6:32 PM:

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

2012-02-15 Thread fred...@hotmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G updated JENKINS-12598: - Attachment: Jenkins_CvsPluginModules.png In 2.0 update you need to specify branch for every