Re: b10 werkz changes break reactor
Debugging it I have seen WerkzProject return null to the eachGoal var in the plugin manager, but I can't debug werkz as the source at cvs.werkz.sf.net is out of date. I'm guessing the werkz that got dropped with b10 is a build from somewhere else? cvs.codehaus.org:/cvsroot/werkz co werkz -bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: b10 werkz changes break reactor
On Tue, 2003-07-15 at 20:35, Brett Porter wrote: Hi, It seems some of the changes made to werkz late in b10 have broken the reactor in some cases. I was using a build from CVS of about 1 or 2 weeeks ago that was fine, but rolling out b10 has caused a lot of unknown goal exceptions when running under reactor. Changing into the appropriate dir and running the goal has no problems. Please make sure nothing has changed on your end. The reactor build for Maven itself is always the final test for the reactor and I always give the Plexus components a whirl. The goal is in my own plugin. Debugging it I have seen WerkzProject return null to the eachGoal var in the plugin manager, but I can't debug werkz as the source at cvs.werkz.sf.net is out of date. I'm guessing the werkz that got dropped with b10 is a build from somewhere else? Can someone help me out getting that source? For now, I'm having to roll back to beta 9 :( Cheers, Brett ~*~*~*~*~*~*~ Brett Porter - Web Developer f2 Network ~ everything essential Ph: +61 2 8596 4437 Email: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: b10 werkz changes break reactor
It appears to be a problem with executing more than one goal at a time: maven clean cdit:build fails maven clean; maven cdit:build works This isn't always the case (other projects have just the cdit:build fail), so there is definitely more to it - but I'm leaving it at that until I can try it out at home. Cheers, Brett -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, 16 July 2003 11:12 AM To: Maven Developers List Subject: Re: b10 werkz changes break reactor On Tue, 2003-07-15 at 20:35, Brett Porter wrote: Hi, It seems some of the changes made to werkz late in b10 have broken the reactor in some cases. I was using a build from CVS of about 1 or 2 weeeks ago that was fine, but rolling out b10 has caused a lot of unknown goal exceptions when running under reactor. Changing into the appropriate dir and running the goal has no problems. Please make sure nothing has changed on your end. The reactor build for Maven itself is always the final test for the reactor and I always give the Plexus components a whirl. The goal is in my own plugin. Debugging it I have seen WerkzProject return null to the eachGoal var in the plugin manager, but I can't debug werkz as the source at cvs.werkz.sf.net is out of date. I'm guessing the werkz that got dropped with b10 is a build from somewhere else? Can someone help me out getting that source? For now, I'm having to roll back to beta 9 :( Cheers, Brett ~*~*~*~*~*~*~ Brett Porter - Web Developer f2 Network ~ everything essential Ph: +61 2 8596 4437 Email: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: b10 werkz changes break reactor
There was a change in the semantics of werkz / attainGoal.I don't know the specifics of it, but it was supposed to allow finegrained control of prerequisite handling. Looking for code that added session as a parameter to the attain tags I think. Bob / Jason will probably know more. Whether this is at all related ... no idea... Brett Porter wrote: It appears to be a problem with executing more than one goal at a time: maven clean cdit:build fails maven clean; maven cdit:build works This isn't always the case (other projects have just the cdit:build fail), so there is definitely more to it - but I'm leaving it at that until I can try it out at home. Cheers, Brett -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, 16 July 2003 11:12 AM To: Maven Developers List Subject: Re: b10 werkz changes break reactor On Tue, 2003-07-15 at 20:35, Brett Porter wrote: Hi, It seems some of the changes made to werkz late in b10 have broken the reactor in some cases. I was using a build from CVS of about 1 or 2 weeeks ago that was fine, but rolling out b10 has caused a lot of unknown goal exceptions when running under reactor. Changing into the appropriate dir and running the goal has no problems. Please make sure nothing has changed on your end. The reactor build for Maven itself is always the final test for the reactor and I always give the Plexus components a whirl. The goal is in my own plugin. Debugging it I have seen WerkzProject return null to the eachGoal var in the plugin manager, but I can't debug werkz as the source at cvs.werkz.sf.net is out of date. I'm guessing the werkz that got dropped with b10 is a build from somewhere else? Can someone help me out getting that source? For now, I'm having to roll back to beta 9 :( Cheers, Brett ~*~*~*~*~*~*~ Brett Porter - Web Developer f2 Network ~ everything essential Ph: +61 2 8596 4437 Email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: b10 werkz changes break reactor
On Wed, 16 Jul 2003, Ben Walding wrote: There was a change in the semantics of werkz / attainGoal.I don't know the specifics of it, but it was supposed to allow finegrained control of prerequisite handling. Looking for code that added session as a parameter to the attain tags I think. Bob / Jason will probably know more. Whether this is at all related ... no idea... Default behaviour hasn't changed. I think what we did (Peter Lynch could probably tell us in more detail, since he's the one who wanted it) a @session attribute so you -could- share the global session. Jason's also added, somewhere along the way, dunno if used in b10, some goal/callback listener thingies. -bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
