Re: svn commit: r419764 - /geronimo/trunk/m2-plugins/pom.xml
On 7/7/06, Jason Dillon <[EMAIL PROTECTED]> wrote: On Jul 7, 2006, at 1:12 AM, Jacek Laskowski wrote: > It is when one's doing some non-trivial changes > without careful thinking how to sort out issues with testing/applying > before they become painful when it comes to applying them to trunk, What exactly are you suggesting by this statement?! Just to quote what you said: "This is an unfortunate reality that occurs when delaying major changes for a significant period." We've got troubles with patches and their testing. I'm really concerned that we don't approach it, but await the next 'major change' that will again remind us about it. I wonder how much time will it take to apply another m2 patch and how we work on it. So, the above should be read as: 'I'm really concerned that although we know we're in a big trouble with patches and their way to trunk, we don't want to sort it out once and for all, but rather ignore it until there's no other way'. I'm preparing a doc about a possible solution that will guide us thru this bumpy RTC road. Will surely take some time, but I hope it's worth it. See you soon...;-) Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: svn commit: r419764 - /geronimo/trunk/m2-plugins/pom.xml
On Jul 7, 2006, at 1:12 AM, Jacek Laskowski wrote: It is when one's doing some non-trivial changes without careful thinking how to sort out issues with testing/applying before they become painful when it comes to applying them to trunk, What exactly are you suggesting by this statement?! --jason
Re: svn commit: r419764 - /geronimo/trunk/m2-plugins/pom.xml
On 7/7/06, Jason Dillon <[EMAIL PROTECTED]> wrote: This is an unfortunate reality that occurs when delaying major changes for a significant period. I disagree, Jason. Quite a contrary. It is when one's doing some non-trivial changes without careful thinking how to sort out issues with testing/applying before they become painful when it comes to applying them to trunk, i.e. the problems testers had were dismissed and noone really knew how the changes were made but the author. It's unnacceptable and am happy to read your comment as supporting the opinion ;-) Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: svn commit: r419764 - /geronimo/trunk/m2-plugins/pom.xml
Yes, sorry... I'm currently resolving an issue that has popped up due to changes made in the trunk post the last cut of the patch which kinda whacked the application an validation. I'm reapplying now from a known good source and revalidating. Will need to correct a faulty commit to all_changes.log post commiting the real changes for 2161. This is an unfortunate reality that occurs when delaying major changes for a significant period. --jason On Jul 6, 2006, at 7:39 PM, John Sisson wrote: [EMAIL PROTECTED] wrote: Author: jdillon Date: Thu Jul 6 18:43:26 2006 New Revision: 419764 URL: http://svn.apache.org/viewvc?rev=419764&view=rev Log: Merge changes for m2 Modified: geronimo/trunk/m2-plugins/pom.xml (contents, props changed) Hi Jason, Can you please put the JIRA issue in the svn log comments so it shows up in the "Subversion commits" tab in the JIRA issue so everyone can keep track of what commits/merges have been done for a JIRA. Thanks, John
Re: svn commit: r419764 - /geronimo/trunk/m2-plugins/pom.xml
[EMAIL PROTECTED] wrote: Author: jdillon Date: Thu Jul 6 18:43:26 2006 New Revision: 419764 URL: http://svn.apache.org/viewvc?rev=419764&view=rev Log: Merge changes for m2 Modified: geronimo/trunk/m2-plugins/pom.xml (contents, props changed) Hi Jason, Can you please put the JIRA issue in the svn log comments so it shows up in the "Subversion commits" tab in the JIRA issue so everyone can keep track of what commits/merges have been done for a JIRA. Thanks, John
