Re: Project Notifier removed when editing build definitions
Yes. Happened after Rahul's notification re-work. Jesse McConnell wrote: > This was on trunk, correct? > > > rahul, this might be an issue in the notifier actions > > jesse > > On 11/7/06, Emmanuel Hugonnet <[EMAIL PROTECTED]> wrote: >> Hi, >> I have edited my build definition since I have to pass some parameters >> via -D. After that my notifier which was imported from my POM was >> removed :(. It looks like updating the project configuration updates >> everything based on submit and not on previous configuration + changes. >> In the database all is removed :( >> > > -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
Re: Independent perforce ant projects triggering builds of each other
On 9 Nov 2006, at 00:14, Jason Foster wrote: 1. The perforce clientspec setup for the machine is targeting a rather large subsection of the repository, starting at a level that is higher up than any of the projects we want to build. Could this be the cause? Does the clientspec need to be narrowed down? I think this is the key point. I'm not a perforce user, but I imagine the perforce scm plugin for maven will look for any changes in this client spec and consider them changes for the project. See if you can change the client spec to be a bit more project specfic, and see if that fixes it. I know it can be a pain, as I guess you are just inheriting it. David
